I'm running Proxmox 3.3.1 to host a virtual machine running Linux (64bit, kernel version 3.2.0). The virtual machine uses a 512GB HDD which was unfortunately configured to use the ide driver when creating the VM.

How can I reconfigure the virtual machine such that the hard disk is accessed using the virtio driver?

I found this forum entry on the topic, but the proposed solutions seem to be about doing this for a Windows guest, which requires adding a small dummy HDD in order to driver installation of drivers inside a guest. I suppose this is not needed for Linux.

Another answer on this topic (though purely about KVM, not about Proxmox in particular) mentions that

[..] you'd need to change the drive's label inside of the guest's /etc/fstab file, replacing all /dev/sdX with /dev/vdX [..]

However, I noticed that the Proxmox guest doesn't use /dev/hdX at all but rather /dev/mapper/<vmname>-root instead. So I'm not sure that answer is really applicable, since Proxmox appears to have it's own way of doing things.

  • Just change it to virtio and go on with your life. Feb 29, 2016 at 15:12
  • @MichaelHampton Well, how to change it to virtio such that I can go on with my life is precisely what this question is about. :-) Feb 29, 2016 at 15:13
  • Doesn't Proxmox provide a nice drop-down box or something like that? Feb 29, 2016 at 15:14
  • @MichaelHampton I'd love to hear more about that, because I didn't find any. It does permit changing the driver of the NIC via the web GUI. Feb 29, 2016 at 15:28
  • @MichaelHampton I said I didn't find it for what I talk about in my question: Hard Disk Drives. I did find it for NICs. Feb 29, 2016 at 15:34

1 Answer 1


Proxmox basically is the interface for use some hypervisor, then probably you use KVM as hypervisor.

Try to change the disc driver and test, in theory you should have no problem, but maybe grub fail in this case update the grub config, for example:

rm /boot/grub/device.map grub-mkdevicemap update-grub2

On some new linux versions grub don't have map file, only do update-grub2 or something.

For do this easily, you can use system rescue cd, and work over you guest vm in a chroot environment. You see mapper path because you're using LVM partitions on you guest.

(I post as answer because I can't comment)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .