Difference between revisions of "VMware Converter"

Jump to navigation Jump to search
m
→‎Troubleshooting: Section headings mixed up - fix
m (→‎Troubleshooting: Section headings mixed up - fix)
Line 87: Line 87:
This problem is caused by the converted OS being unable to find drivers for the boot device.  The conversion appears to complete successfully, but on booting the new VM it fails with a '''STOP: 0x0000007B''' blue screen of death (BSOD). Solutions for Windows 7 and Windows 2008 machines are below, see [http://kb.vmware.com/kb/1005208 VMware KB 1005208 - Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMware Converter] for details on how to fix on other operating systems
This problem is caused by the converted OS being unable to find drivers for the boot device.  The conversion appears to complete successfully, but on booting the new VM it fails with a '''STOP: 0x0000007B''' blue screen of death (BSOD). Solutions for Windows 7 and Windows 2008 machines are below, see [http://kb.vmware.com/kb/1005208 VMware KB 1005208 - Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMware Converter] for details on how to fix on other operating systems


=== Registry Hack ===
==== Registry Hack ====
Prior to running the P2V conversion, on the physical nmachine...
Prior to running the P2V conversion, on the physical nmachine...
# Ensure that the LSI_SAS driver exists
# Ensure that the LSI_SAS driver exists
Line 98: Line 98:
# Reboot, and then reattempt
# Reboot, and then reattempt


=== VMX Hack ===
==== VMX Hack ====
There are times when the registry hack (above) fails to prevent the STOP 7B BSOD.  In the situations I've seen, this is because the boot disk in the VM is attached via IDE rather than SCSI.  In which case you need to hack the VMX config file for the VM in order to represent the boot disk via SCSI.
There are times when the registry hack (above) fails to prevent the STOP 7B BSOD.  In the situations I've seen, this is because the boot disk in the VM is attached via IDE rather than SCSI.  In which case you need to hack the VMX config file for the VM in order to represent the boot disk via SCSI.


Navigation menu