<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Qcow2 on Thaddeus Koenig</title><link>https://www.thaddeuskoenig.com/tags/qcow2/</link><description>Recent content in Qcow2 on Thaddeus Koenig</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Thaddeus Koenig</copyright><lastBuildDate>Thu, 16 Jan 2025 06:06:24 -0500</lastBuildDate><atom:link href="https://www.thaddeuskoenig.com/tags/qcow2/index.xml" rel="self" type="application/rss+xml"/><item><title>Proxmox Qcow2 Import</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_proxmox_qcow2_import/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_proxmox_qcow2_import/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a href="#introduction" class="post-heading__anchor" aria-hidden="true"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;For those who aren&amp;rsquo;t familiar with the concept. Different hypervisors use different file formats to represent VM images and due to the fact that Proxmox uses Qemu (Quick Emulator)/KVM (Kernel-based Virtual Machine) to provide virtualization, it in turn uses Qcow2 (Qemu Copy-On-Write) as the storage file format for virtual machines data. The process to move Qcow2 files into Proxmox may not be as straight forward as it is on VMware, but its still a relatively painless process.&lt;/p&gt;</description></item></channel></rss>