Error importing Windows XP VMWare appliance
Submitted by Allan Konar on July 9, 2007 - 8:16pm.
Import a Windows XP VMWare appliance (I used their P2V converter to create it and have run it without issue within VMWare Player) fail. Here's what I find in the logs:
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:appmgr.cc:1338] Opening VMX file file:///F:\Student 5\Student 5.vmx
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:appmgr.cc:1365] Creating LivePC Student71fd5465-0f27-4053-b8f9-8e5e042691c9
2007-07-09 23:23:32 warn P3196:T3592 [util:propmap.cc:66] propmap file does not exist: file: F:/moka5/Documents and Settings/moka5User/Application Data/moka5/Engine/settings/properties
2007-07-09 23:23:32 warn P3196:T3592 [util:thread.cc:202] starting thread_impl "fetch_op::create" (this=04564570) (started=0, running=0, stopped=0)
2007-07-09 23:23:32 warn P3196:T1412 [appmgr:appmgr.cc:331] Prefetcher thread running
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:appmgr.cc:1393] Copying VMX file
2007-07-09 23:23:32 warn P3196:T3576 [util:thread.cc:307] thread_trampoline(): thread starting (t=04564570, tid=3576) (started=1, running=0, stopped=0)
2007-07-09 23:23:32 warn P3196:T3576 [appmgr:livevm.cc:688] start prefetching livevm "Student71fd5465-0f27-4053-b8f9-8e5e042691c9"
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:appmgr.cc:1422] Converting disks...
2007-07-09 23:23:32 warn P3196:T3428 [appmgr:livepc.cpp:442] poll_state error
2007-07-09 23:23:32 warn P3196:T3428 [appmgr:livepc.cpp:456] poll_state size error
2007-07-09 23:23:32 warn P3196:T3428 [appmgr:livepc.cpp:468] poll_state trace error
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:livevm.cc:2137] Error while processing system.vmdk: wrong magic number
make_fetch_order+1146
except_handler3+0
flag_base::operator>=+79
2007-07-09 23:23:32 warn P3196:T3592 [appmgr:appmgr.cc:1926] deleting livevm Student71fd5465-0f27-4053-b8f9-8e5e042691c9
2007-07-09 23:23:32 warn P3196:T3576 [appmgr:appmgr.cc:2014] Exception occurred during fetch: ver-1.xml doesn't exist and fetch may block
0x43c44a
0x43bbe7
0x421093
new_runnable+1023
new_runnable+809
new_runnable+666
0x408b0000
2007-07-09 23:23:32 warn P3196:T3576 [util:thread.cc:314] thread_trampoline(): thread exiting (t=04564570, tid=3576) (started=1, running=1, stopped=0)
2007-07-09 23:23:32 warn P3196:T3428 [appmgr:livepc.cpp:524] poll_state vm error
Any ideas?
Thanks,
a
what is the conversion step prior to importing?
Submitted by Allan Konar on July 10, 2007 - 10:56am.
And how can I check import errors. I only found three log files (one in documents and settings\...\application data\moka5, which had no relevant info and two on the USB disk with the Moka install, one empty and the other with the entries I posted). I'm happy to do whatever legwork is necessary.
Thanks,
a
The logs for import are
Submitted by Kevin W on July 10, 2007 - 12:52pm.
The logs for import are minimal in the Engine today.
1. How many vmdk files do you have? If there is more one, then most likely you will need to run the vmware-vdiskmanager tool.
====================
* When you try to import, you get this error: Cannot process disk (import.vmdk). Could it be a snapshot volume?
* Even though the import was successful, when you try to start, you get this error: Cannot check for the existence of an old redo log for disk 'winxppro.vmdk'.
The vmware-vdiskmanager tool is distributed with VMWare Workstation and VMWare Server. You can download VMWare Server by going to VMWare's website here.
You can get the executable in the free trial version of VMware Workstation. Download the installer and instead of double-clicking it, go to a command prompt and run the installer with the "/a" switch:
Example based on VMware Worstation 5.5.3:
C:\VMware-workstation-5.5.3-34685.exe /a
You can convert the vmdk by the steps below:
1. At the command line, type vmware-vdiskmanager.exe -r source.vmdk -t 0 target.vmdk
2. If necessary, delete or rename original vmdk files, then rename the target.vmdk file to match the one for the vmx.
3. Alternatively, edit the vmx file to rename source.vmdk file to target.vmdk, such that the target.vmdk file name matches the one for the vmx.
4. Also, edit the vmx file, replace .deviceType = "plainDisk" with .deviceType = "disk"
5. Now import the newly created vmdk file as described above.
Some Virtual Machines
Some Virtual Machines require a conversion still prior to importing into the moka5 Engine.
Check Import errors
If you continue to have issues during import, could you send us your vmx file ([email protected])? That might help us track down the problem. Also, if you could upload your original vmdk disk to e.g. www.sharebig.com we can try converting it.
Kevin