VMware Cloud Community
brechbuehler
Enthusiast
Enthusiast

Import VM from VMware Server

Is is possible to migrate a virtual machine from VMware Server 1.0.10 to ESXi 5.1?

If yes, how?  Can it be done in vSphere Web Client?

I'm aware of one kludgy solution: take a backup using 3rd party software, then do a bare-metal restore onto ESXi.

Reply
0 Kudos
6 Replies
kunaludapi
Expert
Expert

Try vmware standalone converter.

--------------------------------------------------------------- Kunal Udapi Sr. System Architect (Virtualization, Networking And Storage) http://vcloud-lab.com http://kunaludapi.blogspot.com VMWare vExpert 2014, 2015, 2016 If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Reply
0 Kudos
Borja_Mari
Virtuoso
Virtuoso

Hello,

check this documentation about the process to migrate from server to esxi:

http://www.ajpdsoft.com/modules.php?traducir=es-en&name=News&file=article&sid=595

VMware KB: Moving or copying a virtual machine within a VMware environment

VMware KB: Best practices for using and troubleshooting VMware Converter

It should be helpful Smiley Happy

Best regards,

Pablo

------------------------------------------------------------------------------------------------- PLEASE CONSIDER AWARDING any HELPFUL or CORRECT reply. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA . ¡¡Muchas gracias!! VCP3, VCP4, VCP5-DCV (VCP550), vExpert 2010, 2014 BLOG: http://communities.vmware.com/blogs/VirtuallyAnITNoob
Reply
0 Kudos
brechbuehler
Enthusiast
Enthusiast

It comes as .exe files, apparently for Microsoft Windows.  (They offer the sources, but what will be required to build?)  So that required a virtual machine running Windows XP, which I had.

For the conversion source, I chose "VMware Workstation or other VMware virtual machine"; the subtitle reads, "Convert a virtual machine from VMware Workstation, VMware Fusion or other VMware product."  I'd think VMware Server 1.0.10 qualifies as other product.  And the Converter does "see" the .vmx file of the conversion source.  But it cannot get past the error "Unable to obtain hardware information for the selected machine."

I tried replacing every newline in the .vmx file with CR LF, to make the DOS world happier.  No dice, same error.

The Converter successfully reads an Acronis .tib file.  But that puts me back at the kludgy solution that I said I had in the beginning, without Converter.

Reply
0 Kudos
Borja_Mari
Virtuoso
Virtuoso

Hello,

I guess you are following the first documentation (how-to) i commented in my previous reply.

Check this vmware's kb in order to do troubleshooting:

VMware KB: Physical to Virtual (P2V) conversion using VMware vCenter Converter Standalone fails with...

Best regards,

Pablo

------------------------------------------------------------------------------------------------- PLEASE CONSIDER AWARDING any HELPFUL or CORRECT reply. Thanks!! Por favor CONSIDERA PREMIAR cualquier respuesta ÚTIL o CORRECTA . ¡¡Muchas gracias!! VCP3, VCP4, VCP5-DCV (VCP550), vExpert 2010, 2014 BLOG: http://communities.vmware.com/blogs/VirtuallyAnITNoob
brechbuehler
Enthusiast
Enthusiast

That KB states the symptom:

  • You see the error:
    Unable to obtain hardware information for the selected machine
  • This issue occurs when VMware vCenter Converter Standalone is installed on a source physical machine.

This is not the case in my situation.  (I installed the Converter on a virtual machine which was not the source (nor the destination).)

The error "Unable to obtain hardware information for the selected machine" is unspecific, kind of a General Car Error.  But at the bottom of the screen is a little widget to download the logs.  It yields a ZIP of ZIPs, and in the worker's log you can see the underlying cause.  My first issue had been "permission denied", but I had already opened up the permissions because someone said the error means EPERM.  But the next issue was "virtual disk needs fixed".

The only thing the vCenter Converter Standalone can read and process is an Acronis .tib file.  It actually built a clone of the machine, but the result was broken, in that Windows XP demanded to be re-activated because the hardware changed too much -- the old WPA hassle.

So in the end my best option is still Acronis bare-metal restore into a new virtual machine, off the same .tib file.  That avoids any tools from VMware, and yields a working clone that runs under ESXi.

Reply
0 Kudos
continuum
Immortal
Immortal

Reading this post gives me the shivers ...

VMserver 1 VMs very likely are already ESXi compatible but nobody ever asked for that.
You really do not need to torture your innocent VM with Converter.

If the vmdk you have uses the one piece preallocated format "monolithicFlat" all you have to do is upload vmdk + vmx.
Then you redefine type "monolithicFlat" to type "VMFS" - and bingo - thats all there is to do.

Read my notes : VMDK-Handbook-Basics
The link explains how to redefine the vmdk format in less than a minute.

If the VM uses a split or growing vmdk-type - import the vmdk with vmkfstools -i after you uploaded vmx + vmdk with WinSCP or whatever you prefer


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos