ESXi to Proxmox migration Windows 7 BSOD 0x0000007B

[robse]

Hi all,

I have an old ESXi 6.0 test environment I would like to migrate to Proxmox VE. I have added the ESXi as a storage and imported a Windows 7 VM from ESXi. When I boot the VM in the Proxmox environment I get a blue screen with stop code 0x0000007B. I have tested another Windows 7 VM and get the same error.

The following settings I have used for the import:





The VM has the following configuration:



Do I need to prepare something first before the import or do i have to apply some configurations after the import?

Thank you in advance!

 

[Bingo600]

I'm a total beginner , I have no idea if your BSOD is Storage driver related

But stumbled across this one

https://dannyda.com/2023/03/07/how-...rom-vmware-esxi-6-x-and-up-to-proxmox-ve-pve/

A.11 Once done, we will see it in the PVE web gui, make necessary changes, e.g. CPU, RAM, HDD properties, add network device etc. if necessary.

Note: For Windows VMs, we need to change SCSI controller to STAT controller for first time boot, after installing virtio driver, we can switch back to SCSI again from PVE web gui or command line.

 

[sw-omit]

Indeed, it's a bit more tricky to use scsi right away for windows.
I've recently migrated a couple dozen servers (mostly windows) from ESXi to Proxmox, and from the importer the steps I had different from your screenshot are:

• CPU-type the v3 variant (but that depends on your CPU-type, v2 is good/safe, v3 is a bit more modern)
• Are you sure the default storage is the correct one btw (given that the name is "backup")?
• Under Advanced I check the "prepare for VirtIO-SCSI", so that it swaps both the disk-type and scsi-controller (more on that later on)
• Network Interface Model "VirtIO (paravirtualized)"

Other then that, the other steps I do:
While on ESXi, save the network-config if static, install the virtio-tools [1] [2] and then remove the vmware-tools.
After I've migrated and booted in windows, set the network-config again if static, then add a second (temporary) scsi-drive, reboot, shut-down (do not shutdown right away, it needs to see the temp scsi-drive during boot once) then detach the sata/ide drive and re-attach the drive as scsi, boot and you should be good.

[1] https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
[2] https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso (direct iso link for latest stable)
[3] https://fedorapeople.org/groups/vir...o/virtio-win-0.1.189-1/virtio-win-0.1.189.iso (version recommended for Windows 8 and lower)

 

[robse]

Indeed, it's a bit more tricky to use scsi right away for windows.
I've recently migrated a couple dozen servers (mostly windows) from ESXi to Proxmox, and from the importer the steps I had different from your screenshot are:

• CPU-type the v3 variant (but that depends on your CPU-type, v2 is good/safe, v3 is a bit more modern)
• Are you sure the default storage is the correct one btw (given that the name is "backup")?
• Under Advanced I check the "prepare for VirtIO-SCSI", so that it swaps both the disk-type and scsi-controller (more on that later on)
• Network Interface Model "VirtIO (paravirtualized)"

Other then that, the other steps I do:
While on ESXi, save the network-config if static, install the virtio-tools [1] [2] and then remove the vmware-tools.
After I've migrated and booted in windows, set the network-config again if static, then add a second (temporary) scsi-drive, reboot, shut-down (do not shutdown right away, it needs to see the temp scsi-drive during boot once) then detach the sata/ide drive and re-attach the drive as scsi, boot and you should be good.

[1] https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
[2] https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso (direct iso link for latest stable)
[3] https://fedorapeople.org/groups/vir...o/virtio-win-0.1.189-1/virtio-win-0.1.189.iso (version recommended for Windows 8 and lower)

Thanks for your response. I have already tried "prepare for VirtIO-SCSI" with the same result (BSOD). When I try to install the virtio drivers [3] the installer says that the OS must be Windows 8 or higher.

The name of the storage is correct. It is just a test environment.

 

[sw-omit]

Ah, the installer might still be broken for that version [1] but the drivers in the seperate folders are there, so you should still be able to install it through there, or try one of the other (old) versions and try your luck.
You might also have to try with lower machine-versions (hardware tab, machine, keep to the i440fx, but try with lower version-numbers, or try adding the disk's as IDE even. With these outdated / unsupported systems, sometimes it's just a bunch of trial-and-error.

One other thing you could try, is to first try to get a clean windows 7 machine to run on proxmox, see what settings work for that machine, so you at least have a baseline of where to start, for that also take a look at the old best practises [2]

[1] https://askubuntu.com/questions/1310440/using-virtio-win-drivers-with-win7-sp1-x64
[2] https://pve.proxmox.com/wiki/Windows_7_guest_best_practices

 

[simonhoffmann]

What happens if you change the disks to SATA instead of SCSI or VirtIO?

 

[Falk R.]

Hi all,

I have an old ESXi 6.0 test environment I would like to migrate to Proxmox VE. I have added the ESXi as a storage and imported a Windows 7 VM from ESXi. When I boot the VM in the Proxmox environment I get a blue screen with stop code 0x0000007B. I have tested another Windows 7 VM and get the same error.

The VM has the following configuration:

View attachment 73177

Do I need to prepare something first before the import or do i have to apply some configurations after the import?

Thank you in advance!

The BSOD 0x0000007B also states that the OS disk was not found. This is quite normal with Windows and VirtIO SCSI if the drivers have not yet been installed.
So next time mount the disk directly via IDE or SATA.
In addition, add a dummy SCSI disk to the VM.
Then install the VirtIO drivers and then shut down Windows again.
Detach and delete the SCSI disk.
Detach OS disk and reattach with SCSI.

The circumstance with the dummy disk must be with Windows, otherwise Windows will not install the driver as bootable.

 

[Magnus-mercer]

Try changing the disk controller in the VM configuration on Proxmox to match the one used in ESXi (likely LSI Logic or IDE). Or like the reply above, change the disks format?

 

[Falk R.]

Try changing the disk controller in the VM configuration on Proxmox to match the one used in ESXi (likely LSI Logic or IDE). Or like the reply above, change the disks format?

Nothing changes on the hard disk, you just connect it to another controller that Windows can handle.