Converter Unable To Obtain Hardware Information
May 29, 2013 With Converter 5.1 Build 1087880. Unable to obtain hardware information for the. Unable to obtain hardware information. Unable to obtain hardware information for the selected machine. This issue occurs when VMware vCenter Converter Standalone is installed on a source physical machine. Unable to obtain hardware information for the selected machine. This issue occurs when VMware vCenter Converter Standalone is installed on a source physical machine.
I am receiving the message 'Unable to obtain hardware information for the selected machine' when trying to convert a VMWare Server VM (Ubuntu-64bit) to ESXi. I get this message when trying to select the source type in VMWare Standalone Converter 5.0 I tried the VMWare forums and see a lot of suggestions for olderconverter versions most of which are trying to fool the converter by changing the.vmx file Operating System line to something else. I tried this already using several different OS suggestions found and it did not work.
I don't have VMWare Server installed anywhere anymore to troubleshoot but can do this if there isn't a quicker answer within converter. I exported the log files too but there are a ton of files and was not sure which I should be looking.
As I've posted previously, I work in a HyperV environment. Recently started playing with ESXi for personal knowledge. Wanted to run some tests on V2V conversion. Here's my equipment 1 - HyperV (Standard 2008R2 w/HyperV role) 1 - ESXi (Currently in trial mode, but will apply free license after trial) 4 - VM's, 1 w/XP, 1 w/Vista, 1 w/Win7, and 1 w/Win8 And here's my process so far: Installed converter in client-server mode on another server Installed converter agent on XP VM, c ompleted HOT conversion from HyperV to VMWare - worked no problem Installed converter agent on Vista, Win7 and Win8 VM's Received error 'Unable to contact the specified host.'
When trying to convert as 'Powered-on Machine' (followed same process as XP machine) from these 3 VM's Tried to connect to HyperV server, same error, installed Converter agent, and it connects, tells me I need to power down the VM's, so I do but when I t ry to select any of the 3 problem VM's I receive the error 'Unable to obtain hardware information for the selected machine.' Any ideas would be useful.
You've been most helpful. Started the conversion on the Vista and Win7 machines, though I'm still getting the hardware error on with Win8, disabled firewall and lowered UAC all the way (same as the Win7) Though if thats the only machine I need to complete manually, I can always convert the vhd manually. Might be an idea anyways just to know how to complete that process. Then try to reverse the conversion from ESXi back to HyperV (though I'm going to upgrade to Server 2012, been playing with HyperV R3 at the office and I'm getting a bit excited about whats going to happen. (I find it's better to know how to do it before you actually need to do it, so if worst comes to worst I'm already prepared).
Jody5052 wrote: You've been most helpful. Started the conversion on the Vista and Win7 machines, though I'm still getting the hardware error on with Win8, disabled firewall and lowered UAC all the way (same as the Win7) Though if thats the only machine I need to complete manually, I can always convert the vhd manually. Might be an idea anyways just to know how to complete that process. Then try to reverse the conversion from ESXi back to HyperV (though I'm going to upgrade to Server 2012, been playing with HyperV R3 at the office and I'm getting a bit excited about whats going to happen. (I find it's better to know how to do it before you actually need to do it, so if worst comes to worst I'm already prepared) don't know if it is still available or not but in the ESX 3.02 time frame there was a cold p2v disk you could run on a machine that would allow you to convert any (even non-supported OS types) system. It still works but you have to upgrade the vm hardware from 4 to 7 (or higher) afterwards.
Unable To Obtain History
On the Hyper-V side I have never worked with the product other than one time at a MS office just before the R2 release on 2008. They were so far behind VMware my shop was not interested in changing. My personal choice is still VMware. Did you know that they (MS) just put in a new feature that will allow you to commit (merge) the snapshot AVHD files without powering down the VM? It has been around in VMware since I started working with them in 07.
Unable To Obtain Ip Address
Enough about my Hyper-V hating rant - good luck on your quest for knowledge! I'm quite aware of the new features in 2012, I upgraded my home servers about 3 months ago, and while I know M$ has been quite far behind in terms of the capabilities of the hypervisor, they have done A LOT of catching up with the new R3. Just need to allow device redirection. I worked in a VMWare shop a few years ago and thought it was the greatest thing I'd ever seen, but unfortunately the higher ups have a hard time swallowing the licensing costs, when with purchase of 08R2 Enterprise, we have license for HV, 4 VMs, as well as capability for HA. But then again, my annual budget is less than what most companies would spend on a single server. But we make do. As Mother Theresa explained: “We the willing, led by the unknowing, are doing the impossible for the ungrateful.
We have done so much, with so little, for so long, we are now qualified to do anything, with nothing.” And while I'd rather not give up on the Win8 system, unfortunately (well, not really, but in regards to the issue) one of our clients recently purchased another location and I'll be tied up with that for a few weeks. Kb929547 vista patch. I may find time to try a cold convert in the odd hours, but for now I'm considering this a moot issue.