Failed to convert vmware server image into ESXi 3.5 U2, anyone who can help me (with logs)

[Bright_Zhao]

Hi, Everyone

Before ESXi, I using VMware Server 1.0.x to host my guest OS (Windows 2003), recently I found the ESXi is free to use, then I using VMware Converter 3.0.3 to convert my original VMware image into the ESXi 3.5 Update 2, but everytime I do the conversion, it'll failed on 42%, and I think the following section from the log files as the reasons, but don't know how to resolve that:

3 2008-08-18 13:33:26.468 'App' 4036 verbose ,0 NfcNetTcpWrite: timed out waiting for socket to be ready (101)

3 2008-08-18 13:33:26.468 'App' 4036 warning ,0 NFC ERROR NfcNet_Send: requested 272, sent only 9 bytes

3 2008-08-18 13:33:26.484 'App' 4036 warning ,0 NFC ERROR NfcFileSendMessage: hdr send failed:

3 2008-08-18 13:33:26.484 'App' 4036 warning ,0 NFC ERROR Network error -- Failed to send header message

3 2008-08-18 13:33:30.562 'App' 4036 info imageProcessingTaskStep,194 BlockLevelCloning::task step "copy local->remote" destroyed 3 2008-08-18 13:33:30.562 'App' 4036 error blockLevelCloningTaskImpl,868 File transfer failed. 3 Dst error: Network error -- Failed to send header message 3 2008-08-18 13:35:18.625 'App' 4036 error imageProcessingTaskImpl,552 BlockLevelCloning::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.NfcConnectionFault

3 2008-08-18 13:35:18.625 'App' 4036 verbose imageProcessingTaskImpl,154 BlockLevelCloning::task: SetState to error 3 2008-08-18 13:35:18.625 'App' 4036 verbose imageProcessingTaskWrapper,886 Remote task BlockLevelCloning::task completed

2008-08-18 13:35:18.625 'App' 4036 verbose imageProcessingTaskWrapper,749 Got an update from CloneTask::task 3 2008-08-18 13:35:18.625 'App' 1176 verbose imageProcessingTaskWrapper,437 Waiting for updates from CloneTask::task

3 2008-08-18 13:35:18.625 'App' 1176 verbose imageProcessingTaskWrapper,668 (Re)Start waiting for property updates from CloneTask::task 2008-08-18 13:35:18.625 'App' 4036 verbose imageProcessingTaskWrapper,749 Got an update from BlockLevelCloning::task 3 2008-08-18 13:35:18.625 'App' 1264 verbose imageProcessingTaskWrapper,515 Cleaning up remote task BlockLevelCloning::task 3 2008-08-18 13:35:18.625 'App' 1264 verbose imageProcessingTaskWrapper,1201 Disposing task wrapper for task BlockLevelCloning::task 3 2008-08-18 13:35:18.625 'App' 5956 verbose disposable,122 object explicitly disposed: BlockLevelCloning::task 3 2008-08-18 13:35:18.625 'App' 5956 verbose imageProcessingTaskImpl,123 BlockLevelCloning::task being destroyed 3 2008-08-18 13:35:18.625 'App' 1264 error imageProcessingTaskStep,423 CloneTask::task step "Cloning into disk datastore1 PA3-PIVOD-S1/PA3-PIVOD-S1.vmdk" failed

[IamTHEvilONE]

It looks like there may be a networking hiccup ... and yes that's a technical term

Random disconnects can happen for a number of reasons, like duplex settings not being consistent across the connection. Source = Auto, Switch = 100/Full, ESX = Auto

take a look at this document for some hints.

Investigating network device settings as a cause of VMware Converter failures

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

This may not only apply to where you are going to, but where you are coming from in the case of your UNC path to the VMX file.

btw .... is this really a windows 98 vm you are attempting to convert? Just as an FYI (not saying it won't work):

http://www.vmware.com/support/converter/doc/releasenotes_conv303.html#guestos

Support for the following guest operating systems is Experimental. VMware Converter 3 can clone source images containing these operating systems, but the destination virtual machine may or may not work without additional configuration after import. In particular, if the source image contains unsupported hardware, you might need to modify the configuration of the destination virtual machine before using it:

• Linux

• Windows NT 3.x

• Windows ME

• Windows 98

• Windows 95

• MS-DOS

EvilOne

1 - Check the documents

2 - Search the forums

3 - Post Question

and remember ... I like points

[Phil_4096 · Accepted solution]

Hi,

This is a known "feature" of converter v3.0.3 when converting disks with a lot of empty space. When you get the option, don't use "convert all disks and leave current size", use "select volumes..." but you don't have to change anything. This is also quicker because I think it creates new disk(s) and just copies the data, rather than converting the entire disk block-for-block.

Phil.

[Bright_Zhao]

yes, exactly.

[mgrumley]

Thanks a million for the fix Phil!! It solved my problems just in time for me to take the gun out of my mouth.

Michael