﻿ticket	summary	version	type	created	modified	_changetime	_description	_reporter
7982	OVA file made with VirtualBox 4.0 can't be read by VMware ovftool	VirtualBox 4.0.0	defect	2011-01-03T03:16:29Z	2019-07-01T22:52:08Z	2019-07-01T22:52:08Z	"I created a 32-bit openSUSE 11.3 virtual machine using VirtualBox 4.0.0 on a 64-bit openSUSE 11.3 host. The machine works fine. I then exported it to an OVA file using the Export wizard, which did not report any errors. But when I try to read it into VMware using VMware's ""ovftool"" conversion utility, ""ovftool"" reports an error:


znmeb@AlgoCompSynth:~/VirtualBox> ovftool Project\ Kipling.ova .
Opening OVA source: Project Kipling.ova
Opening VMX target: .
Error: OVF Package is not supported by target:
 - Line 25: Unsupported hardware family 'virtualbox-2.2'.


I've attached the XML 'ovf' file - it is indeed calling this a 'virtualbox-2.2' machine, which the VMware tools apparently do not support. I haven't checked the VMware documents yet to see what they do support, but I can do that if you don't have that filed away somewhere.
"	Ed Borasky
11160	.ova image created with Virtual Box, failed to import in VMware	VirtualBox 4.2.4	defect	2012-11-05T20:32:18Z	2020-03-03T15:45:33Z	2020-03-03T15:45:33Z	"The image can be imported into Virtual Box without any problems.

VMware fails:
{{{
The import failed because /home/user/Whonix-Gateway.ova did not pass OVF
specification conformance or virtual hardware compliance checks.

Click Retry to relax OVF specification and virtual hardware compliance
checks and try the import again, or click Cancel to cancel the import.
If you retry the import, you might not be able to use the virtual machine
in VMware Player.
}}}

Who is responsible for the bug? VMware or Virtual Box?

VMware Bug report:
http://communities.vmware.com/thread/423920

Download link Whonix-Gateway.ova:
http://sourceforge.net/projects/whonix/files/whonix-0.4.5/
 
project website:
http://whonix.sf.net

Source code:
https://github.com/adrelanos/Whonix

How the .ova image is created:
https://github.com/adrelanos/Whonix/blob/master/whonix_createvm"	Tsso
12635	Can't import to different basedir	VirtualBox 4.3.6	enhancement	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	2014-01-22T21:03:11Z	"It's nice to have --basedire option for cloning, and the very same option would be quite useful also when importing OVF or other formats.

Otherwise, to move my VM to the correct basedir I first have to import it,  clone --basedir , and finally remove the old copy.

Not very straightforard"	Alex
18571	Vboxmanage export / import not working - invalid 'ovf:id' attribute	VirtualBox 5.2.28	defect	2019-04-18T06:58:57Z	2019-04-19T08:05:40Z	2019-04-19T08:05:40Z	"I'm running am Ubuntu 18.04.2 LTS Server with Virtualbox 5.2.28

Exporting an virtual machine with command line works without any reported error. Result is an *.ova file.

Importing this machine with the command vboxmanage import file.ova ends with this error:

root@nono2018:~# vboxmanage import 20210417_ADC2.ova
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Error reading ""/root/20210417_ADC2.ova"": missing or invalid 'ovf:id' attribute in operating system section element, line 18
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at line 307 of file VBoxManageAppliance.cpp

If I open the *.ova file with a editor, i can see
<Section xsi:type=""ovf:OperatingSystemSection_Type"" ovf:id=""-1160446143"">

Why is the ovf:id negativ?

Any suggestion to solve the problem?

Regards
Michael"	Curval1230
19014	Imported OVA with SATA controller unbootable in BIOS mode	VirtualBox 6.0.12	defect	2019-10-14T18:18:20Z	2019-10-14T18:21:06Z	2019-10-14T18:21:06Z	"'''Steps to reproduce:'''

1. Import OVA/OVF template with following entry for disk controller:

{{{
<Item>
<rasd:Description>SATA Controller</rasd:Description>
<rasd:Caption>sataController0</rasd:Caption>
<rasd:InstanceID>4</rasd:InstanceID>
<rasd:ResourceType>20</rasd:ResourceType>
<rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
<rasd:Address>0</rasd:Address>
<rasd:BusNumber>0</rasd:BusNumber>
</Item>
}}}

