VM not booting after qm importdisk

[Ventor]

Hello,

we are in the middle of the migration process from oVirt to Proxmox, since the recent Redhat / CentOS news. We bought new hypervisors and would like to run them in a 3 node cluster.

To transfer our VMs, I thought we could use the qm importdisk command to transfer our RAW disk images. So I copy them over via SCP and import the on the new hypervisor. Everything works fine until I want to boot the VM.

The VM says: "Could not read the boot disk."

On oVirt we used VirtIO for the disks, no SCSI or anything like that.

Is there anything I need to do before this works?

Cheers from Cologne,

Marc

 

[TodorPetkov]

Is the new (imported) disk marked as boot device?

 

[Ventor]

Is the new (imported) disk marked as boot device?

Yes. Even when I try to manually boot it, it does not work.

 

[flatpzero]

The instructions for migrating VMs from libvirt to Proxmox are not very good and the help from Proxmox support is also not very good.

If your VM was using virtio for block access with libvirt then you need to ensure that virtio is used to boot.

The file that you need to pay attention to is /etc/pve/qemu-server/vm#.conf

where vm# is the VM id number you'll see from the Proxmox web UI.

For virtio VMs, you need to ensure that these three lines are present:

boot: virtio0
scsihw: virtio-scsi-pci
virtio0: images/vm-vm#-disk-0,size=100G

Use the "qm set" command to change that file, don't edit it yourself. as that'll take care of ensuring that proxmox knows about the config changes.

The above is especially true for Windows VMs. With Linux you may get away with being able to change from virtio to scsi but Windows will not boot if you try that. Your Proxmox VM *must* have the same disk configuration as your KVM VM.

It would be good if there was a tool to convert the libkvm XML into a Proxmox .conf file or similar.