Linux guests (Fedora 13, Ubuntu 10.04) install unsuccessfully in VirtualBox 3.2.2

[rusivi]

+ Host information:

lsb_release -rd Description: Ubuntu 9.10 Release: 9.10

apt-cache policy virtualbox-3.2 virtualbox-3.2:

Installed: 3.2.2-62298~Ubuntu~karmic Candidate: 3.2.2-62298~Ubuntu~karmic Version table:

* 3.2.2-62298~Ubuntu~karmic 0

100 /var/lib/dpkg/status

+ Guest information:

Fedora-13-i686-Live.iso downloaded from www.fedoraproject.org

+ Problem summary:

I have tried to install a Fedora VM on 2 separate occasions, and a Ubuntu 10.04 VM on 3, and each time the VMs are corrupted on different parts of the install. VBox.log is for the most recent Fedora VM.

[rusivi]

vbox.log Fedora 13 VM

[rusivi]

vbox.log Ubuntu Lucid

[rusivi]

downstream bugs: ​https://bugs.launchpad.net/ubiquity/+bug/590038 ​https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/590025

[rusivi]

VBox.log An additional install attempt where the VM becomes corrupted.

[rusivi]

vbox.log of corrupted Fedora 11

[rusivi]

vbox.log openSUSE 11.1 corrupted VM

[aeichner]

Can you please try if the following test build fixes the corruption? You have to create a new disk because the fixed bug is triggered only when the image grows.

​http://www.virtualbox.org/download/testcase/VirtualBox-2010-06-04-21-28-39-lin32-rel-3.2.51-r62399.run

Thanks for your help!

[rusivi]

Replying to aeichner:

Can you please try if the following test build fixes the corruption? You have to create a new disk because the fixed bug is triggered only when the image grows.

​http://www.virtualbox.org/download/testcase/VirtualBox-2010-06-04-21-28-39-lin32-rel-3.2.51-r62399.run

Thanks for your help!

I would be glad to try the file but I don't know what it is nor what to do with it... if you have a .deb file I'll take it, otherwise I'll need some instructions on what to do with it. Thanks!

[Frank Mehnert]

VBox 3.2.4 is about to be uploaded. It contains the fix.

[Frank Mehnert]

Please reopen if necessary. Please make sure that you don't put the guest disk image files on an ext4 partition on the host.

[Julio Lajara]

Dude come on lets be real, this is still happening with 3.2.4 and "dont put it on ext4" is not a fix. Is the issue with Vbox or is it with ext4.... if it is ext4 please post the link or info to problem. I cannot install Fedora 13, Slackware or Ubuntu on Vbox, the crap is dead in the water and essential unusable and thus this is truly a show stopping bug in my opinion. So to simply stating dont use ext4 as a host is not suitable if you already have one and you have no choice. So that is not a fix.

[aeichner]

That is easier said than it is done. What should we do in your opinion? Like any other application we have depend on the correctness of the filesystem. We can't do anything if the filesystem isn't working correctly. And is not our fault if distributions use filesystems as defaults which don't have seen that much testing than older ones and use it because it may be faster.

The link to the kernel bug we opened is below: ​https://bugzilla.kernel.org/show_bug.cgi?id=16165

And we are working on a workaround by disabling async I/O if the file is on a ext4 filesystem but this is not easy on Linux.

[aeichner]

Oh and another workaround is to enable the host I/O cache in the controller settings.

[Julio Lajara]

Fair enough, if the bug is not in the app itself feel free to reclose and thank you for the explanation, it was not clear from the previous launchpad links that this was the problem).

[rusivi]

Just installed newest version of VBox (3.2.6) on Ubuntu 9.10 ext4 host, Ubuntu 10.04 guest, installed flawlessly. Nice job on the workaround! This bug is considered closed.