2,187
edits
Difference between revisions of "VMware Converter"
Jump to navigation
Jump to search
→Converted VM boots to PSOD - STOP 7B: Added "VMX Hack"
(→Troubleshooting: Converted VM boots to BSOD - STOP 7B) |
(→Converted VM boots to PSOD - STOP 7B: Added "VMX Hack") |
||
| Line 85: | Line 85: | ||
=== Converted VM boots to PSOD - STOP 7B === | === Converted VM boots to PSOD - STOP 7B === | ||
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). | 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 === | |||
Prior to running the P2V conversion, on the physical nmachine... | |||
# Ensure that the LSI_SAS driver exists | # Ensure that the LSI_SAS driver exists | ||
#* <code> C:\Windows\System32\Drivers\lsi_sas.sys </code> | #* <code> C:\Windows\System32\Drivers\lsi_sas.sys </code> | ||
| Line 96: | Line 98: | ||
# Reboot, and then reattempt | # Reboot, and then reattempt | ||
=== 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. | |||
# Shutdown the VM, and identify where the VMX config file is located | |||
#* To find the VMX: | |||
#*# Right-click over the VM and select '''Edit Settings...''' | |||
#*# Go to the '''Options''' tab | |||
#*# Inspect the '''Virtual machine Configuration File''' field | |||
# Remove the VM from the inventory (right-click, '''Remove from Inventory''') | |||
# Edit the VMX file | |||
#* Either download the VMX using Datastore Browser, and in order to edit locally. Rename the original file to <code><VM Name>.vmx.orig</code> | |||
#* Or SSH to the ESX and edit directly (create a copy of the config file 1st!) | |||
# Look for all config lines starting with <code>ide</code> (they needn't be all together in the same place) | |||
# Update as per the examples below, and save the VMX | |||
# Browse the datastore to the edited VMX, and right-click to '''Add to Inventory''' to re-add the VM into vCentre | |||
#* If the import fails, restore the original VMX file and try again, you may have made a mistake in the config (you may have missed some lines in the jumbled up config file) | |||
# Double check the disk config of the VM, then power on | |||
#* If the power-on fails, remove VM from the inventory again, restore the original VMX file and try again, you may have made a mistake in the VMX config file | |||
Original contents of VMX file... | |||
ide0:0.present = "TRUE" | |||
ide0:0.fileName = "VM-Name.vmdk" | |||
ide0:1.present = "TRUE" | |||
ide0:1.clientDevice = "TRUE" | |||
ide0:1.deviceType = "cdrom-raw" | |||
ide0:1.startConnected = "FALSE" | |||
New contents of VMX file... | |||
ide0:0.present = "TRUE" | |||
ide0:0.clientDevice = "TRUE" | |||
ide0:0.deviceType = "cdrom-raw" | |||
ide0:0.startConnected = "FALSE" | |||
scsi0.present = "true" | |||
scsi0.sharedBus = "none" | |||
scsi0.virtualDev = "lsisas1068" | |||
scsi0:0.present = "true" | |||
scsi0:0.fileName = "VM-Name.vmdk" | |||
scsi0:0.deviceType = "scsi-hardDisk" | |||
== Alternatives == | == Alternatives == | ||