VirtualBox

Opened 14 years ago

Closed 14 years ago

#6907 closed defect (fixed)

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

Reported by: rusivi Owned by:
Component: other Version: VirtualBox 3.2.2
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

+ 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.

Attachments (5)

fedora13-2010-06-05-05-41-13.log (106.9 KB ) - added by rusivi 14 years ago.
vbox.log Fedora 13 VM
ubuntu-lucid-1004-2010-06-05-06-12-41.log (41.5 KB ) - added by rusivi 14 years ago.
vbox.log Ubuntu Lucid
ubuntu-lucid-1004-2010-06-05-14-15-45.log (45.5 KB ) - added by rusivi 14 years ago.
VBox.log An additional install attempt where the VM becomes corrupted.
Fedora-11-2010-06-06-01-22-49.log (46.8 KB ) - added by rusivi 14 years ago.
vbox.log of corrupted Fedora 11
opensuse111-2010-06-06-14-41-43.log (39.6 KB ) - added by rusivi 14 years ago.
vbox.log openSUSE 11.1 corrupted VM

Download all attachments as: .zip

Change History (16)

by rusivi, 14 years ago

vbox.log Fedora 13 VM

by rusivi, 14 years ago

vbox.log Ubuntu Lucid

by rusivi, 14 years ago

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

by rusivi, 14 years ago

vbox.log of corrupted Fedora 11

by rusivi, 14 years ago

vbox.log openSUSE 11.1 corrupted VM

comment:2 by aeichner, 14 years ago

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!

in reply to:  2 comment:3 by rusivi, 14 years ago

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!

comment:4 by Frank Mehnert, 14 years ago

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

comment:5 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed

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

comment:6 by Julio Lajara, 14 years ago

Resolution: fixed
Status: closedreopened

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.

comment:7 by aeichner, 14 years ago

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.

comment:8 by aeichner, 14 years ago

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

comment:9 by Julio Lajara, 14 years ago

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).

comment:10 by rusivi, 14 years ago

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.

comment:11 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use