Converter (and it's predecessor, Virtual Machine Importer) only supports Ghost 9 and higher images (.sv2i). If you are using an older version of ghost (.gho), you will need to manually create a new VM, boot it with the ghost restore disk, and restore your .gho image. Then, run Converter and just choose the Reconfigure step.
Version 11? The current version is 10, which does create .2svi files. Do you have the Symantec version of Ghost or the old Binary Software version? Or is this some beta version?
Edit: Ah! You're using "Norton Save & Restore." Does NSR give you the option to save as .2svi when you create the image file?
I downloaded the trial version of Norton Save & Restore v1.0. It does create images with a .sv2i extension. There is no option for .GHO extension. I was able to convert the .sv2i image with Converter 3.
The last time I saw Ghost image files with .GHO extension was version 8 and older, which were all DOS based.
I'm running Ghost 11 also. It came as part of the Ghost Solution Suite 2.0, which was released in November of 2006. It only creates .GHO files:
<a href="http://imageshack.us">!http://img152.imageshack.us/img152/8030/ghostao2.jpg|alt=Image Hosted by ImageShack.us|src=http://img152.imageshack.us/img152/8030/ghostao2.jpg|border=0!</a>
I'm running Ghost 11 also. It came as part of the
Ghost Solution Suite 2.0, which was released in
November of 2006. It only creates .GHO files:
Got it. GhostCast is based on the older DOS Ghost program, which is why it only produces .GHO files. I used GhostCast and PQI Driveimage in the past. Both product lines were aquired by Symantec and brought under the name "Ghost." Why Symantec has numbered the Ghost portion of GhostCast "11" is beyond me. I read that the next version of the standalone Ghost may be "12" to avoid confusion about the version numbers.
In any case, .GHO files are not compatible with Converter. You'll need to upgrade to the standalone Ghost or Livestate. Otherwise, create a new vritual machine, restore the .GHO file to the VM, then use Converter to "convert" the VM rather than "import."
Hmm. When you create the Ghost image, don't include any utility partition, if any. Perhaps just the boot partition. If you still have problems, you'll want to start a new thread (for a new topic) and include the converter logs.
And at least we have a Converter product. Does MS have a P2V converter? And what about the Linux guys?
In my case, the servers are still physical and I'm using VMWare server for DR purposes. So the physical servers are regularly Ghosted (Livestate in my case) and I convert the images to VMs. The VMs become offline standby servers. When I can get funding for ESX and have all the servers virtualized, then we'll probably stop using Livestate on the servers. We're still imaging the desktops, again for DR purposes.
But how do specify GHO image? Isn't it needs to be in v2i format?
As I already mentioned in my first reply to you... you can create the VM yourself and manually restore the older .gho Ghost image into the VM. Then, before you power the VM up after restoring the Ghost image, run the VMware Converter and select the Configuration option only.