<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Xenserver 6.5 OVF+VHD to XCPNG]]></title><description><![CDATA[<p dir="auto">I feel like I used to know this answer, but that could be my imagination. <img src="https://xcp-ng.org/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=f084dd9e819" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">I have a Windows Server 2008 R2 Standard VM that was exported from Xenserver 6.5 perhaps 10 years ago. The export is servername.ovf along with a pair of [uuid].vhd files. The source of the export was an HP server with a paid of Xeon E5s... maybe 2640 or similar. The new target is variety of Dell Poweredges with various "modern" Xeons (eg, 6226R). There's a HUGE architectural difference.</p>
<p dir="auto">I have tried:</p>
<ol>
<li>Importing the OVF, which fails complaining about the disks</li>
<li>TAR'd the OVF and VHDs into an OVA, which also fails</li>
<li>I've tried these with two versions of XCP Center and two versions of XO targeting three versions of XCP (8.1, 8.2, and 8.3)</li>
<li>Importing just the VHDs via XO, that fails</li>
</ol>
<p dir="auto">I poked around on the google and Gemini suggested using vbox to convert the VHD to a VMDK, but I think that's incorrect, and it doesn't work anyway.... Vbox bombs out with "could not get the storage format" of the VHD.</p>
<p dir="auto">Does anyone have any idea on how I might be able to get this ancient @$$ VM running again?</p>
]]></description><link>https://xcp-ng.org/forum/topic/12427/xenserver-6.5-ovf-vhd-to-xcpng</link><generator>RSS for Node</generator><lastBuildDate>Fri, 21 Aug 2026 01:41:40 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/12427.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Aug 2026 23:00:05 GMT</pubDate><ttl>60</ttl></channel></rss>