Issues migrating VirtualBox Windows Server 2008R2 VM

W

wgshef

New Member
Jan 30, 2025
6
1
3
I'm trying to migrate a VirtualBox VM into ProxMox VE, and could use some help in figuring out how to get this accomplished.
VM is a Windows Server 2008R2. Before migrating, I removed the VB Guest Additions and ran the MergeIDE.bat file. I also changed the NIC to an E1000.
I converted the hard drive using VBoxManage: VBoxManage clonehd --format RAW <path to VM HDD.vdi> <destination file.img>
Running ProxMox 8.3.3 and VirtualBox Version 7.0.8 r156879 (Qt5.15.2)

I then created a ProxMox VM. Results from qm config for it are:
Code: 
root@pve:~# qm config 303
boot: order=ide0;ide2;net0
cores: 1
cpu: kvm64
ide0: local-lvm:vm-303-disk-0,size=50G
ide2: local:iso/virtio-win.iso,media=cdrom,size=709474K
machine: pc-i440fx-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1747104499
name: SQL2005-14
net0: e1000=BC:24:11:B8:F9:EC,bridge=vmbr0,firewall=1
numa: 0
ostype: win7
smbios1: uuid=9a491ffb-5ad9-4204-b5d0-ce53f6635a1b
sockets: 1
tags: sql;home-lab
vmgenid: 5647b92c-4de8-4f67-97bc-ba8bbd6627ed

I copied the .img file for the HDD, replacing the vm-303-disk-0 drive above. When I start the VM, I get the boot menu, then there is a quick BSOD and then it immediately reboots and starts over. It was so fast that I couldn't even start to read the BSOD - it was just a quick flash of blue. After many attempts, I was finally able to capture a screenshot of it:
ProxMox VB VM migration BSOD.jpg

I have tried multiple different processors for the VM (pentium, pentium3, kvm64, Nehalem, qemu32, qemu64, x86-64-V2, and they are all doing the same thing. The VM boots up fine in VirtualBox.

I greatly appreciate all your assistance in figuring out what needs to be done to get this working.
Additionally, how do you determine what processor to use for a VM? You would think there would be something like a wiki "for this OS, this is the processor that you should use".

Thanks,
Wayne
 
Hello wgshef! Windows error 0x0000007B means INACCESSIBLE_BOOT_DEVICE - see the Microsoft documentation. In other words, Windows has issues accessing your storage. Could you please try to see whether it helps using SATA instead of IDE?

wgshef said:
I have tried multiple different processors for the VM (pentium, pentium3, kvm64, Nehalem, qemu32, qemu64, x86-64-V2, and they are all doing the same thing. The VM boots up fine in VirtualBox.

I greatly appreciate all your assistance in figuring out what needs to be done to get this working.
Additionally, how do you determine what processor to use for a VM? You would think there would be something like a wiki "for this OS, this is the processor that you should use".
Click to expand...
This should be unrelated to your issue, but this is explained in the Proxmox VE documentation on CPU types. In general, you'll want either of the following:
  • Either set the CPU type to host to have the best performance, in case you don't need live migrations between nodes in a cluster, or in case all nodes in a cluster have the same CPU model and microcode
  • Or set the CPU type to the lowest generation model in your cluster - see QEMU CPU types and Intel/AMD CPU types. (Important: Live migrations between Intel and AMD host CPUs have no guarantee to work.)
 
  • Like
Reactions: _gabriel
You must log in or register to reply here.
Top Bottom