2,187
edits
Difference between revisions of "VMware Converter"
Jump to navigation
Jump to search
→Troubleshooting: Converted VM boots to BSOD - STOP 7B
(→Unable to obtain hardware information for the selected machine: Added a couple of suggestions) |
(→Troubleshooting: Converted VM boots to BSOD - STOP 7B) |
||
| Line 84: | Line 84: | ||
* In Vista (and maybe Win7) run Converter as an Administrator | * In Vista (and maybe Win7) run Converter as an Administrator | ||
=== | === 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). For Win7 and Win2008 machines, prior to conversion... | |||
# Ensure that the LSI_SAS driver exists | |||
#* <code> C:\Windows\System32\Drivers\lsi_sas.sys </code> | |||
# Locate the following registry key | |||
#* <code> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS </code> | |||
# If it exists, with contents, change the following | |||
#* <code> Start </code> to <code> 0 </code> (would have been <code>3</code> originally) | |||
# If it doesn't exist with contents, import the key from a working Win7 or Win2008 VM | |||
# Reboot, and then reattempt | |||
For further info 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] | |||
== Alternatives == | |||
If VMware Converter is unable to P2V your machine (for example as of writing you can't P2V a Win2k8 R2 machine as the VSS interface has changed and VMware haven't released a new version yet), there are other (free) options | If VMware Converter is unable to P2V your machine (for example as of writing you can't P2V a Win2k8 R2 machine as the VSS interface has changed and VMware haven't released a new version yet), there are other (free) options | ||
# Use [http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx SysInternals Disk2vhd] to hot-clone a machines disk(s) to Microsoft format VHD files | # Use [http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx SysInternals Disk2vhd] to hot-clone a machines disk(s) to Microsoft format VHD files | ||
# Use [http://www.starwindsoftware.com/converter StarWind V2V Converter] to convert VHD file(s) to VMDK format (use sparse/thin (VI4 only) and iSCSI options) | # Use [http://www.starwindsoftware.com/converter StarWind V2V Converter] to convert VHD file(s) to VMDK format (use sparse/thin (VI4 only) and iSCSI options) | ||
# Upload the VMDK file(s) to an appropriate datastore (in a folder with the VM name) | # Upload the VMDK file(s) to an appropriate datastore (in a folder with the VM name) | ||
# Create a new VM, using the active/boot disk of the VMDK's just uploaded (if multiple disks, add others | # Create a new VM, using the active/boot disk of the VMDK's just uploaded (if multiple disks, add others separately after VM has been created) | ||
# Edit the VMX file to cater for the new VMDK's ?? | # Edit the VMX file to cater for the new VMDK's ?? | ||
# On first boot it may be | # On first boot it may be necessary to edit the registry to avoid a BSOD (change <code>REG_DWORD Start</code> to <code>0</code> in <code>HKLM\p2v\ControlSet001\services\LSI_SAS</code> (you need to boot using a recovery CD to be able to access the registry. | ||
For further info see http://sanbarrow.com/p2v2008r2.html | For further info see http://sanbarrow.com/p2v2008r2.html | ||
[[Category: VMware]] | [[Category: VMware]] | ||