VMware Converter 4.01: “Unable to obtain hardware information” or “Unable to determine Guest Operating System”
Posted by jpluimers on 2010/06/10
Sometimes you get an error message “Unable to obtain hardware information” or “Unable to determine Guest Operating System” when using VMware Converter 4.01.
This happens at least with VMware Converter 4.01 and converting x64 VM’s like “Windows 7” and “Windows Server 2008 R2” from ESXi 4 U1.
Others found out it also happens with some Linux VMs, I have not tried those yet.
A the VMware communitie, user wildblue posted a workaround:
Similar problem here – Windows 7 VM, converter gives the “Unable to obtain hardware information for the selected machine”
Log shows (I’m assuming this is the important part)
error 'ManagedMachineDataConnectionLogger'] Cannot query source HW info: vmodl.fault.SystemErrorExport Wizard through VI Client gives ‘Unable to determine Guest Operating System’
Changing the VM’s settings and making the Operating System something other than Win 7 seems to work. Export to OVF works too. Guess those are your work arounds until the next verion of converter.
So the trick is these steps:
- Write down the Guest Operating System type
(You can perform step 1, 2 and 4 by pressing “Edit Settings” in the VM, in the dialog then go to the “Options” tab. ) - Change your VM configuration Guest Operating System type to a similar processor type (keep 64-bit or 32-bit) for a lower release of the OS (Windows 7 -> Vista -> XP, etc)
- Convert your VM; if it fails, go back to step 2
- Restore the VM configuration Guest Operating System type to the original saved in step 1
Piece of cake when you know it :-)
–jeroen
via VMware Communities: Unable to obtain hardware information ….
The Wiert Corner - irregular stream of stuff 
sam said
This method worked to get me past the first error in VCenter converter standalone. However I wasn’t then able to select the VM hard drives individually (by volume as opposed to by disk) to deploy to the new VM.
Removing and re-adding the source VM to the inventory did not fix it for me either.
jpluimers said
Did you get it fixed this time?
Liliana Forero said
I get this error message “Unable to determine guest operating system” with a WINDOWS98 Virtual machine. I change the version of the virtual machine, but it did not work. Any help?.
jpluimers said
Sorry, I have no idea and would start with a search like this: ‘Unable+to+determine+guest+operating+system’+’windows+98’
Windows 2008 R2 64 bit V2V conversion fails with “Unable to determine Guest Operating System” error « Virtualization Guide said
[…] to: https://wiert.me/2010/06/10/vmware-converter-4-01-unable-to-obtain-hardware-information-or-unable-to-… Share this:FacebookLinkedInMoreTwitterLike this:LikeBe the first to like this […]
Carl Green said
Removing from inventory and adding it back worked for me. OK…. that makes no sense. But good to know.
jpluimers said
Thanks for the tip.
You receive the error message “Unable to determine Guest Operating System” when trying to move a VM using VMware Converter | The IT Bod said
[…] Found this excellent solution here https://wiert.me/2010/06/10/vmware-converter-4-01-unable-to-obtain-hardware-information-or-unable-to-… […]
jpluimers said
You are most welcome (:
Ovidiu said
For me just rebooting the ESXi host did the trick.
James Rogers said
Thanks, this worked for me! Like others, I changed the description of a Windows Server 2008 R2 64-bit machine to Windows Server 2008 64-Bit and it converted just fine.
EJH said
Converted a Win 64bit 2008 R2 to Win 64bit 2008. Works now! Thanks!
neil said
Thanks DanyBoy. Same worked for me
DanyBoy said
What worked for me is, that I removed the VM from the inventory and re-add it. converter was then able to see the information it needed
Harry said
Worked for me too…Thanks!!
my 2010 blog in review « The Wiert Corner – irregular stream of Wiert stuff said
[…] VMware Converter 4.01: “Unable to obtain hardware information” or “Unable to deter… June 2010 11 comments 4 […]
IL said
Could you provide a direct link for VMware vCenter Converter? It seems download part of vmware.com site in maintenance mode.
IL said
VMWare site came back but and there are direct links for VMware Converter 3.0 only:
http://download3.vmware.com/software/converter/VMware-p2v-3.0.0-39557.exe
http://download3.vmware.com/software/converter/VMware-converter-3.0.1-44840.exe
http://download3.vmware.com/software/converter/VMware-converter-3.0.2-59994.exe
http://download3.vmware.com/software/converter/VMware-converter-3.0.2u1-62456.exe
http://download3.vmware.com/software/converter/VMware-converter-3.0.3-89816.exe
As for VMware vCenter Converter 4.0 you should register to obtain temporal direct links. I guess no use to place it here :)
jpluimers said
Thank you!
–jeroen
IL said
Another link for the sake of those struggling with Windows 2000 :)
VMware drops support for Windows NT and 2000 in vCenter Converter 4.3
http://virtualization.info/en/news/2010/10/vmware-drops-support-for-windows-nt-and-2000-in-vcenter-converter.html
markus said
worked for me, too. Great tip, thanks!
TimmyC said
Worked for me Three! Convertying Win2008 R2, set down to Win2008, no problem, Thanks man!
Now, can VMWARE get off their apparently dead asses and UPDATE THE CONVERTER!!!!!
Can I get a HELL YEAH!
adc11 said
Doesn’t work for me, gives me that message when trying to convert Win7 64-bit or Win2008 R2, no matter what I set the Guest OS type to. Works fine for converting Linx 64-bit and WinXP 32-bit.
adc11 said
Update: I restarted Converter and then it worked with OS type set to “Other 32-bit”
Holland said
Worked for me! Just changed the VM to Windows 2008 64bit and it converted! Awesome tip!
Muhammad Adnan said
The Solution Also Worked for me. Windows 2008 R2 Change it to Windows 2008.
Jackson said
The solution worked for me while I try to convert a Windows Server 2008 R2 x64. I changed it to Windows Server 2008 x64 and the process continues. Thank you!