ovftool to VI: "No space left for device '#' on parent controller '#'" for IDE Disks

[MikeMatczynski]

I have an OVF I'm trying to import into VI (ESX 3.5) and I'm getting the following error:

Error: OVF Package is not supported by target:
- Line 57: No space left for device '7' on parent controller '6'.

Here's the snippet of OVF:

      <Item>
        <rasd:Address>0</rasd:Address>
        <rasd:ElementName>IDE 0</rasd:ElementName>
        <rasd:InstanceID>6</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:AddressOnParent>0</rasd:AddressOnParent>
        <rasd:ElementName>Harddisk disk1</rasd:ElementName>
        <rasd:HostResource>ovf:/disk/disk1</rasd:HostResource>
        <rasd:InstanceID>7</rasd:InstanceID>
        <rasd:Parent>6</rasd:Parent>
        <rasd:ResourceType>17</rasd:ResourceType>
      </Item>
      <Item>
        <rasd:Address>1</rasd:Address>
        <rasd:ElementName>IDE 1</rasd:ElementName>
        <rasd:InstanceID>8</rasd:InstanceID>
        <rasd:ResourceSubType>piix4</rasd:ResourceSubType>
        <rasd:ResourceType>5</rasd:ResourceType>
      </Item>

Thanks!

Mike

[MikeMatczynski]

It's ovftool 2.0.1

[admin]

what happen if you either use --lax option for ovftool or remove the ResourceSubType for the IDE devices.

eske

Den 21/01/2011 kl. 19.22 skrev MikeMatczynski:

VMware Communities<http://communities.vmware.com/index.jspa>

ovftool to VI: "No space left for device '#' on parent controller '#'" for IDE Disks

created by MikeMatczynski<http://communities.vmware.com/people/MikeMatczynski> in Open Virtualization Format Tool - View the full discussion<http://communities.vmware.com/message/1684303#1684303

[MikeMatczynski]

Deleting the ResourceSubType for both IDE controllers still presents the blocking error.

Invoking ovftool with "--lax" allows the import to proceed, but the imported machine's disks have changed to SCSI

[MikeMatczynski]

After more digging it appears that ESX does not support IDE hard drives, and thus the validation error.

Nonetheless, the error message "No space left for device on parent controller" is extremely misleading!

[ancorp]

I also received this error, and in my case it was a premade image (OVF) from Bitnami and all that is needed to do is to use the VMware vCenter Converter Standalone to convert the OVF to be compatible with ESX/ESXi systems, which changes the underlying disk structure as needed on import I believe. Bitnami does at the time of this writing at least, use underlying IDE disks in their virtual machine images.

More info on their specific process found here: http://wiki.bitnami.org/Virtual_Appliances_Quick_Start_Guide#VMware_ESX_or_ESXi

This may also apply to anyone else not necessarily using Bitnami....but more run into this virtual image using IDE disk problem, and Converter will insulate the problem by changing the VM to a supported type on-the-fly.

My $.02

[MatteoMarchetti]

I have the same issue with the BitNami preconfigured VM. Can you please share what options have you used in order to convert it? Thanks.

[Mr_TAW]

Could it be that old/wrong HW configuration leads to this error? I started to deploy a VM with HW configuration V5 to an ESX server and failed with "no space left on device". Then I changed HW configuration to V10 and now the deployment is running.