Importing Oracle Solaris 10 and 11 appliances fails to set the memory correctly => fixed in 7.0.6

[bricowan]

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]

Impossible RAM amount

[bricowan]

It was actually 7.0.4. Sorry. 7.0.6a on Linux imports correctly. Will check the Windows host as soon as a VM completes updating windows..

[paulson]

Thanks for the report. This issue was discovered internally not that long ago and was addressed in VirtualBox 7.0.6. It was a matter of mixing up bytes and megabytes when displaying the memory value in the Export/Import Wizard.