virtualbox.org

Ok - new to VirtualBox and must be doing something daft.

Have visualized my old Win XP laptop using VMware vCentre Converter to prodiuce .vmdk files. It produces two files; a smaller <computer name>.vmdk and the main image <computer-name>-flat.vmdk.

This is the first VM I have tried to add using VirtualBox and when I select

New ... name the machine... set the memory size.... and select "use an existing virtual hard drive", point to the <computer name>.vmdk file on my USB drive I get the error

Failed to open the hard disk E:\<computer name>\<computer name>.vmdk.

Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

If I try to use the <computer name>-flat.vmdk file I get the error;

Failed to open the hard disk E:\<computer name>\<computer name>-flat.vmdk.

Could not get the storage format of the medium 'E:\<computer name>-flat.vmdk' (VERR_NOT_SUPPORTED).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: Medium
Interface: IMedium {29989373-b111-4654-8493-2e1176cba890}
Callee: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

Anyone point me at my obvious mistake.


Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

The smaller file (the descriptor) is the one you should select using the browser. The descriptor is actually a text file - open it with a decent text editor and make sure the image filename doesn't include a path, and make sure the image is in the same folder as the descriptor.

If you continue to have trouble then zip up the descriptor and attach it to a message here. The general form of your vmdk isn't the usual one, but it's not so uncommon either.

Hi - had a look and looks quite undramatic - main file is named but with no path and is sitting in thew same directory on my USB drive. descriptor file looks like this

# Disk DescriptorFile
version=1
encoding="windows-1252"
CID=86c298a0
parentCID=ffffffff
isNativeSnapshot="no"
createType="monolithicFlat"

# Extent description
RW 312586240 FLAT "Black SDS XP laptop FSQ-3HZK24J-flat.vmdk" 0

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "9"
ddb.longContentID = "114f2c5899075579584682c686c298a0"
ddb.uuid = "60 00 C2 91 01 6d 63 51-24 20 d6 c9 4b 12 3a 86"
ddb.geometry.cylinders = "19457"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.thinProvisioned = "1"
ddb.adapterType = "buslogic"
ddb.geometry.biosCylinders = "19457"
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"

The error I get when I try to add this as a new machine is

Failed to open the hard disk E:\Black SDS XP laptop FSQ-3HZK24J\Black SDS XP laptop FSQ-3HZK24J.vmdk.

Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

Looks like it is moaning about the descriptor file itself.

I have tried recreating the image of the PC using various different options in VMware Creator, but all with the same result.

Any ideas welcome

DaveK82 wrote:The error I get when I try to add this as a new machine is

Failed to open the hard disk E:\Black SDS XP laptop FSQ-3HZK24J\Black SDS XP laptop FSQ-3HZK24J.vmdk.

Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

Looks like it is moaning about the descriptor file itself.

I don't think so. The error message is in two parts "Failed to open disk name". And "VBOX_E_OBJECT_NOT_FOUND". The descriptor can reference more than one image, and I thought perhaps it might be referencing a second one, or referencing a physical drive or folder, but apparantly not.

Please show me the contents of folder "E:\Black SDS XP laptop FSQ-3HZK24J\*". I need to see filenames (with extensions) and file sizes. Confirm that the drive letter is still "E:\" since VirtualBox will not tolerate drive and folder name changes once an object is registered.


You might also consider imaging the source drive with Disk2VHD, however the VHD format is not very good, so I would convert it to VDI format first using CloneVDI, before building a VM around the disk.

If drive E: is an external drive then I hope you're aware that a FAT32 formatted drive cannot hold single files larger than 4GB.

Yes, drive is still E:\ and it's NTFS .

I'm afraid the picture isn't totally useful. As I said, I need to know the file name and size - the exact size. I'm particularly interested in the exact size (in bytes) of the image file. I can't get it from that picture.