VMware Cloud Community
al8
Contributor
Contributor
Jump to solution

Importing VM to ESX Server 3.01

I am trying to import a virtual machine from a workstation to the ESX Server by using the VMware Import Wizard from the

Workstation. After going through various settings, selections, and clicking the finish button at the end,

I get the following message:

"Virtual machine you are trying to import is currently open. Please close the virtual machine and try again."

I made sure that the VM was shutdown. What does it mean when it say it's open?

Anyone has any idea what it means and know how to fix the problem?

Thanks,

al8

0 Kudos
1 Solution

Accepted Solutions
rriva
Expert
Expert
Jump to solution

Remove it form favorite

Close the VM TAB

Finaly check if in the VM folder, you could not see any .lck file

If a .lck file is present, the system consider your VM open.

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com

View solution in original post

0 Kudos
3 Replies
rriva
Expert
Expert
Jump to solution

Remove it form favorite

Close the VM TAB

Finaly check if in the VM folder, you could not see any .lck file

If a .lck file is present, the system consider your VM open.

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
0 Kudos
al8
Contributor
Contributor
Jump to solution

Thank you!

Just as you said: .lck file was there and the tab was still showing after I had removed the VM from favorite.

So, I just closed the VM Tab per your instruction. The .lck file was no longer there.

Now it's importing to the ESX Server.

By the way, there was a warning message when I was going through the VMware Import Wizard to import the VM.

It said: "warning: cannot configure the source image". Is that something that needs to be concerned with? Or can I just ignore it.

Thanks a bunch,

al8

0 Kudos
rriva
Expert
Expert
Jump to solution

I've never seen that error message before but if you can import the VM correctly, I think you can ignore it without any problem.

Have you tried to customize the OS during the import ? Maybe the message is related to the customization.

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
0 Kudos