2. Try to boot...

'''Expected:'''

System booted up.

'''Actually'''

Got weird behavior -- on first boot strange error appears,
on second boot system freezes after passing GRUB.
Sometimes after several reboots system is booted.

'''Workaround'''
Seems it's similar to #6984.

SATA controller is created with port count equal to 30.
If port count is set to 1, system boots up flawlessly.

Also when SATA controlled is removed via VirtualBox UI,
and new is one added to the system, it's port count is 0.

Tested with Fedora 30. Screenshot attached."	Roman Valov
18730	Ignore extra entries in OVF manifest file (.mf)	VirtualBox 6.0.8	defect	2019-06-28T14:33:18Z	2019-06-28T14:50:03Z	2019-06-28T14:50:03Z	"When a faulty program adds additional entries in the manifest file [1], VirtualBox crashes sometimes without error, sometimes with the error ""NS_ERROR_CALL_FAILED (0x800706BE)"". I propose that it should instead just ignore these entries.

[1] https://code.vmware.com/forums/3086#613566|5230149"	darkdragon
18709	Problems importing .ova appliances on 6.0 versions	VirtualBox 6.0.8	defect	2019-06-14T16:48:19Z	2019-06-22T08:47:18Z	2019-06-22T08:47:18Z	"I've been experiencing an issue when importing .ova appliances on all 6.0 versions, included the latest ( 6.0.8 ).

Just after importing it, it works fine. But if I log on to Windows with another user and try to add (via ""Machine -> Add"" in VirtualBox Manager) the already imported virtual machine, I get an error message with result code ""VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)"", and the operation fails. In the details, it says ""Could not find an open hard disk with UUID ..."". Also, when I'm logged with the same Windows user that imported the .ova appliance, if I remove the virtual machine (without deleting its files) and then try to add it again (""Machine -> Add""), I get the same error. These problems never happened to me on 5.2 versions.

I've realized that, just after importing the .ova appliance, the '''.vbox''' file lacks section '''<MediaRegistry>''', and also subsection '''<HardDisks>'''. Despite this, for the same Windows user that has imported the appliance, for some reason it works at first.

A workaround that I've found is, just after importing the .ova appliance, to remove hard disks attachments and then add them again. Doing this, section <MediaRegistry> (and subsection <HardDisks>) gets written in .vbox file. After this operation, other Windows users can add the virtual machine.

Thank you."	MBE76
20966	Ova/Ovf Signature Verification Issue	VirtualBox 6.1.34	defect	2022-06-03T14:10:11Z	2022-06-03T14:10:11Z	2022-06-03T14:10:11Z	"I sign my ovf file with my own code signing certificate. I am getting a certificate validation error while importing the resulting signed ovf file. I am getting this error even though I upload the SubCA and CA certificates of the signing certificate to the Windows Certificate Store.

I downloaded the source code of the 6.1.34 version of VirtualBox and debug it on my windows machine. And I found that the problem was because of the Name Constraints extension in the SubCA certificate of the certificate I signed.

While reading SubCA certificate from Windows Certificate Store on rtCrStoreAddCertsFromNative method, RTCrX509Certificate_DecodeAsn1 method gives an error in the relevant SubCA certificate. The error message reads: 0x00000000033ae4e8 ""CurCtx.Cert.TbsCertificate.T3.Extensions.papItems[#].ExtnValue.NameConstraings. It gives error 0x80 (expected 0x10/0x20)'

What kind of a problem is there in the SubCA certificate, can you help with this?"	MustafaBayrak
19440	OVF import fails due to incorrect validation of SHA256 digests	VirtualBox 6.1.4	defect	2020-03-27T15:38:37Z	2020-03-27T15:38:37Z	2020-03-27T15:38:37Z	"
When importing a virtual machine (VM) from .ovf file that is accompanied by a
.mf file that specifies file integrity hashes using SHA256, the importer (both
fom the GUI or using VBoxManage) check the integrity of the files as part of
the import process.

Specifically, the file I am seeing the issues is the hard drive of the VM,
provided in VMDK format. The importer exits with an error indicating that the
digest of the VMDK file does not match the one in the .mf file, but using tools
such as sha256 sum I see that the hash does match (see output below).

{{{
$ VBoxManage import ~/vms/testvm0146.ovf

(...snip...)

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): Attribute 'SHA256' on
'testvm0146-0.vmdk' does not match
('03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9' vs.
'19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d')
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component
ApplianceWrap, interface IAppliance
VBoxManage: error: Context: ""RTEXITCODE handleImportAppliance(HandlerArg*)"" at
line 1118 of file VBoxManageAppliance.cpp
}}}

However, sha256sum gives the following output:

{{{
$ sha256sum ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

Additionally, sha246deep also provides the same hash:

{{{
$ sha256deep ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk
}}}

The contents of the testvm0146.mf file are:

{{{
$ cat ~/vms/testvm0146.mf
SHA256(testvm0146-0.vmdk)=
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
SHA256(testvm0146-1.nvram)=
4615577454b8ea7c464f4aee064936e48db52ddb08f23e9ea74ade5e12fce8ce
SHA256(testvm0146.ovf)=
7cbaf2f6dc9ada576ae99ba0f5ef001432650581ad401d4312f297d2737ced49
}}}

As can be seen, the output of sha256sum and the .mf file match
(`03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9`), but for
some reason virtualbox determines the SHA256 hash to be
`19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d`, and thus the
comparison fails.

This has been seen both in Oracle Virtualbox packages (in Ubuntu) as well as Debian-packaged virtualbox (in Debian), which suggests the issue is probably upstream in virtualbox.
"	radnaj
21500	aRC=VBOX_E_FILE_ERROR (0x80bb0004)	VirtualBox-7.0.6	defect	2023-02-12T20:13:33Z	2023-02-12T20:21:59Z	2023-02-12T20:21:59Z	"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



"	pabel
21499	aRC=VBOX_E_FILE_ERROR (0x80bb0004)	VirtualBox-7.0.6	defect	2023-02-12T20:12:20Z	2023-02-12T20:12:20Z	2023-02-12T20:12:20Z	"
If the annotations/describing textfield of the machine => <attached pic> grows up to more than 8192 bytes/signs/text and when this machine once is exported as *.ova it will not be possible to import again and use it in Virtalbox


=> ERROR-Notation while refusing to load *.ova  :

ApplRead ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={86a98347-7619-41aa-aece-b21ac5c1a7e6} aComponent={ApplianceWrap} aText={Element 'Annotation' exceeds limit of 8192 bytes VERR_BUFFER_OVERFLOW (Buffer too small to save result.)}, preserve=false aResultDetail=0



It will be helpful to reserve enough place for text annotations
in my case I store all notices of buildups for new machines as helpful stepbystep reminders



"	pabel
21432	Importing Oracle Solaris 10 and 11 appliances fails to set the memory correctly	VirtualBox-7.0.6	defect	2023-01-25T20:14:37Z	2023-01-28T00:38:46Z	2023-01-28T00:38:46Z	"This looks something like bug 4188 regressed.

Steps:
1. Download the Solaris 10 or 11 Admin VM templates from the Oracle Network.
2. Start VB 7.0.6
3. Select file/Import Appliance.
4. Select the ova file just downloaded and press ""next""
5. Scroll down to change the CPU and memory settings.
6. Observe non-sensical amount of RAM for the system. (see attached)
7. Set it to 4096 MB...
8. Allow the import to complete
9. Check the system settings of the imported VM.
10. Observer 0GB, and on going in, the VM is allocated a mere 4MB. This causes a memory issue on boot.

The issue can be worked around by manually setting RAM post-import... But there is something rotten in Denmark here."	bricowan
21430	Ubuntu kernel panic on Windows 11	VirtualBox-7.0.6	defect	2023-01-24T13:03:26Z	2023-01-24T13:03:26Z	2023-01-24T13:03:26Z	Trying to get the DVWA (Damn Vulnerable Web App) VM working in the current version of OVB running on a Windows 11 laptop.  Every time I tried to start the DVWA VM (an Ubuntu Linux VM) it crashed with a kernel panic.  When I downgraded from Windows 11 back to Windows 10 it started successfully.  	Dr John Mc
