VMware Converter - Revision history

Sstrutt: /* Troubleshooting */ Added Unexpected element tag

2016-12-22T16:31:22Z

Troubleshooting: Added Unexpected element tag

← Older revision		Revision as of 16:31, 22 December 2016
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 ==

Sstrutt: /* Troubleshooting */ Section headings mixed up - fix

2012-05-03T10:38:42Z

Troubleshooting: Section headings mixed up - fix

← Older revision		Revision as of 10:38, 3 May 2012
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.

Sstrutt: /* Converted VM boots to PSOD - STOP 7B */ Added "VMX Hack"

2012-05-03T10:37:34Z

Converted VM boots to PSOD - STOP 7B: Added "VMX Hack"

@@ Line 85: / Line 85: @@
 === 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...
+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
 # Ensure that the LSI_SAS driver exists
 #* <code> C:\Windows\System32\Drivers\lsi_sas.sys </code>
@@ Line 96: / Line 98: @@
 # 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]
+=== VMX Hack ===
 == Alternatives ==

Sstrutt: /* Troubleshooting */ Converted VM boots to BSOD - STOP 7B

2012-05-01T09:43:06Z

Troubleshooting: Converted VM boots to BSOD - STOP 7B

← Older revision		Revision as of 09:43, 1 May 2012
Line 84:		Line 84:
	* In Vista (and maybe Win7) run Converter as an Administrator		* In Vista (and maybe Win7) run Converter as an Administrator

	=== ~~Other Options~~ ===		=== 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 ~~seperatley~~ after VM has been created)		# 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 ~~nessessary~~ 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 ~~usind~~ a recovery CD to be able to access the registry.		# 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]]

Sstrutt: /* Unable to obtain hardware information for the selected machine */ Added a couple of suggestions

2011-03-22T14:03:19Z

Unable to obtain hardware information for the selected machine: Added a couple of suggestions

← Older revision		Revision as of 14:03, 22 March 2011
Line 78:		Line 78:

	Some suggestions from various sources...		Some suggestions from various sources...
			* Try migrating the VM to another ESX
			* Try re-registering the VM in the vCentre inventory
	* Network connectivity problems between the server and client (ie the vCentre that Converter is running from, and the client machine that Converter is connecting to)		* Network connectivity problems between the server and client (ie the vCentre that Converter is running from, and the client machine that Converter is connecting to)
	* Try changing the VM's OS to ''Other'' (32bit or 64bit), migrate and then change the OS back to what it really is.		* Try changing the VM's OS to ''Other'' (32bit or 64bit), migrate and then change the OS back to what it really is.

Sstrutt: /* Troubleshooting */ Added "Unable to determine guest operating system"

2010-09-02T14:45:11Z

Troubleshooting: Added "Unable to determine guest operating system"

← Older revision		Revision as of 14:45, 2 September 2010
Line 71:		Line 71:

	== Troubleshooting ==		== Troubleshooting ==
			=== Unable to determine guest operating system ===
			Try re-registering the source VM in its vCentre

	=== Unable to obtain hardware information for the selected machine ===		=== Unable to obtain hardware information for the selected machine ===
	Unfortunately this is generic error and can be triggered by a rich variety of reasons. You'll probably need to ''Export diagnostic details...'' and then trawl through the logs to get a better picture, though there's no guarantee that this will be in any way illuminating.		Unfortunately this is generic error and can be triggered by a rich variety of reasons. You'll probably need to ''Export diagnostic details...'' and then trawl through the logs to get a better picture, though there's no guarantee that this will be in any way illuminating.

Sstrutt: /* Unable to obtain hardware information for the selected machine */ Typo and formatting

2010-09-02T13:14:02Z

Unable to obtain hardware information for the selected machine: Typo and formatting

