VMware Cloud Community
Ajay_Nabh
Enthusiast
Enthusiast

error message while importing VMware Server Virtual Machine to ESX 3.5/VC2.5

Hi All

I am having issue with importing VM from Virtual server to ESX 3.5/VC2.5. In step one when I enter path of .vmx file and username/password. when I click next, It gives me error messgae " The Source VM could not be found" Please find log info below:

=========================================================================================================

2008-06-18 13:41:10.742 'P2V' 4124 info Starting execution of a Task

2008-06-18 13:41:10.742 'ClientConnection' 4124 info Making sure that UFAD interface has version vmware-converter-4.0.0

2008-06-18 13:41:10.758 'BaseLibs' 4124 warning SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs 10.20.1.66

2008-06-18 13:41:10.758 'BaseLibs' 4124 warning SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

  • The host name used for the connection does not match the subject name on the host certificate

  • A certificate in the host's chain is based on an untrusted root.

2008-06-18 13:41:10.758 'BaseLibs' 4124 warning SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

2008-06-18 13:41:10.898 'ClientConnection' 4124 info UFAD interface version is vmware-converter-4.0.0

2008-06-18 13:41:11.133 'P2V' 4124 info Task execution completed

2008-06-18 13:41:11.351 'P2V' 5032 info QuerySourceInfo called

2008-06-18 13:41:11.351 'P2V' 4124 info Starting execution of a Task

2008-06-18 13:41:11.351 'P2V' 4124 info Successfully connected to VMImporter

2008-06-18 13:41:11.789 'BaseLibs' 3436 warning SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs 10.20.1.66

2008-06-18 13:41:11.789 'BaseLibs' 3436 warning SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

  • The host name used for the connection does not match the subject name on the host certificate

  • A certificate in the host's chain is based on an untrusted root.

2008-06-18 13:41:11.789 'BaseLibs' 3436 warning SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

2008-06-18 13:41:12.883 'P2V' 4124 error Task failed: P2VError IMPORT_SOURCE_NOT_FOUND()

=========================================================================================================================

Having said that, I can migrate this VM using converter from the machine where this Vm is running using vmware server 1.04 to ESX3.5/VC2.5

Any help will be appreciated

Thanks in advance

Ajay

Reply
0 Kudos
4 Replies
IamTHEvilONE
Immortal
Immortal

You shouldn't need to user Converter to do this. the VMware Server 1.0.x format can be imported directly by ESX; see the documentation below.

You could use Converter against the 1.0.4 Server Image, but installing Converter directly into the Virtual Machine (if windows) or running it against the vmx source with the VM powered off.

>http://kb.vmware.com/kb/900

>Importing GSX Server and Workstation Virtual Disks to ESX Server

>Follow these steps to convert virtual disks created with GSX Server and Workstation to virtual disks that can be used with ESX Server.

>Note: You can migrate only a virtual machine created with virtual SCSI disks to an ESX Server system. ESX Server will not recognize the virtual IDE disks. If you have P2V Assistant, you can use this tool to convert the virtual machine from IDE to SCSI. Also see Converting a GSX Server Virtual IDE Disk to a Virtual SCSI Disk (http://kb.vmware.com/kb/1881).

1. Make sure the .vmdk file or files are accessible from the service console.

2. At the command line, enter:

vmkfstools -i <folder>/<filename>.vmdk <vmhba number>:<filename>.dsk

<folder> is the name of the folder from which you are importing.

<filename> is the name of the file you are importing.

<vmhba number> is the name of the VMFS partition.

For example:

vmkfstools -i /mnt/bigserver/putfileshere/mydisk.vmdk vmhba0:0:0:1:mydisk.dsk

Note on preallocated disks: If the virtual disk that you are importing is a preallocated disk, you'll have two .vmdk files that look something like this:

-rw-rr 1 root root 10737418240 Dec 20 23:14 win2k3-gsx-flat.vmdk

-rw-rr 1 root root 351 Dec 20 21:13 win2k3-gsx.vmdk

Run vmkfstools on the smaller file -- the one that does not include "flat" in its file name. In the example above, the correct file to choose is win2k3-gsx.vmdk.

>You can find additional information on using the vmkfstools utility in the ESX Server documentation.

Reply
0 Kudos
Ajay_Nabh
Enthusiast
Enthusiast

Thanks for your reply. but I thought there may be a fix for my problem.

Thanks anyway

Ajay

Reply
0 Kudos
IamTHEvilONE
Immortal
Immortal

I'm not saying there isn't a fix. The only thing that I can tell from the slice of the log provided is that you are using VMware Converter 4.0.0 plug-in from VirtualCenter. A newer version of the Standalone Converter, 3.0.3, is available from our site. Can you try the import with 3.0.3 and attach the logs in case of an error?

When you say you are importing a:

>VM from Virtual server to ESX 3.5/VC2.5

Do you mean Microsoft Virtual Server, or a different VMware Product? You mention a VMX, so I would assume a VMware Product.

>enter path of .vmx file and username/password

Where is this virtual machine being stored that requires a user name and password?

Reply
0 Kudos
Ajay_Nabh
Enthusiast
Enthusiast

HI IamTHEvilONE

Thanks for your comments. It works if I use standalone converter on VM host which is 2003 server or inside the VM. but Import through VI client using enterprise converter does not work. I am importing VMware server 1.04 VM. VM is stored on windows 2003 server which is connected to NAS using network cable.

Thanks

Ajay

Reply
0 Kudos