Your just going about your day, trying to P2V a machine using the Cold Clone when you get the error: Unable to determine Guest OS
You check the client log and don’t find anything helpful:
1 2 |
vmware-converter-client-0.log [2011-02-15 09:35:08.718 'P2V' 840 error] [task,296] Task failed: P2VError UNABLE_TO_DETERMINE_GUEST_OS |
Then you check the agent log and it sheds light on the problem:
1 2 3 4 5 |
vmware-converter-agent-0.log [#3] [2011-02-15 09:35:23.000 'App' 268 warning] [attachedDiskWin32,499] Warning: no attached disks were detected. [#3] [2011-02-15 09:35:23.000 'App' 268 error] [slave,359] No local disks were detected, so no local host config info. [#3] [2011-02-15 09:35:23.000 'App' 1072 error] [importSource,369] Unable to read OS info from system disk: vmodl.fault.SystemError [#3] [2011-02-15 09:35:23.000 'App' 1072 error] [imageProcessingTaskImpl,572] VmiQuerySourceInfoTask::task{2}: Image processing task has failed with MethodFault::Exception: sysimage.fault.UnableToDetermineGuestOs |
- Run over to your server vendors support site (in my case support.dell.com) and download the proper driver
- Next extract the contents of your download (usually a self-extracting exe) Â and browse to the result. Â You should have a folder with some files:
- .cat, .sys, and a few .inf’s
- Copy these to a new folder –Â ensure this folder name is 8 characters or less and contains all capital letters and/or numbers
- Then copy this new folder to the same location as your coldclone.iso
- When you download the .zip file that contains coldclone.iso it also contains a tool called petool.exe. Â Ensure petool.exe is in the same directory as the coldclone.iso
- Now open a command prompt and navigate to the location where you have coldclone.iso
- Type: petool.exe -i coldclone.iso -d “Full path to folder containing storage driver” (see example below)
- Hit enter and watch the tool inject the new driver you specified
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
Example of Storage Driver Injection: D:\Downloads\VMware-convertercd-4.1.1-206170>peTool.exe -i coldclone.iso -d "D:\Downloads\VMware-convertercd-4.1.1-206170\R210509" Log: checking options ... Log: checking file existence ... load ISO image ... load ISO image succeeded load boot image ... load boot image succeeded extract boot image ... extract boot image succeeded Log: adding storage driver R210509 Log: adding driver name R210509 Log: adding driver name succeeded Log: adding storage driver R210509 succeeded load ISO image ... load ISO image succeeded Log: pack image file back ... pack the ISO image ... load source directory & boot image file ... load source directory & boot image file done write system reserved sector ... write system reserved sector done write primary volume descriptor ... write primary volume descriptor done write boot record ... write boot record done write volume descriptor set terminator ... write volume descriptor set terminator done write boot image ... write boot image done write path tables ... write path tables done write directory record and files ... 0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100% write directory record and files done pack ISO image succeeded Log: pack image file back succeeded Log: clean up ... Log: clean up succeeded D:\Downloads\VMware-convertercd-4.1.1-206170> |
Use the newly created coldclone.iso and try your P2V again–everything should work as expected this go around. Â If not check your logs again, if you see the same error message you still might have the wrong storage drivers. Â In the case of Dell confirm your storage adapter model in the DRAC or during bootup and ensure you download the corresponding adapter driver.
For more information check out VMware KB: Â 1012947 – Adding additional drivers to the VMware Converter Cold Clone ISO