Description of problem:
After converting Windows 2008 R2 physical machine, VM fails to start with error code: 0x0000007B. The booting was not working even with ide disk. The registry value for intelide was 3. But it was giving same error when this was changed to 0. The VM was able to boot when the following registry values was changed to 0.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\pciide
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\msahci
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iaStorV
HKEY_LOCAL_MACHINE\System\ControlSet001\Services\atapi
Not sure which one worked. However changing the disk to virtio is still giving the same BSOD error even after installing all the drivers within the guest.
Version-Release number of selected component (if applicable):
libguestfs-1.32.7-3.el7.x86_64
How reproducible:
Unknown
Steps to Reproduce:
1. Convert a physical Windows 2008 R2 using virt-p2v
2. VM fails to boot with BSOD
Actual results:
VM was not able to boot with BSOD error 0x0000007B
Expected results:
VM should be able to boot without manual intervention
Additional info:
Comment 3Richard W.M. Jones
2017-01-02 22:43:14 UTC
On a further look at the output, I've spotted a warning:
virt-v2v: warning: there are no virtio drivers available for this version
of Windows (6.1 x86_64 Server). virt-v2v looks for drivers in
/usr/share/virtio-win
The guest will be configured to use slower emulated devices.
Please install the virtio-win package on the conversion server
and try the whole conversion again.
Issue was not reproducible when the virtio drivers was installed in the conversion server. The same physical machine was imported without any issue with the virtio drivers.
Comment 11Richard W.M. Jones
2017-02-16 13:37:10 UTC
Closing per comment 10. If you try this again, please make sure
the customer has the virtio-win drivers.