2,187
edits
Difference between revisions of "VMware Converter"
Jump to navigation
Jump to search
→Troubleshooting: Added Unexpected element tag
(→Converted VM boots to PSOD - STOP 7B: Added "VMX Hack") |
(→Troubleshooting: Added Unexpected element tag) |
||
| (One intermediate revision by the same user not shown) | |||
| 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. | ||
| Line 136: | Line 136: | ||
scsi0:0.fileName = "VM-Name.vmdk" | scsi0:0.fileName = "VM-Name.vmdk" | ||
scsi0:0.deviceType = "scsi-hardDisk" | scsi0:0.deviceType = "scsi-hardDisk" | ||
==== Unexpected element tag ==== | |||
* A general system error occurred: Unexpected element tag “ConvertManager” seen while parsing serialized DataObject of type converter.AgentInstanceContent at line7, column 63 while parsing return value of type converter.ServiceInstanceContent, version converter.version.version2 at line 7, columen 0 while parsing SOAP body at line 6, column 0 while parsing SOAP envelope at line 2, column 0 while parsing HTTP response for method retrieveConent on object of type converter.ServiceInstance at line 1, column 0 | |||
Caused by the VMware Converter utility from a previous attempt still existing on the server to be P2V'ed, uninstall the utility | |||
== Alternatives == | == Alternatives == | ||