I reloaded PVE on a single non clustered node that was I was having networking issues. It was the wrong call as it was just a IP conflict, too late to go back.
Now I have a fresh install of PVE 7.4-3 with many RAW VM disks (Windows 7 guests) on LVMs that are all added as storage a show up as expected.
LVM King256
After recreating the VM (ID 350) as close to the original config as I could recall, I tries to attach the old VM Disk 2 ways:
1) Rename: lvrename the vm disk to the same number as the new VM
lvrename /dev/King256/vm-200-disk-0 /dev/King256/vm-350-disk-1
qm rescan
And the VM Disk is added to the config of VM 350
Change boot options to boot from disk-1
2) Extract to raw and import:
dd if=/dev/King256/vm-200-disk-0 of=/root/vm350.raw status=progress
qm importdisk 350 /root/vm350.raw King256
Change boot options to boot from disk-1
Both of the above methods fail and I get
VM 350 not running
TASK ERROR: Failed to run vncproxy.
I haven't restored RAW LVM disks before so I'm stumped.
I don't know that its really a VNC issue, but rather the VM is failing completely at boot, so the VNC never comes up.
I'm sure there hasn't been any drive corruption.
Update 1
Running the VM from the command line I see:
root@gamebox:~# qm start 350
WARN: no physical CD-ROM available, ignoring
kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=101: Can't create IDE unit 1, bus supports only 1 units
start failed: QEMU exited with code 1
root@gamebox:~# qm start 350
WARN: no physical CD-ROM available, ignoring
kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=101: Can't create IDE unit 1, bus supports only 1 units
start failed: QEMU exited with code 1
Update2
Ok so apparently this is common with Q35 so I've switched to i440fx
I'm getting this now
Wouldn't the restored RAW disk be in the same bootable state as before? With the special windows partitions for booting?
Update3
I assigned on the disks to a working W10 VM and it's showing up as Unallocated in W10 Disk Management.
Now I have a fresh install of PVE 7.4-3 with many RAW VM disks (Windows 7 guests) on LVMs that are all added as storage a show up as expected.
LVM King256
After recreating the VM (ID 350) as close to the original config as I could recall, I tries to attach the old VM Disk 2 ways:
1) Rename: lvrename the vm disk to the same number as the new VM
lvrename /dev/King256/vm-200-disk-0 /dev/King256/vm-350-disk-1
qm rescan
And the VM Disk is added to the config of VM 350
Change boot options to boot from disk-1
2) Extract to raw and import:
dd if=/dev/King256/vm-200-disk-0 of=/root/vm350.raw status=progress
qm importdisk 350 /root/vm350.raw King256
Change boot options to boot from disk-1
Both of the above methods fail and I get
VM 350 not running
TASK ERROR: Failed to run vncproxy.
I haven't restored RAW LVM disks before so I'm stumped.
I don't know that its really a VNC issue, but rather the VM is failing completely at boot, so the VNC never comes up.
I'm sure there hasn't been any drive corruption.
Update 1
Running the VM from the command line I see:
root@gamebox:~# qm start 350
WARN: no physical CD-ROM available, ignoring
kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=101: Can't create IDE unit 1, bus supports only 1 units
start failed: QEMU exited with code 1
root@gamebox:~# qm start 350
WARN: no physical CD-ROM available, ignoring
kvm: -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=101: Can't create IDE unit 1, bus supports only 1 units
start failed: QEMU exited with code 1
Update2
Ok so apparently this is common with Q35 so I've switched to i440fx
I'm getting this now
Wouldn't the restored RAW disk be in the same bootable state as before? With the special windows partitions for booting?
Update3
I assigned on the disks to a working W10 VM and it's showing up as Unallocated in W10 Disk Management.
Last edited: