VMware
3 Replies Last post: Aug 30, 2006 2:00 AM by Mike_Laverick  

Migrate (Relocate) Virtual Machine between ESX 2.5.2 hosts posted: Aug 29, 2006 3:39 PM

Click to view sysmexnz's profile Novice 9 posts since
Dec 14, 2005
Current Configuration
2 x ESX 2.5.3 hosts with local storage (no SAN)
Virtual Centre 2.0

I am trying to migrate (relocate) some virtual machines from one ESX host to another (the VM's are shutdown) with VC 2.0

Validation goes ok, but once the copy starts I get the following error

Network Copy Failed for File. [] /root/vmware/vmserver3/nvram

Anyone seen this before and have a solution to this ?
Click to view Mike_Laverick's profile Virtuoso 4,063 posts since
Jan 5, 2004
Current Configuration
2 x ESX 2.5.3 hosts with local storage (no SAN)
Virtual Centre 2.0

I am trying to migrate (relocate) some virtual
machines from one ESX host to another (the VM's are
shutdown) with VC 2.0

Validation goes ok, but once the copy starts I get
the following error

Network Copy Failed for File. []
/root/vmware/vmserver3/nvram

Anyone seen this before and have a solution to this ?

seen this on the forum before... i believe it turned out to be a permissions problem... the guy unregistered the VM... deleted the VMX configuration files... re-created them with the existing disk option... and the problem went away...

I notice the error says a network error. there have been some forum members who have had some unpleasant cold migrate errors and they seem to centre around network activity... where it has failed mid-way through the "move" (actually, all moves are copies) and they have been unable to retrieve the original VM...

Personally, i would recommend cloning the VM to the destination server.... unless you were doing from one SAN LUN to another where network reliability is insignificant...

Regards
Mike

Regards
Mike

Click to view Mike_Laverick's profile Virtuoso 4,063 posts since
Jan 5, 2004
As I say, very strange, becuase DNS works fine -
before these changes I could ping and ftp from each
host to one another.

Now its funny you mention that - I think it must have been the same thread - as the work around came back to me - when you mentioned the DNS issue...

Seems to me that the are couple of reasons why need to sort out name-resolution before we begin with vi-3...

this issue....
finding the license server (defaults to FQDN if license server has one)
initial set-up of VMware High Availability...

Regards
Mike

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities