hobokenchicken/dustin.coffee-jekyll-blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added new post

Browse Source
This commit is contained in:
Dustin Newkirk
2026-02-12 11:17:02 -05:00
commit 8c3ae79399
47 changed files with 4157 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

124
tech/2024/03/04/changes-are-brewing.html Normal file
View File

@@ -0,0 +1,124 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<!-- Begin Jekyll SEO tag v2.8.0 -->
<title>transitioning from lxc to vms: preparing for xcp-ng | d@n tech</title>
<meta name="generator" content="Jekyll v4.3.4" />
<meta property="og:title" content="transitioning from lxc to vms: preparing for xcp-ng" />
<meta name="author" content="dustin newkirk" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="Introduction: In this latest discussion at d@n tech, we’re focusing on a significant transition in the server environment. I’ve recently embarked on a project to shift from LXC containers to VMs (Virtual Machines), a move prompted by upcoming changes in the server infrastructure. Why the Shift?: The move away from LXC containers, a staple in my Proxmox setup, to VMs is driven by a need for greater flexibility and platform independence. With plans to eventually migrate to XCP-NG from Proxmox, VMs present a more viable option due to their portability and compatibility with various platforms. The Transition Process: Evaluation: The initial phase involved assessing the existing LXC configurations, understanding the nuances of their deployment within Proxmox. Selecting the VM Platform: After exploring various options, I settled on a VM platform that complements the forthcoming XCP-NG environment. Migration Strategy: I planned the migration in stages, aiming to minimize disruptions and ensure data integrity throughout the process. Implementation: The services were methodically transitioned from LXC to VMs, with each step rigorously tested for performance and functionality. Post-Migration Optimization: Following the migration, I’ve been focusing on fine-tuning the VMs to optimize their performance in the new environment. Upcoming Changes: The most significant upcoming change is the construction and deployment of a new server that will run XCP-NG. This shift marks a departure from the current Proxmox setup. Once the new server is built and put into production, the VMs, currently housed within Proxmox, will be migrated over to XCP-NG. This transition is not just a change in technology but a strategic move towards a more versatile and robust server ecosystem. Challenges and Learnings: Navigating through this transition hasn’t been straightforward. From compatibility checks to performance tuning, each step presented its own set of challenges. However, these hurdles have provided valuable insights into both Proxmox and XCP-NG platforms. Conclusion: This journey from LXC containers to VMs, culminating in the move to XCP-NG, is more than a technical upgrade. It’s a step towards future-proofing the server environment, ensuring I stay agile and adaptable in the ever-evolving tech landscape. Looking Ahead at d@n tech: As we move closer to the full deployment of the XCP-NG server, stay tuned for more updates, insights, and learnings from this journey." />
<meta property="og:description" content="Introduction: In this latest discussion at d@n tech, we’re focusing on a significant transition in the server environment. I’ve recently embarked on a project to shift from LXC containers to VMs (Virtual Machines), a move prompted by upcoming changes in the server infrastructure. Why the Shift?: The move away from LXC containers, a staple in my Proxmox setup, to VMs is driven by a need for greater flexibility and platform independence. With plans to eventually migrate to XCP-NG from Proxmox, VMs present a more viable option due to their portability and compatibility with various platforms. The Transition Process: Evaluation: The initial phase involved assessing the existing LXC configurations, understanding the nuances of their deployment within Proxmox. Selecting the VM Platform: After exploring various options, I settled on a VM platform that complements the forthcoming XCP-NG environment. Migration Strategy: I planned the migration in stages, aiming to minimize disruptions and ensure data integrity throughout the process. Implementation: The services were methodically transitioned from LXC to VMs, with each step rigorously tested for performance and functionality. Post-Migration Optimization: Following the migration, I’ve been focusing on fine-tuning the VMs to optimize their performance in the new environment. Upcoming Changes: The most significant upcoming change is the construction and deployment of a new server that will run XCP-NG. This shift marks a departure from the current Proxmox setup. Once the new server is built and put into production, the VMs, currently housed within Proxmox, will be migrated over to XCP-NG. This transition is not just a change in technology but a strategic move towards a more versatile and robust server ecosystem. Challenges and Learnings: Navigating through this transition hasn’t been straightforward. From compatibility checks to performance tuning, each step presented its own set of challenges. However, these hurdles have provided valuable insights into both Proxmox and XCP-NG platforms. Conclusion: This journey from LXC containers to VMs, culminating in the move to XCP-NG, is more than a technical upgrade. It’s a step towards future-proofing the server environment, ensuring I stay agile and adaptable in the ever-evolving tech landscape. Looking Ahead at d@n tech: As we move closer to the full deployment of the XCP-NG server, stay tuned for more updates, insights, and learnings from this journey." />
<link rel="canonical" href="https://dustin.coffee/tech/2024/03/04/changes-are-brewing.html" />
<meta property="og:url" content="https://dustin.coffee/tech/2024/03/04/changes-are-brewing.html" />
<meta property="og:site_name" content="d@n tech" />
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2024-03-04T00:00:00-05:00" />
<meta name="twitter:card" content="summary" />
<meta property="twitter:title" content="transitioning from lxc to vms: preparing for xcp-ng" />
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"dustin newkirk"},"dateModified":"2024-03-04T00:00:00-05:00","datePublished":"2024-03-04T00:00:00-05:00","description":"Introduction: In this latest discussion at d@n tech, we’re focusing on a significant transition in the server environment. I’ve recently embarked on a project to shift from LXC containers to VMs (Virtual Machines), a move prompted by upcoming changes in the server infrastructure. Why the Shift?: The move away from LXC containers, a staple in my Proxmox setup, to VMs is driven by a need for greater flexibility and platform independence. With plans to eventually migrate to XCP-NG from Proxmox, VMs present a more viable option due to their portability and compatibility with various platforms. The Transition Process: Evaluation: The initial phase involved assessing the existing LXC configurations, understanding the nuances of their deployment within Proxmox. Selecting the VM Platform: After exploring various options, I settled on a VM platform that complements the forthcoming XCP-NG environment. Migration Strategy: I planned the migration in stages, aiming to minimize disruptions and ensure data integrity throughout the process. Implementation: The services were methodically transitioned from LXC to VMs, with each step rigorously tested for performance and functionality. Post-Migration Optimization: Following the migration, I’ve been focusing on fine-tuning the VMs to optimize their performance in the new environment. Upcoming Changes: The most significant upcoming change is the construction and deployment of a new server that will run XCP-NG. This shift marks a departure from the current Proxmox setup. Once the new server is built and put into production, the VMs, currently housed within Proxmox, will be migrated over to XCP-NG. This transition is not just a change in technology but a strategic move towards a more versatile and robust server ecosystem. Challenges and Learnings: Navigating through this transition hasn’t been straightforward. From compatibility checks to performance tuning, each step presented its own set of challenges. However, these hurdles have provided valuable insights into both Proxmox and XCP-NG platforms. Conclusion: This journey from LXC containers to VMs, culminating in the move to XCP-NG, is more than a technical upgrade. It’s a step towards future-proofing the server environment, ensuring I stay agile and adaptable in the ever-evolving tech landscape. Looking Ahead at d@n tech: As we move closer to the full deployment of the XCP-NG server, stay tuned for more updates, insights, and learnings from this journey.","headline":"transitioning from lxc to vms: preparing for xcp-ng","mainEntityOfPage":{"@type":"WebPage","@id":"https://dustin.coffee/tech/2024/03/04/changes-are-brewing.html"},"url":"https://dustin.coffee/tech/2024/03/04/changes-are-brewing.html"}</script>
<!-- End Jekyll SEO tag -->
<meta name="keywords" content="" />
<meta name="google-adsense-account" content="ca-pub-5033279084799102">
<link rel="shortcut icon" href="/assets/logos/dn-tech-favicon-color.png" />
<link rel="apple-touch-icon" href="/assets/logos/logo-color.png"/>
<link rel="stylesheet" type="text/css" href="/assets/css/styles.css" />
<link rel="stylesheet" type="text/css" href="/assets/css/prism.css" />
<script src="/assets/js/prism.js"></script>
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-5033279084799102"
crossorigin="anonymous"></script>
</head>
<body>
<div class="wrapper">
<header class="wrapper-header">
<div class="header">
<h1>d@n tech</h1>
<br>
<h5><i>Caffinated Tech Insights</i></h5>
<br>
<nav>
<a href="/">About & Contact</a>
<a href="/posts">Posts</a>
<a href="/categories/">Categories</a>
<a href="/resume">Resume</a>
</nav>
<hr>
</div>
</header>
<main class="wrapper-main">
<div class="main-content">
<div class="post-info">
<h2>transitioning from lxc to vms: preparing for xcp-ng</h2>
<p>04 Mar 2024 - </p>
</div>
<div class="post-content">
<h4 id="introduction">Introduction:</h4>
<p>In this latest discussion at d@n tech, we’re focusing on a significant transition in the server environment. I’ve recently embarked on a project to shift from LXC containers to VMs (Virtual Machines), a move prompted by upcoming changes in the server infrastructure.</p>
<h4 id="why-the-shift">Why the Shift?:</h4>
<p>The move away from LXC containers, a staple in my Proxmox setup, to VMs is driven by a need for greater flexibility and platform independence. With plans to eventually migrate to XCP-NG from Proxmox, VMs present a more viable option due to their portability and compatibility with various platforms.</p>
<h4 id="the-transition-process">The Transition Process:</h4>
<ul>
<li><strong>Evaluation:</strong> The initial phase involved assessing the existing LXC configurations, understanding the nuances of their deployment within Proxmox.</li>
<li><strong>Selecting the VM Platform:</strong> After exploring various options, I settled on a VM platform that complements the forthcoming XCP-NG environment.</li>
<li><strong>Migration Strategy:</strong> I planned the migration in stages, aiming to minimize disruptions and ensure data integrity throughout the process.</li>
<li><strong>Implementation:</strong> The services were methodically transitioned from LXC to VMs, with each step rigorously tested for performance and functionality.</li>
<li><strong>Post-Migration Optimization:</strong> Following the migration, I’ve been focusing on fine-tuning the VMs to optimize their performance in the new environment.</li>
</ul>
<h4 id="upcoming-changes">Upcoming Changes:</h4>
<p>The most significant upcoming change is the construction and deployment of a new server that will run XCP-NG. This shift marks a departure from the current Proxmox setup. Once the new server is built and put into production, the VMs, currently housed within Proxmox, will be migrated over to XCP-NG. This transition is not just a change in technology but a strategic move towards a more versatile and robust server ecosystem.</p>
<h4 id="challenges-and-learnings">Challenges and Learnings:</h4>
<p>Navigating through this transition hasn’t been straightforward. From compatibility checks to performance tuning, each step presented its own set of challenges. However, these hurdles have provided valuable insights into both Proxmox and XCP-NG platforms.</p>
<h4 id="conclusion">Conclusion:</h4>
<p>This journey from LXC containers to VMs, culminating in the move to XCP-NG, is more than a technical upgrade. It’s a step towards future-proofing the server environment, ensuring I stay agile and adaptable in the ever-evolving tech landscape.</p>
<h4 id="looking-ahead-at-dn-tech">Looking Ahead at d@n tech:</h4>
<p>As we move closer to the full deployment of the XCP-NG server, stay tuned for more updates, insights, and learnings from this journey.</p>
</div>
</div>
</main>
</div>
<footer class="wrapper-footer">
<div class="footer">
<span class="footer-text float-left">This work is licensed under <a rel="license" href="https://www.gnu.org/licenses/gpl-3.0.en.html" target="_blank">GPLv3</a></span>
<span class="footer-text float-right">
Site Updated: 2025-07-29 ET (<a href="/feed.xml" target="_blank">RSS</a>)
</span>
</div>
<script src='https://storage.ko-fi.com/cdn/scripts/overlay-widget.js'></script>
<script>
kofiWidgetOverlay.draw('dustinnewkirk', {
'type': 'floating-chat',
'floating-chat.donateButton.text': 'Support Me',
'floating-chat.donateButton.background-color': '#ff851b',
'floating-chat.donateButton.text-color': '#3D2200'
});
</script>
</footer>
</body>
</html>

