Unable to obtain hardware information for the selected machine "esx 4"

Trying to use VMWare converter version 4.0.1  build 161434 to copy a W2003 server from one ESX server to another. The W2003 won't boot as it says there's not enough disk space. (I think i've taken too many snapshots).
Anyway the solution is to clone the server to another and then re-install.
When i use the converter wizard I get "Unable to obtain hardware information for the selected machine" . Have checked a few sites and they have suggested redfining the OS on the VM Server to Other (32 bit).
That didn't work..
Donald_from_OZAsked:
Who is Participating?
 
coolsport00Connect With a Mentor Commented:
Absolutely; glad it's up for you now. :) So, the underlying issue is still needing space. You have 40 and 50GB on the datastores, but that might not be enough for ALL the VMs you have on those datastores, because they need not only space for their disk files, but swap space as well.

Regards,

~coolsport00
0
 
coolsport00Commented:
Hmm...ok, let's 'define' your terms above just so I have it correct. Let's call your 2K3 a VM (as opposed to 'server') if that is indeed what it is; or is it a physical box? Since you stated 'copy from one ESX host to another, I assume it's a VM'. I assume the snapshots you're referring to are associated with the 2K3 VM? Remove any snapshots you have with it before 'converting' (moving) the VM to another host. Are you trying to use the Converter *Standalone* tool or converter plug-in within vCenter? My next question is why don't you use the 'migrate' function within vCenter? Or, are these hosts not managed by vCenter? Are the hosts ESX or ESXi?

So, here's my recommendation based off what I assume from your post
- revert all snapshots on the W2K3 VM so it's a 'clean' VM
- if you're using converter STANDALONE tool, close out of it
- go into Task Mgr and stop all vconverter*.exe processes
- reopen converter standalone (say 'yes' to start the server service)
- try the conversion (move) again selecting to convert a 'powered on machine' for your source 2K3 VM (if you need to keep the VM up and running)

If you're using vCenter to manage the ESX hosts, shut down your 2K3 VM (if it's possible) and do a 'migrate' to the other host.

A 3rd option is to use Veeam FastSCP to 'copy' the VM files to the other host (http://www.veeam.com/vmware-esxi-fastscp.html).

Hope that helps.

Regards,
~coolsport00
0
 
Donald_from_OZAuthor Commented:
I'm at home now but I can fill in the gaps:

Have deleted all of the snapshots from the W2003 guest.
The W2003 won't boot as I get a disk error.
I am running converter standalone from the an XP desktop machine.
I am using VSphere client as an interface.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
coolsport00Commented:
So, the converted VM won't boot, or the original VM? Do you have vCenter? If your converted VM is the one that's giving you the error, try converting using the converter plug-in within vCenter if possible. If you don't have that, power down the VM and use the Veeam copy tool (if you're able to power down the orig VM).

~coolsport00
0
 
vmwarun - ArunCommented:
1.How much free space is available on the ESX host where the W2K3 VM resides ?
2.Are you able to power on the VM ?
0
 
Donald_from_OZAuthor Commented:
The original VM won't boot.
 There is only 2.6 gig of space left on one of the datastores.
I don't have Vcenter.
Will try the veeam copy tool.
0
 
coolsport00Commented:
OK...yes, try Veeam and post the results when done.

~coolsport00
0
 
Donald_from_OZAuthor Commented:
Tried the Veeam tools but they don't work for ESX free.
I have deleted a heap of snaphots and then it went pear shaped.
One forum suggested that I take a snaphot and then delete all which didn't make any difference.
So I need to tackle a bigger issue, because if the servers stop they won't reboot.
In the log, I'm getting this error when I try to restart the server:
Unable to power on <servername> on localhost on DA-Center
Looked in the log file and I think this is the problem.
Failed to extend swap file (fileHandle 89124563) from 0 KB to 2097152 KB: No space left on device
Both datastores have 40gb and 50gb free.





0
 
coolsport00Commented:
For Veeam to work with ESXi, you have to power down the VM, then copy the files to the other host. Within FastSCP, you add the ESXi hosts under the 'Servers' heading, then browse to the datastore on the host with the VM, right-click the VM folder/directory, and select 'Copy'. Then, browse to the datastore on the 2nd ESXi host and 'Paste' it there. Again, the VM has to be off for it to work with ESXi. And now that I think about it, you may have to enable SSH on your ESXi hosts before doing the above works (see: http://www.yellow-bricks.com/2008/08/10/howto-esxi-and-ssh/).

What do you mean by "it went pear shaped"? What servers are you referring to?...your 2K3 VM? Is it on now? I tought you said it wouldn't boot? Let's clarify what's going on. Let's just throw away converting/moving your VM for now. Is the underlying issue that your 2K3 VM won't boot? If it doesn't boot, some of the research you've done has suggested you to move your VM, thus why you posted this question, correct? I guess I just want clarification to be able to better assist you. Explain in detail what happened to get to this point if you could.
Thanks...

~coolsport00
0
 
Donald_from_OZAuthor Commented:
Trying to copy the servers was a solution to the underlying problem which is:
I have a Dell Poweredge server running ESXi free.
It has 5 guests.
2 are currently running and I daren't turn them off.
None of the remaining three will boot up as I get :"Insufficient disk space on datastore"
They were running OK until I tried to delete the snapshots from the W2003 guest. Then it went downhill from there.
When I try to power up the guest I get the following
Message from localhost.MHO.LOCAL: Failed to
extend swap file (fileHandle 105213670) from 0
KB to 2097152 KB: No space left on device. Could
not power on VM : No space left on device. Failed
to power on VM
info
06/04/10 21:55
root
0
 
coolsport00Commented:
OK...and what are you using for storage? Is it local disks, a SAN, or something else?
0
 
coolsport00Commented:
Also, let me know what you've tried thus far to rectify this so I don't ask you to try something you haven't already attempted. :)
0
 
Donald_from_OZAuthor Commented:
I've deleted one of the secondary drives from one of the guests to free up space.
See screengrab of current setup for machine that I'm trying to boot up.
I have no Linux experience

datastore.png
0
 
coolsport00Commented:
Ok...as we've been going through this post/thread, my intuitions have thinking about swap file allocation. And, although you've cleared out some space in general on the datastore, that may not be sufficient. I've searched a bit on your error and have come up with a couple links that verify my 'intuition' that I'd like to have you look at/try:
http://communities.vmware.com/thread/126888
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003856

I recommend first to power down the 2K3 (if it isn't already) and edit it -> decrease the CPUs from 2 to 1 and decrease the memory to 1024MB. Then, try to boot it up. If it doesn't, look at the VMware KB for more suggestions to try and post back your results.

Regards,
~coolsport00
0
 
coolsport00Commented:
0
 
Donald_from_OZAuthor Commented:
Neither of those options worked.
I deleted one of the guests and it is now working.

I guess I need to do some housekeeping.

Thanks for your help.
0
All Courses

From novice to tech pro — start learning today.