windows 2000 p2v won't convert/move from host

[dandevnull]

Setup

Windows 2000 VM that I just did a P2V resides on

ESX 3.5 update 2 68GB image 50GB available

I wanted

to move it to an ESX 3i Host temporarily while I build a new Host but

it won't move, it failed after almost 2 hours initially. Now it fails

almost immediately. See attached converter log:

I wish I had virtual center. That'd make it all much easier.

Thanks for any and all assistance.

[IamTHEvilONE]

dandevnull,

Welcome to the forums. When providing relevant files (logs, screenshots, etc), please use the attach feature. If you put the body of a log file into the post, it makes it very hard to follow. When we review the file, we can quote specific sections as required.

Do you mind editing your post to remove the log file from the posting and attach the related vmware-converter .log file?

Also, are the ESX and ESXi hosts managed by VirtualCenter? If so, VirtualCenter can do all of the heavy lifting between data stores. Otherwise, I'll look at the full log file to see what was going on.

EvilOne

1 - Check the documents

2 - Search the forums

3 - Post Question

And remember to award points to those who assist you.

vmware-converter.log (capture a record on the system where Converter is installed)

- Contains information regarding the import/reconfiguration steps taken by the agent when converting the physical/virtual machine.

- Is available in the Source Physical Machine OS’s temp directory (C:\Windows\Temp\vmware-temp)

[dandevnull]

Not to be pushy, but... any luck?

Thanks muchly.

[IamTHEvilONE · Accepted solution]

Sorry, when a post is edited, the rest of the thread is not notified. It looks like there is some form of networking problem between the vm and the ESXi datastore. There are some serious gaps in time according to the log file, then an NFC (network file copy) Error .... see below:

>\[#8] \[2008-10-05 23:15:43.620 'App' 1776 verbose] BlockLevelCloningTaskImpl::CopyStartCallback: Just started copying into: steelix/steelix.vmdk

>\[#8] \[2008-10-05 23:36:57.733 'App' 1776 warning] \[,0] \[NFC ERROR] NfcNetTcpWrite: bWritten: -1

There are a couple relevant kbs for what you are seeing here:

Troubleshooting cloning problems

http://kb.vmware.com/kb/1006292

Investigating network devices and device settings as a cause of VMware Converter failures

http://kb.vmware.com/kb/1004615

If you want to simplify the situation, and assuming that it is a windows vm ... install converter inside the VM rather than doing it as a VI virtual machine ... that will reduce the problems of network communication per Best Practices for Troubleshooting VMware Converter -

http://kb.vmware.com/kb/1004588

Cheers,

EvilOne

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

[dandevnull]

Sorry it took so long. So, I finally got it working. I had to run chkdsk 4 times before all errors were resolved. Converter will do a p2v with a fubar'd disk but won't move it from VM to VM with one. Thanks.

[IamTHEvilONE]

man, that's a lot of chkdsks.

[dandevnull]

You're telling me. The first time it hung in the first phase, then the second, and so on. All told it took wel over 5 hours to complete the process.

Lesson learned: Make sure the disks are clean before you P2V.

Thanks again for the pointers.