<?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[Grub looking for /dev/vda instead of /dev/xvda]]></title><description><![CDATA[<p dir="auto">Hey Team XPC,</p>
<p dir="auto">I've got a VM running on an XPC-NG 8.1 host that I think was probably migrated to there from a different vm host (kvm maybe?) several years ago.</p>
<p dir="auto">The VM is running Zentyal 6.2 which is based on Ubuntu 18.04 and I'm trying to update it to Zentyal 7, which I think also updates the base OS to 20.04.</p>
<p dir="auto">The upgrade is failing with a message that <code> grub-install /dev/vda</code> failed as it's missing from the device.map. I ran <code>grub-mkdevicemap</code> thinking that would help but then realised that the device is /dev/<strong>x</strong>vda not /dev/vda. This is why I think the system might have originated with a different hypervisor. To back that up, if I check fstab I see a note to say that "# / was on /dev/vda1 during installation"</p>
<p dir="auto">So, at some point during the upgrade, grub is being run and told to install it's self to /dev/vda but that doesn't exist any more, problem is that I'm struggling a bit to work out where the /dev/vda is coming from so that I can go fix it. Does anyone have any idea where I might start looking?</p>
]]></description><link>https://xcp-ng.org/forum/topic/10670/grub-looking-for-dev-vda-instead-of-dev-xvda</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 09:55:31 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/10670.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 27 Mar 2025 16:09:05 GMT</pubDate><ttl>60</ttl></channel></rss>