P2V Windows 7 - Yet another 0x0000007B problem

[VriM]

Hello,

My current (and only) desktop computer is an aging Windows 7, which I'd like to put on my Proxmox before I transition to more modern hardware.

I've read around a bit about this whole P2V thing and tinkered with it, but still keep getting those dreaded 0x0000007B BSODs on boot, when the orb thingies start swirling.
I like to think I know what the problem is, but I'm wary about the usual solutions...

But first things first:
I went the Disk2vhd way to export my C: drive, mostly following Michael Sage's guide (the main difference being that I converted the vhdx outside of where the images are, and imported it with qm importdisk).

My CPU is an Intel i7 3770K, so I went with IvyBridge (I even tried some more generic ones, to no avail).

When I tinker a bit more and set vm-201-disk-1 to virtio, I can load the proper drivers and the drive can be seen.
Obviously the System Recovery tools won't actually fix anything, but at least it confirms that I'm missing those drivers in my OS.

I'm aware of MergeIDE and the like, and that's were I'm being cautious...
I won't pretend I understand exactly what it does, but checking at the .reg file, it sets the PCCIde Start key to 0, while my current configuration has it to 3 (and MSAHCI is 0, in case that's relevant).
The last time I did tamper with AHCI was like a decade ago, and I couldn't access my OS afterwards, that's why I'm extra-careful.

Can/should the virtio drivers somehow be loaded in my current bare-metal system beforehand, or will it mess my OS up ?
Is MergeIDE the only alternative (I'd rather steer clear of sysprep) ?

 

[not-the-admin]

Newbie to Proxmox, but I just figured out this problem for me, after combing tons of pages here and elsewhere.
I was able to access my windows drive through the troubleshooting tools after the BSD, so I knew the drive was fine. I finally found this LINK which explained how to enable specific services for hardware controllers; and after a few tries, I solved my problem. For me, all the Atapi, intelide and LSI_SAS services were already started, but there was a note that said "If you had set your SATA controller mode to AHCI before this error occurred, you should also set Start = 0 in the msahci section." I missed it the first time, but when I set that to '0', BAM, it booted right up.

Good luck.

 

[Kingneutron]

https://search.brave.com/search?q=w...summary=1&conversation=e068ff613734d9f383a6ba

EDIT: Win7 reached EOL 5 years ago. You should have done a P2V back when the tools for it were fresh. Hope you've kept all your original install ISOs and apps, or you're going to be doing a lot of searching for old versions.

AOMEI may still have a version available that will do P2V, but you might have to use rescatux afterward to fix boot. (This is from my p2v VM notes) - Veeam may also have a viable bare-metal backup/restore for it that does hardware injection, but it's chancy. You will also need to uninstall any chipset-specific software from the VM to avoid BSODs.

https://www.supergrubdisk.org/

Worst case scenario, download a Win7 ISO and fresh-install to VM, then reinstall your apps and migrate docs + data over. Then when everything is configured and working, BACK IT UP.