No boot baremetal windows to qcow2 converstion

[hardbrocklife]

So Im trying to do the whole convert an existing baremetal windows installation to a KVM. I have been following this tutorial:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE


I just had to use different file locations because my PVE storage was too small for 240gb windows-server.qcow2 file.

I used the command below, /mnt/bigaboys/Gaming-Server3/Gaming-Server3.vmdk being the location of the vmdk file on my mounted NFS, and /mnt/pve/bigaboy/images/105 being the location that I had to make the conversion to due to the limited storage at /var/lib/vz/images/ on /PVE.

I am not about to fool with backing up all the VMs and resizing stuff on the SSD disk im using to host the VMs. Im too ignorant for that at the moment.

command:

qemu-img convert -f vmdk /mnt/bigaboys/Gaming-Server3/Gaming-Server3.vmdk -O qcow2 /mnt/pve/bigaboy/images/105/windows-server.qcow2

Everything seem to have executed properly.

My 105 config file that I updated according to the tutorial:

GNU nano 7.2                                    /etc/pve/local/qemu-server/105.conf                                             
boot: order=ide0;ide2;net0
cores: 4
cpu: x86-64-v2-AES
ide0: bigaboy:105/windows-server.qcow2
ide2: none,media=cdrom
machine: pc-i440fx-8.0
memory: 16000
meta: creation-qemu=8.0.2,ctime=1690048480
net0: e1000=62:D6:27:6D:93:22,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=32958991-5bf4-4426-9486-5745160abe6a
sockets: 1
vmgenid: 57d36a5a-faae-4cb3-a489-47374dffa59a

And the console screen when I try to boot:


Any help would be appreciated as I like to learn. I did test the vmdk in vmware player on the baremetal windows installation, to ensure driver/device whatever did the thing.

I cant think of any other information to add that may be useful. If I need to provide anything simply ask.

 

[alexskysilk]

check your boot order (under vmid->options.)

Since you mapped your boot drive to ide0, make sure thats in there.

 

[hardbrocklife]

ide0 is first, which I am assuming is correct:



Based on your statement Im assuming that you believe the issue is due to the location of the windows image? It cant find it or see essentially?

 

[hardbrocklife]

Not sure if I should edit the previous comment or add another with additional information...

If I ls the dir where the VM is at, I get this

root@pve:/mnt/pve/bigaboy/images# ls
100  105

100 is my Truenas Scale VM, 105 being the folder for my windows VM.

If I go to look at the TNS vmid -> options I see this:



The fact that vm-100-disk-0.qcow2 is in /mnt/pve/bigaboy/images/100 and windows-server.qcow2 is in /mnt/pve/bigaboy/images/105 but ide0 is not in the boot order for VMID100/TNS makes me think I am missing some sort of linking of something somewhere...

This is my conf for VMID100:

GNU nano 7.2                                             /etc/pve/local/qemu-server/100.conf                                                     
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
ide2: local:iso/TrueNAS-SCALE-22.12.3.1.iso,media=cdrom,size=1713888K
memory: 8192
meta: creation-qemu=8.0.2,ctime=1688001756
name: TNS
net0: virtio=7A:0A:7F:19:93:42,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-100-disk-0,iothread=1,size=32G
scsi1: bigaboy:100/vm-100-disk-0.qcow2,iothread=1,size=12000G
scsi2: bigaboy2:100/vm-100-disk-0.qcow2,iothread=1,size=12000G
scsihw: virtio-scsi-single
smbios1: uuid=a4e89f9a-6344-4008-9385-2ee7ed4026ca
sockets: 1
unused0: littleboy:100/vm-100-disk-0.qcow2
vmgenid: 09d9945c-76df-4cab-b429-76385b3a0a61

Should I make the boot order for VMID105 the same as VMID100?

I am not used to the layering of files within VM directories within global directories for the host, but Im slowly adapting.

Does my reasoning make sense, or am I missing something?

 

[alexskysilk]

why are you mapping your disk for vm105 to 100? this isnt gonna work for any purpose. Make sure that you dont have anything for vm-100* associated with vm105 and vice versa. reboot to make sure as relevent.

next, was your original windows install bios or UEFI? make sure to match the system types, and make sure there's an efi partition in case of the latter. If it still doesnt boot, something probably went wrong in the disk conversion.

 

[hardbrocklife]

why are you mapping your disk for vm105 to 100? this isnt gonna work for any purpose. Make sure that you dont have anything for vm-100* associated with vm105 and vice versa. reboot to make sure as relevent.

next, was your original windows install bios or UEFI? make sure to match the system types, and make sure there's an efi partition in case of the latter. If it still doesnt boot, something probably went wrong in the disk conversion.

Who is mapping 100 to 105? You must have me confused with someone else.

What I was explaining is that the VM for both of them is in the same location. The same directory. What I was pointing out is that if tje VM for 100 and the VM for105 are in the same directory, it makes sense that there boot drives should match. I was pointing out they do not, so I'm going to try that next.

I am going to double check the boot type though. That could easily be it. The vmdk was made with a UEFI system, so that could potentially be the issue.

I'll report back tomorrow.