sysimage.fault.DiskLibConnectionFault (DiskLib error = 4194313) - Not A Network Problem!!!

[idfubar]

Regarding errors of the form:

2008-03-12 16:34:20.765 'App' 708 info Creating Local Disks

2008-03-12 16:34:20.775 'App' 708 verbose Creating Local Disk; Disk name=
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk; Mode = persistent; Is2GBSplit = No; preallocate space = Yes; is disk Flat = Yes; size = 15744724

2008-03-14 07:22:17.996 'App' 708 info FAILURE TO CREATE Disk name=
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk DiskLib error = 4194313

2008-03-14 07:22:18.056 'App' 708 info DISKLIB-LINK : "
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk" : failed to open (The system cannot find the file specified).

2008-03-14 07:22:18.056 'App' 708 info DISKLIB-CHAIN : "
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk" : failed to open (The system cannot find the file specified).

2008-03-14 07:22:18.056 'App' 708 info DISKLIB-LIB : Failed to open '
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk' with flags 0x2 (The system cannot find the file specified).

2008-03-14 07:22:18.056 'App' 708 error DiskLib_Open failed on
10.0.1.198\c$\WinNT\Temp\Win2k\Win2k.vmdk with error The system cannot find the file specified.

2008-03-14 07:22:18.066 'App' 1084 info VmiImportTask::task step "create VM" destroyed 2008-03-14 07:22:18.066 'App' 1084 error Error during creation of target VM 2008-03-14 07:22:18.066 'App' 1084 info VmiImportTask::task step "create and clone to VM" destroyed

2008-03-14 07:22:18.066 'App' 1084 info VmiImportTask::task step "Clone VM" destroyed 2008-03-14 07:22:18.066 'App' 1084 error VmiImportTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.DiskLibConnectionFault

2008-03-14 07:22:18.066 'App' 1084 verbose VmiImportTask::task: SetState to error 2008-03-14 07:22:20.169 'App' 1084 verbose object explicitly disposed: VmiImportTask::task

2008-03-14 07:22:20.179 'App' 648 verbose object explicitly disposed: computer= 2008-03-14 07:22:20.179 'App' 648 verbose Cleaning up computer's child objects 2008-03-14 07:22:20.179 'App' 648 verbose Unregistring volume id=attVol={computer=,1}

2008-03-14 07:22:20.179 'App' 648 verbose Unregistring volume id=attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},2}

2008-03-14 07:22:20.179 'App' 648 verbose Unregistring disk id=disk=

2008-03-14 07:22:20.179 'App' 1084 verbose VmiImportTask::task being destroyed

2008-03-14 07:22:21.111 'App' 1188 verbose CloseSession called for session id=63007A6F-03C1-4339-AF3E-21AA998A5BCC

2008-03-14 07:22:21.111 'VmdbAdapter' 1188 verbose Removed vmdb connection /db/connection/#a/

A search of the VMTN forums reveals six threads: one by 'devzero' (no reply), four (1, 2, 3, and 4) addressed by 'theanykey' (suggesting network problems as the root cause), and one with a different "sysimage.fault.*" error but also without resolution.

Regarding the excerpt:

The network is entirely open (i.e. no port or address restrictions on the single domain) and virtualization of the computer's FAT32-based OS partition (one of two partitions on the computer's single basic disk) to a standalone virtual machine has not been successful (i.e. the operation initially failed block-level virtualization and later file-level virtualization both with and without the optional customization step); as such the complete logs from a failed "remote, hot, file-based, customized, non-split" virtualization attempt have been attached to this post and can be reviewed by anyone who may be seeking a challenge.

PS: Converter v3.0.2u1 build 62456 will not install locally to the Windows 2000 instance which is being virtualized and the source & target are being accessed with their respective "Administrator" logins from a borrowed laptop being returned tomorrow; the only idea which has come to mind is to specify the second partition as a network destination...

[theanykey]

Connecting to
10.0.1.198\c$\Temp as Administrator

SMB manager: Error connecting to share http://\\10.0.1.198\c$\Temp: 1312

Failed to connect to
10.0.1.198\c$\Temp as Administrator. Error: Unspecified error in SMB share manager.

Can you try mapping the network share as a drive letter via windows and then push it to that new drive letter? Test the share by writing, saving, verifying.

[idfubar]

the only idea which has come to mind is to specify the second partition as a network destination...

Local installation was successful using the 'Administrator' account instead of an account assigned to the 'Administrators' group (WTF?); unfortunately the operation still failed, both before converting the primary/active partition to NTFS and after.

PS: The error message was the same both before and after conversion to NTFS, specifically:

ERROR: Failed to take snapshot of a source volume.

Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems,

and not having enough free disk space.

After reviewing the "Best Practices" document (attached along with logs from the "local hot" failure) it's fair to say all suggested steps were followed; the only recourse for successful Converter conversion is to attempt conversion of an intermediary format (i.e. proprietary backup image or competing vendor's virtual machine) or to attempt "remote hot" conversion again per suggestion of the 'theanykey' (with the assumption that specifying an explicitly mapped drive as the destination can/will have some effect).

Message was edited by: idfubar, 20080319@1045PDT (fixed a spacing issue between "after" and "PS")

Message was edited by: idfubar, 20080319@1045PDT (fixed a spacing issue between "space" and "after")

[theanykey]

Please note that the attached converter best practices is not a compilation provided by vmware and may contain outdated or incorrect information.

For example the networking tourbleshooter is incorrect as it references specifics to converter version 3.0.0 (3 versions old) and the required ports have changed.

In your log now, I see:

Vsnap does not have admin rights

Something else is going on here. Since this is a windows 2000 machine, can you reboot the box and try again?

If it fails again, can I see a full view screenshot of diskmanagement?

[idfubar]

The machine was successfully virtualized using Parallels Transporter (made by a company formerly called SWsoft); unfortunately the newest version of VMware Converter (3.0.2) does not seem to support direct V2V conversion of Parallels Virtual Machines...