Just wondering if anyone knows if there are any documented instances of someone being able to successfully re-inject the VirtIO drivers into a UEFI-based Windows VM?
At first, we thought it was just a VMware problem, but then we had the same issue happen on a native-AHV VM. The VM operates normally for weeks, with regular reboots, but randomly after a reboot, it bluescreens with an "Inaccessible Boot Device" error.
We haven't found a single "solution" that has actually fixed the problem. We can get the VM to boot into recovery mode, but none of the recovery options work. If we manually load up VirtIO driver from the command prompt (drvload vioscsi.inf) we can regain access to our drives, but adding the driver to the boot image via DISM does not help (dism /image:c:\ /add-driver /driver:vioscsi.inf). The server reboots to the same blue screen.
SFC doesn't help, neither do the standard bootrec options (i.e. bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd), nor does "bootsec /nt60 sys"
We've also tried the steps in: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000kAWeCAM with no luck.
We normally clone a template VM that was created on the cluster (native-AHV, not converted from another hypervisor) and the VirtIO drivers are still installed after a sysprep, but we’re switching to manually creating each VM from a Windows Server DC iso instead.
Any suggestions?
