Errors when importing OVF appliances

This is another quick note to self which others may also benefit from....

There was a bug in the Export OVF code of VirtualBox 3.2.8 (and earlier) with vm's that have multiple hard disks. The bug was that each hard disk was given the same unique ID (UUID). Although the export seemed to work correctly, the resultant ovf looked something like this:

...
      <StorageController name="SATA Controller" type="AHCI" PortCount="2" useHostIOCache="false" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
          <AttachedDevice type="HardDisk" port="0" device="0">
            <Image uuid="{eb5b9e44-321f-4cc7-84c3-781fd9d5a661}"/>
          </AttachedDevice>
          <AttachedDevice type="HardDisk" port="1" device="0">
            <Image uuid="{eb5b9e44-321f-4cc7-84c3-781fd9d5a661}"/>
          </AttachedDevice>
      </StorageController> 
...

and so when you came to import the appliance, the import failed because there are 2 disks with the same UUID.

The right solution is that the creator of the vm should upgrade to 3.2.12 or later and re-export again. But a hacky solution involves hand editing the ovf file:

  1. remove the section between:
  2. <vbox:Machine ....>
    ....
    </vbox:Machine>
    
  3. remove/rename the .mf manifest file (because the digital signature will be wrong now we've changed the .ovf file)
  4. try importing again. 

HTH 

- FB 

Comments:

I am getting the exact same error in 4.0.8 of Virtual Box. I checked the .ovf file and the uuid's were different. please revisit this bug.

Posted by guest on May 29, 2011 at 10:31 PM BST #

Idem for me, with version 4.0.8 of Virtual Box.
Regression?

Posted by guest on June 24, 2011 at 01:17 AM BST #

Post a Comment:
Comments are closed for this entry.
About

Fat Bloke

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
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
   
       
Today