did an esxi import
woudn't boot - BSOD x7b or whatever it is - inaccessible boot device.
tried the various disk controllers.
the only one that would boot the system was the MegaRAID SAS 8708EM2.
*however* I had loads of freakin' weird things going on. The os (server 2012 r2) booted fine, but I couldn't uninstall any apps.
Application event log showed lots of 'could not access file. file not found' issues, very odd.
System event log showed lots of write failure disk removed, error flushing cache stuff pretty much exactly like our famous "[vioscsi] Reset to device ... system" issue ( https://forum.proxmox.com/threads/r...system-unresponsive.139160/page-9#post-713581 ) and ( https://github.com/virtio-win/kvm-guest-drivers-windows/issues/623#issuecomment-1875076293 ).
I'm trying to remember how I fixed this now. It was last week. I think I probably did something like added another disk & controller, booted to install drivers, then removed the boot disk and added it back in over sata rather than scsi or virtio, to get a properly working system, then same process to migrate across to virtio. I was trying to install virtio but none of the kvm drivers would install, citing ceritificate hash errors. This could just be a 2012r2 issue though. I somehow got out of this mess then did an in place upgrade to 2022 and was back on track with virtio.
I know I began on sata as per the esxi import guidance and it would not boot at first though, which is why I ended up on MegaRAID SAS.
just sharing FYI. Might be strangely related to the viostor problems.
I suspect it could be a clash between the VMWare guest addons (drivers) that were still installed, and the KVM emulated hardware.
woudn't boot - BSOD x7b or whatever it is - inaccessible boot device.
tried the various disk controllers.
the only one that would boot the system was the MegaRAID SAS 8708EM2.
*however* I had loads of freakin' weird things going on. The os (server 2012 r2) booted fine, but I couldn't uninstall any apps.
Application event log showed lots of 'could not access file. file not found' issues, very odd.
System event log showed lots of write failure disk removed, error flushing cache stuff pretty much exactly like our famous "[vioscsi] Reset to device ... system" issue ( https://forum.proxmox.com/threads/r...system-unresponsive.139160/page-9#post-713581 ) and ( https://github.com/virtio-win/kvm-guest-drivers-windows/issues/623#issuecomment-1875076293 ).
I'm trying to remember how I fixed this now. It was last week. I think I probably did something like added another disk & controller, booted to install drivers, then removed the boot disk and added it back in over sata rather than scsi or virtio, to get a properly working system, then same process to migrate across to virtio. I was trying to install virtio but none of the kvm drivers would install, citing ceritificate hash errors. This could just be a 2012r2 issue though. I somehow got out of this mess then did an in place upgrade to 2022 and was back on track with virtio.
I know I began on sata as per the esxi import guidance and it would not boot at first though, which is why I ended up on MegaRAID SAS.
just sharing FYI. Might be strangely related to the viostor problems.
I suspect it could be a clash between the VMWare guest addons (drivers) that were still installed, and the KVM emulated hardware.
Last edited: