VMware Cloud Community
vmtayo
Contributor
Contributor

LiveState Import of IBM x236 server fails with VMwareImporter 2.0 RC

Hello,

We have a number of IBM BladeCenter HS20 systems plus IBM x236 systems running Windows 2003 Server R2 (only one x236 runs Windows 2003 Server SP1). Symantec LiveState v6.0.1 is used to create images of all systems. We are able to import the LiveState images of the BladeCenter systems into VMware Server using VMwareImporter Build 30557. However, all IBM x236 images consistently[/u] fail to import and the following error message is reported:

"[i]Virtual machine importer is unable to recognize the operating system in the source VM or image. Please ensure that you have full access to the source directory[/i]."

Listed below is a log file from a failed import of one of our x236 systems running Windows 2003 R2 Standard Edition. It has one C drive (136GB), a basic disk formatted with NTFS. Any suggestions would be most welcome. Let me know if you need more specific information.

\[2006-09-15 15:53:05.750 'App' 3212 info] Impersonating user Administrator in session 496A29AC-D883-4356-B54D-5E0205409EE5

\[2006-09-15 15:53:05.765 'App' 3372 info] \[vmImporter,211] Found UFAD log at .\vmware-ufad.log-0.log

\[2006-09-15 15:53:05.734 'App' 2472 info] Current working directory: C:\Documents and Settings\Administrator\Desktop

\[2006-09-15 15:53:05.734 'App' 2472 info] \[vmiSupport,195] VMImporter UI logger created

\[2006-09-15 15:53:05.734 'ClientConnection' 2472 info] Connecting to ufa-client on named pipe
.\pipe\vmware-ufad-vmdb

\[2006-09-15 15:53:05.734 'ClientConnection' 2472 info] Mounting remote VMDB path / to local /vmomi/...

\[2006-09-15 15:53:05.734 'BaseLibs' 1108 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2006-09-15 15:53:05.750 'ClientConnection' 2472 info] Connection established!

\[2006-09-15 15:53:05.765 'App' 2472 info] \[vmiSupport,199] UFA connection established

\[2006-09-15 15:53:05.781 'App' 2472 info] \[vmiSupport,207] UFAD logfile path is: C:\Program Files\VMware\VMware Virtual Machine Importer 2\vmware-ufad.log-0.log

\[2006-09-15 15:53:10.718 'App' 3212 verbose] \[imageProcessingTaskImpl,495] Starting execution of an image processing task, this = 01575030

\[2006-09-15 15:53:10.718 'App' 3212 verbose] \[imageProcessingTaskImpl,145] SetState to 1, this = 01575030

\[2006-09-15 15:53:10.718 'App' 3212 info] \[vmiQueryOsTask,117] vmiQueryOsTask initialized

\[2006-09-15 15:53:10.718 'App' 3212 verbose] \[ufaConnection,94] Creating local adapter...

\[2006-09-15 15:53:10.718 'App' 3212 verbose] \[vmiUtils,79] VmiImportTask::GetComputerSpec - Instantiating V2iDisk

\[2006-09-15 15:53:10.718 'App' 3212 verbose] \[vmiUtils,84] VmiImportTask::GetComputerSpec - Calling v2id.wrapDiskImage()

\[2006-09-15 15:53:13.671 'App' 3476 verbose] \[slaveConnection,189] Creating local connection to the co-located slave

\[09/15/06 15:53:13] Status: (VmountDisk:237) disk E:\SLVS2005\SmallSite\drive-0.vmdk was opened

\[09/15/06 15:53:13] Error: (VmountPartitionList:140) This virtual disk has no partition table (or a corrupt one).

\[09/15/06 15:53:13] Error: (VmountLocator:114) Vmount2.Vmount2Disk: This virtual disk has no partition table (or a corrupt one).

\[09/15/06 15:53:13] Error: (VmountLocator:114) Vmount2.Vmount2Disk2: Cannot access layout on disk

\[09/15/06 15:53:13] Status: (VmountDisk:440) disk E:\SLVS2005\SmallSite\drive-0.vmdk was closed

\[2006-09-15 15:53:15.593 'App' 4048 verbose] \[diskSet,373] Volume: idx=0 sysId=7 active=Y

\[2006-09-15 15:53:15.593 'App' 4048 verbose] \[virtualVolumeWin32,208] Mounting virtual volume virtVol=\{computer=,1}... \[09/15/06 15:53:15] Status: (VmountDisk:237) disk E:\SLVS2005\SmallSite\drive-0.vmdk was opened \[09/15/06 15:53:15] Status: (VmountDevice:1529) device of type volume with offset 32256 was created \[09/15/06 15:53:15] Error: (VmountLocator:114) Vmount2.Vmount2Device: no drive letter currently assigned \[2006-09-15 15:53:18.640 'App' 3212 error] \[vmiQueryOsTask,377] Unable to read OS info from system disk: sysimage.fault.PlatformError \[2006-09-15 15:53:18.640 'App' 4048 verbose] \[disposable,109] object explicitly disposed: computer=\

\[2006-09-15 15:53:18.640 'App' 4048 verbose] \[disposable,45] disposable object being destroyed: computer=\{b450f1bf71794f93ab40ec1bc03c51fa37c5be05}

\[2006-09-15 15:53:18.640 'App' 4048 verbose] \[diskSet,118] Cleaning up computer's child objects

\[2006-09-15 15:53:18.640 'App' 4048 verbose] \[diskSet,141] Unregistering volume id=virtVol=\{computer=,1} \[2006-09-15 15:53:18.640 'App' 4048 verbose] \[virtualVolumeWin32,163] Unmounting virtual volume virtVol=\{computer=,1}...

\[2006-09-15 15:53:36.171 'App' 4048 verbose] \[diskSet,151] Unregistering disk id=disk=\{28c848b5ba65af8cf8032d2451b50af53c8f9a97}

\[2006-09-15 15:53:36.250 'App' 3212 info] \[vmiUtils,276] Deleting E:\SLVS2005\SmallSite\drive-0.vmdk

\[2006-09-15 15:53:36.250 'App' 3212 info] \[vmiUtils,281] Deleting E:\SLVS2005\SmallSite\drive-0.vmdk.rdonly

\[2006-09-15 15:53:36.250 'App' 3212 verbose] \[imageProcessingTaskImpl,145] SetState to 3, this = 01575030

\[2006-09-15 15:53:36.250 'App' 3212 error] \[imageProcessingTaskImpl,529] Image processing task has failed with a fault: sysimage.fault.UnableToDetermineGuestOs

\[2006-09-15 15:53:36.281 'App' 3212 verbose] \[disposable,109] object explicitly disposed: VmiQueryOsTask::task\{8}

\[2006-09-15 15:53:36.281 'App' 3212 verbose] \[disposable,45] disposable object being destroyed: VmiQueryOsTask::task\{8}

\[2006-09-15 15:53:36.296 'App' 3212 info] \[vmImporter,211] Found UFAD log at .\vmware-ufad.log-0.log

\[2006-09-15 15:53:36.296 'App' 3212 info] \[vmImporter,234] Found VMOUNT log at C:\WINDOWS\TEMP\vmware-vmount.log

\[09/15/06 15:53:36] Status: (VmountDevice:147) device of type volume with offset 32256 was closed

\[09/15/06 15:53:36] Status: (VmountDisk:440) disk E:\SLVS2005\SmallSite\drive-0.vmdk was closed[/i]

Reply
0 Kudos
3 Replies
vmtayo
Contributor
Contributor

Please note that we have also tried creating LiveState images using Symantec LiveState Recovery Advanced Server v6.0.2. Again, all IBM x236 images fail to import.

Reply
0 Kudos
gautam
Expert
Expert

Sorry for the delayed resoponse, in addition to the C Drive were there any unformatted/non-windows partitions that were part of the SV2I backup?

vmtayo
Contributor
Contributor

Thanks for the response. There are no unformatted/non-windows partitions.

We have been experimenting with the new VMware Converter Beta 3.0 and we have successfully migrated a SV2I file from an IBM x236 system.

Reply
0 Kudos