← Older revision		Revision as of 13:14, 2 September 2010
Line 72:		Line 72:
	== Troubleshooting ==		== Troubleshooting ==
	=== Unable to obtain hardware information for the selected machine ===		=== Unable to obtain hardware information for the selected machine ===
	Unfortunately this is generic error and can be triggered by a rich variety of reasons. You'll probably need to ''Export diagnostic details...'' and then trawl through the logs to get a better picture, though there's no ~~gaurantee~~ that this will be in any way illuminating. Some suggestions from various sources...		Unfortunately this is generic error and can be triggered by a rich variety of reasons. You'll probably need to ''Export diagnostic details...'' and then trawl through the logs to get a better picture, though there's no guarantee that this will be in any way illuminating.

			Some suggestions from various sources...
	* Network connectivity problems between the server and client (ie the vCentre that Converter is running from, and the client machine that Converter is connecting to)		* Network connectivity problems between the server and client (ie the vCentre that Converter is running from, and the client machine that Converter is connecting to)
	* Try changing the VM's OS to ''Other'' (32bit or 64bit), migrate and then change the OS back to what it really is.		* Try changing the VM's OS to ''Other'' (32bit or 64bit), migrate and then change the OS back to what it really is.

Sstrutt: Created "Troubleshooting" and made "Other Options" a child of it

2010-09-02T13:13:07Z

Created "Troubleshooting" and made "Other Options" a child of it

← Older revision		Revision as of 13:13, 2 September 2010
Line 68:		Line 68:
	#* Run now! Its bound to fail as a scheduled task! Click '''Next'''		#* Run now! Its bound to fail as a scheduled task! Click '''Next'''
	# '''Ready to Complete'''		# '''Ready to Complete'''
	#* Leave ''Power on the new virtual ~~amchine~~ after creation'' checkbox cleared, then click '''Finish'''		#* Leave ''Power on the new virtual machine after creation'' checkbox cleared, then click '''Finish'''

	== Other Options ==		== Troubleshooting ==
			=== Unable to obtain hardware information for the selected machine ===
			Unfortunately this is generic error and can be triggered by a rich variety of reasons. You'll probably need to ''Export diagnostic details...'' and then trawl through the logs to get a better picture, though there's no gaurantee that this will be in any way illuminating. Some suggestions from various sources...
			* Network connectivity problems between the server and client (ie the vCentre that Converter is running from, and the client machine that Converter is connecting to)
			* Try changing the VM's OS to ''Other'' (32bit or 64bit), migrate and then change the OS back to what it really is.
			* In Vista (and maybe Win7) run Converter as an Administrator

			=== Other 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		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

Sstrutt: /* Other Options */ Elaborated some steps in procedure

2010-07-29T12:42:14Z

Other Options: Elaborated some steps in procedure

← Older revision		Revision as of 12:42, 29 July 2010
Line 72:		Line 72:
	== Other Options ==		== Other 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		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 ~~disks~~ 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 ~~files~~ to VMDK's		# 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)
	# Create a new VM, ~~then upload~~ the VMDK ~~files~~		# Upload the VMDK file(s) to an appropriate datastore (in a folder with the VM name)
	# Edit the VMX file to cater for the new VMDK's		# Create a new VM, using the active/boot disk of the VMDK's just uploaded (if multiple disks, add others seperatley after VM has been created)
			# Edit the VMX file to cater for the new VMDK's ??
	# On first boot it may be nessessary 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 usind a recovery CD to be able to access the registry.		# On first boot it may be nessessary 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 usind a recovery CD to be able to access the registry.

Sstrutt: Fixed typos

2010-07-28T13:15:38Z

Fixed typos

← Older revision		Revision as of 13:15, 28 July 2010
Line 1:		Line 1:
			==Overview==
	VMware Converter clones an existing physical (or virtual) machine into a new virtual machine.		VMware Converter clones an existing physical (or virtual) machine into a new virtual machine.
	# A new VM is created		# A new VM is created
Line 75:		Line 76:
	# Create a new VM, then upload the VMDK files		# Create a new VM, then upload the VMDK files
	# 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 nessessary to edit the registry to avoid a BSOD (change <REG_DWORD Start</code> to </code> in <code>HKLM\p2v\ControlSet001\services\LSI_SAS</code> (you need to boot usind a recovery CD to be able to access the registry.		# On first boot it may be nessessary 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 usind 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]]