VirtualBox

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#4773 closed defect (duplicate)

Fedora 11 installation fails on Windows XP

Reported by: John Owned by:
Component: installer Version: VirtualBox 3.0.4
Keywords: linux guest installation crash Cc:
Guest type: Linux Host type: Windows

Description

Host is Windows XP fully updated. Guest is Fedora 11 (F11) from stock DVD ISO. Using default F11 installation settings, VirtualBox crashes when installing files from installation media to virtual hard drive. I'm not sure if it's related, but the crash always happens when installing the glibc-common package.

I tried a myriad of virtual hard drive configurations (e.g. piix3, piix4, additional controllers, slots, differencing, etc.). Saw a post about reducing VM memory below 2 GB, but that setting was never above 2 GB.

Originally started-out with a rather customized F11 install, but in the course of trouble-shooting, simplified to the default install. Downloaded a fresh copy of the DVD ISO too; did not help.

Searched the Internet for similar issue but did not see any.

Many VB log files attached. Hopefully you can find something.

Attachments (4)

VBox.log (164.6 KB ) - added by John 15 years ago.
VBox.log.1 (171.6 KB ) - added by John 15 years ago.
VBox.log.2 (46.3 KB ) - added by John 15 years ago.
VBox.log.3 (163.4 KB ) - added by John 15 years ago.

Download all attachments as: .zip

Change History (7)

by John, 15 years ago

Attachment: VBox.log added

by John, 15 years ago

Attachment: VBox.log.1 added

by John, 15 years ago

Attachment: VBox.log.2 added

by John, 15 years ago

Attachment: VBox.log.3 added

comment:1 by John, 15 years ago

Host is i386.

comment:2 by Frank Mehnert, 15 years ago

Resolution: duplicate
Status: newclosed

Please try to decrease the guest RAM setting for this VM. You already used 1500MB which should normally work but which might be an edge case. Try to start with 512MB or 768MB. A Fedora 11 guest usually does not need much more than 512MB RAM. The reason for these problems on 32-Bit Windows is that we have to map the whole guest memory into the virtual memory of the VMM process. The size of the virtual address space for users is only 2GB on Windows -- and the whole process including the binaries etc. must fit there.

I will close this bug as duplicate as there are other open bugs around. In a later release we will tighten this restriction but so far either use less guest memory or switch to a 64-bit host.

comment:3 by Sander van Leeuwen, 15 years ago

64 MB of VRAM is also overkill. 16 is usually more than enough.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use