VMware vSphere

 View Only
  • 1.  Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 03, 2007 06:18 AM

    Hello, I am using VMware Converter 3.0.1 and having problems with converting a physical Machine: I'm importing a W2K Server which is located in the DMZ; I was able to finish the importing wizard (to a ESX Server) and after a reboot of the physical machine VMware Converter pops up with a failure "ERROR: Unknown error returned by VMware Converter Agent".

    I did several successfull imports physical to virtual without any problems so I assume the failure could be due to closed ports from the LAN to DMZ.

    Which ports are used for doing a successfull import? Does someone have the same problems? Can it be due to the new allocation of disk size ( I always choosed the option "Min. size".

    Thank you, Armin



  • 2.  RE: Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 03, 2007 04:59 PM

    See table 2-4 of the Converter 3.0.1 documentation (http://www.vmware.com/pdf/VMware_Converter_manual301.pdf)

    Note that the ports have changed since Converter 3.0.



  • 3.  RE: Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 04, 2007 08:35 AM

    Thanks for the hint but these ports are open allready. Log indicates this:

    ......

    \[2007-05-04 09:18:01.411 'P2V' 388 error] \[task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.FileOpenError)

    \[2007-05-04 09:18:01.411 'P2V' 388 verbose] \[task,339] Transition from InProgress to Failure requested

    \[2007-05-04 09:18:01.411 'P2V' 388 verbose] \[task,388] Transition succeeded

    \[2007-05-04 09:18:01.411 'P2V' 388 verbose] \[job,276] Job 8 changing state from 1 to 2

    \[2007-05-04 09:18:01.411 'P2V' 388 verbose] \[serialization,214] Serializing job 8

    \[2007-05-04 09:18:01.411 'P2V' 388 verbose] \[serialization,221] Archiving job to C:\Documents and Settings\user\Application Data\VMware\p2v30\jobs\00000008.xml

    \[2007-05-04 09:18:01.426 'P2V' 388 verbose] \[jobManager,375] Raising event 2 for job 8

    \[2007-05-04 09:18:01.426 'P2V' 388 verbose] \[jobManager,375] Raising event 4 for job 8

    \[2007-05-04 09:18:01.426 'P2V' 388 verbose] \[jobManager,375] Raising event 6 for job 8

    \[2007-05-04 09:18:01.426 'VmdbSvc' 388 verbose] Shutting down VMDB service...

    \[2007-05-04 09:18:01.426 'VmdbSvc' 388 verbose] Unregistering callback...

    \[2007-05-04 09:18:01.442 'VmdbSvc' 388 verbose] ...done

    .......

    I do not understand the part "P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.FileOpenError)" and did not find any hint.

    Thanks, Armin



  • 4.  RE: Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 05, 2007 11:32 AM

    I think if you look in the converter log you'll see more details about which file converter can't open... The log you supplied (I think) is the client log, which is more vague,...



  • 5.  RE: Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 08, 2007 06:04 AM

    You will at least need TCP port 902 open to the serviceconsole, from more ports see the manual...



  • 6.  RE: Convert Physical to ESX : Status Failed | which ports are needed?

    Posted May 08, 2007 08:00 AM

    It works with TCP Port 902 open - thanks, Armin