114
tech/2024/03/27/brewing-resilience-from-lxc-to-vm-for-flawless-plex-and-beyond.html Normal file
View File

@@ -0,0 +1,114 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<!-- Begin Jekyll SEO tag v2.8.0 -->
<title>brewing resilience: from lxc to vm for flawless plex and beyond | d@n tech</title>
<meta name="generator" content="Jekyll v4.3.4" />
<meta property="og:title" content="brewing resilience: from lxc to vm for flawless plex and beyond" />
<meta name="author" content="dustin newkirk" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="Introduction: Hey everyone, it’s time for another tech update from d@n tech! Recently, I made a significant change to my Plex server setup that I’m excited to share with you all. After encountering issues with hardware transcoding, I decided to transition my Plex server from an LXC container to a VM, utilizing GPU passthrough for flawless transcoding performance." />
<meta property="og:description" content="Introduction: Hey everyone, it’s time for another tech update from d@n tech! Recently, I made a significant change to my Plex server setup that I’m excited to share with you all. After encountering issues with hardware transcoding, I decided to transition my Plex server from an LXC container to a VM, utilizing GPU passthrough for flawless transcoding performance." />
<link rel="canonical" href="https://dustin.coffee/tech/2024/03/27/brewing-resilience-from-lxc-to-vm-for-flawless-plex-and-beyond.html" />
<meta property="og:url" content="https://dustin.coffee/tech/2024/03/27/brewing-resilience-from-lxc-to-vm-for-flawless-plex-and-beyond.html" />
<meta property="og:site_name" content="d@n tech" />
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2024-03-27T00:00:00-04:00" />
<meta name="twitter:card" content="summary" />
<meta property="twitter:title" content="brewing resilience: from lxc to vm for flawless plex and beyond" />
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"dustin newkirk"},"dateModified":"2024-03-27T00:00:00-04:00","datePublished":"2024-03-27T00:00:00-04:00","description":"Introduction: Hey everyone, it’s time for another tech update from d@n tech! Recently, I made a significant change to my Plex server setup that I’m excited to share with you all. After encountering issues with hardware transcoding, I decided to transition my Plex server from an LXC container to a VM, utilizing GPU passthrough for flawless transcoding performance.","headline":"brewing resilience: from lxc to vm for flawless plex and beyond","mainEntityOfPage":{"@type":"WebPage","@id":"https://dustin.coffee/tech/2024/03/27/brewing-resilience-from-lxc-to-vm-for-flawless-plex-and-beyond.html"},"url":"https://dustin.coffee/tech/2024/03/27/brewing-resilience-from-lxc-to-vm-for-flawless-plex-and-beyond.html"}</script>
<!-- End Jekyll SEO tag -->
<meta name="keywords" content="" />
<meta name="google-adsense-account" content="ca-pub-5033279084799102">
<link rel="shortcut icon" href="/assets/logos/dn-tech-favicon-color.png" />
<link rel="apple-touch-icon" href="/assets/logos/logo-color.png"/>
<link rel="stylesheet" type="text/css" href="/assets/css/styles.css" />
<link rel="stylesheet" type="text/css" href="/assets/css/prism.css" />
<script src="/assets/js/prism.js"></script>
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-5033279084799102"
crossorigin="anonymous"></script>
</head>
<body>
<div class="wrapper">
<header class="wrapper-header">
<div class="header">
<h1>d@n tech</h1>
<br>
<h5><i>Caffinated Tech Insights</i></h5>
<br>
<nav>
<a href="/">About & Contact</a>
<a href="/posts">Posts</a>
<a href="/categories/">Categories</a>
<a href="/resume">Resume</a>
</nav>
<hr>
</div>
</header>
<main class="wrapper-main">
<div class="main-content">
<div class="post-info">
<h2>brewing resilience: from lxc to vm for flawless plex and beyond</h2>
<p>27 Mar 2024 - </p>
</div>
<div class="post-content">
<h4 id="introduction">Introduction:</h4>
<p>Hey everyone, it’s time for another tech update from d@n tech! Recently, I made a significant change to my Plex server setup that I’m excited to share with you all. After encountering issues with hardware transcoding, I decided to transition my Plex server from an LXC container to a VM, utilizing GPU passthrough for flawless transcoding performance.</p>
<h4 id="the-importance-of-hardware-transcoding-and-gpu-passthrough">The Importance of Hardware Transcoding and GPU Passthrough:</h4>
<p>Before diving into the transition process, let’s talk about why hardware transcoding and GPU passthrough are crucial for a smooth Plex experience. Hardware transcoding offloads the burden of video transcoding from the CPU to specialized hardware, such as a GPU. This results in lower CPU usage, faster transcoding speeds, and better playback performance, especially for remote streaming or multiple concurrent streams. GPU passthrough allows a virtual machine to directly access and utilize a physical GPU, ensuring optimal performance for tasks like video encoding and decoding.</p>
<h4 id="encountering-issues-and-making-the-transition">Encountering Issues and Making the Transition:</h4>
<p>A couple of weeks ago, I noticed that hardware transcoding on my Plex server was no longer functioning properly. After troubleshooting for hours, I discovered that something had broken, preventing the GPU from being utilized for transcoding within the LXC container. Faced with this dilemma, I decided to take the plunge and convert my Plex server to a VM, passing the GPU directly to the VM for optimal performance.</p>
<h4 id="the-transition-process">The Transition Process:</h4>
<p>Converting the Plex server from an LXC container to a VM was no small feat, but it was well worth the effort. I spent several hours meticulously configuring the VM and setting up GPU passthrough. Once everything was in place, I fired up Plex and was thrilled to see hardware transcoding working flawlessly once again. The difference in performance was like night and day, with smoother playback and reduced CPU load.</p>
<h4 id="conclusion">Conclusion:</h4>
<p>The transition from LXC to VM with GPU passthrough has revitalized my Plex server, ensuring seamless streaming experiences for users across the United States. With hardware transcoding back on track, remote streaming is once again smooth and reliable, regardless of the distance. Beyond Plex, this change underscores the significance of leveraging hardware acceleration and GPU passthrough for a wide range of services hosted on my server. From media streaming to collaborative projects and beyond, the improved performance enhances the overall user experience and reinforces the reliability of my server infrastructure.</p>
<h4 id="stay-tuned">Stay Tuned:</h4>
<p>As I continue to fine-tune my server setup and explore new technologies, including optimizations for remote streaming and enhancements to various hosted services, be sure to stay tuned for more updates and insights here at d@n tech. Whether you’re a fellow tech enthusiast or a remote user enjoying the benefits of my server, there’s always something new on the horizon.</p>
</div>
</div>
</main>
</div>
<footer class="wrapper-footer">
<div class="footer">
<span class="footer-text float-left">This work is licensed under <a rel="license" href="https://www.gnu.org/licenses/gpl-3.0.en.html" target="_blank">GPLv3</a></span>
<span class="footer-text float-right">
Site Updated: 2025-07-29 ET (<a href="/feed.xml" target="_blank">RSS</a>)
</span>
</div>
<script src='https://storage.ko-fi.com/cdn/scripts/overlay-widget.js'></script>
<script>
kofiWidgetOverlay.draw('dustinnewkirk', {
'type': 'floating-chat',
'floating-chat.donateButton.text': 'Support Me',
'floating-chat.donateButton.background-color': '#ff851b',
'floating-chat.donateButton.text-color': '#3D2200'
});
</script>
</footer>
</body>
</html>