VirtualBox

Opened 12 years ago

Closed 8 years ago

Last modified 4 years ago

#11004 closed defect (obsolete)

VirtualBox crash when finishing installation of a Fedora 17 guest on a Windows Vista host

Reported by: terje7601 Owned by:
Component: other Version: VirtualBox 4.2.0
Keywords: fedora Cc:
Guest type: Linux Host type: Windows

Description

On a fresh VirtualBox 4.2 install on a Windows Vista host, I created a new VM for Fedora using all the default settings. I then started the VM & pointed it to the 32-bits .iso file of Fedora 17 ( http://download.fedoraproject.org/pub/fedora/linux/releases/17/Live/i686/Fedora-17-i686-Live-Desktop.iso ) I chose "Install to hard drive", followed the instructions & everything installed just fine. At the end i got a window saying something like "Congratulations! You have successfully installed Fedora. Please reboot" When clicking reboot, the VM crashes: a Windows message with "Oracle VM VirtualBox Manager has stopped working". And when i close the message, the main window of VirtualBox is still open and the status of the VM is "Aborted". At this point i closed VirtualBox & saved the VM log file which you can find in attachment. Note that when restarting the VM again, I eventually get it to boot & the installation seems to have succeeded. If there 's anything else I can do to help resolve this issue, just let me know.

Attachments (6)

VBox.log (55.7 KB ) - added by terje7601 12 years ago.
VBox.2.log (59.6 KB ) - added by wzisinfo 10 years ago.
VBox.3.log (82.6 KB ) - added by clubbing80s 10 years ago.
Clubbing80s VBox.log
applications1.vbox (18.6 KB ) - added by clubbing80s 10 years ago.
Clubbing80s - VM Configuration
Vbox.log (146.1 KB ) - added by JN 4 years ago.
Hardening.log (492.7 KB ) - added by JN 4 years ago.

Download all attachments as: .zip

Change History (27)

by terje7601, 12 years ago

Attachment: VBox.log added

comment:1 by terje7601, 11 years ago

I just tried this again with version 4.2.4, but it still crashes.

comment:2 by MattBenjamin, 11 years ago

I have seen this issue weith Fedora 18, on 4.2.6.r82870.

comment:3 by terje7601, 11 years ago

This is reproducable with Fedora 17 on 4.2.10

comment:4 by ekerazha, 11 years ago

I also have this issue with every VirtualBox 4.2 release.

This issue has been reported multiple times with multiple Linux distributions:

comment:6 by ekerazha, 11 years ago

Please note that this is not Fedora 17 or Windows Vista specific, I can reproduce the issue with multiple Linux distributions on Windows 8.

comment:7 by ekerazha, 11 years ago

Last edited 11 years ago by ekerazha (previous) (diff)

comment:10 by tcreek, 10 years ago

If these issues are not going to be fixed, why not just shutdown VirtualBox down for good?

comment:11 by david1024, 10 years ago

Same issue with windows 8 (and windows 8.1) host with centOS6.5 live or bin cd installs (using centOS6.5 32bit in all cases).

CentOS 6.5 install (any) will crash VirtualBox in the same manner as this bug describes. I've repeated this many many times. (win7/vista compatibility modes, admin priv..., etc..) Once, windows locked up. (couldn't repeat the lockup, just the crash is repeatable.) Host Machine is a Lenovo ThinkPad Twist (model S230u). VB version 4.3.6 r91406.

comment:12 by Frank Mehnert, 10 years ago

david1024, please attach a VBox.log file of such a VM session.

by wzisinfo, 10 years ago

Attachment: VBox.2.log added

comment:13 by wzisinfo, 10 years ago

I got same issue when install OracleLinux 6.4 on Windows 7 host, 64bit. After first packages installation complete, click reboot, Vbox crash, then after reboot, and kdump setup, click finish, VBox crash. Tried Vbox 4.3.8 and 4.2.24, same result. Also tried to remove the VM, and then re-create the vdi on different filesysytem, re-install, but still same result.

Last edited 10 years ago by wzisinfo (previous) (diff)

comment:14 by Frank Mehnert, 10 years ago

wzisinfo, do you have a minidump available?

comment:15 by jsberg, 10 years ago

Fixed a problem with identical symptoms by disabling 3D acceleration.

comment:16 by EscapeArtist, 10 years ago

I've got the same problem (Windows 7 host/Debian guest). Turn of 3D and the problem goes away. This doesn't necessarily happen during install. It happens every time I power off the virtual machine. Every time.

If I have 3D enabled and power off the guest, and then when it crashes on the host, if I do not click "Close the application", then my event system in Windows slows to a crawl: the mouse moves slowly and keyboard entries are received by whatever program at about 1 every 5 seconds or so until I can get to close the application. The second the application is close, Windows becomes responsive again.

comment:17 by clubbing80s, 10 years ago

Hi. I'm experiencing the same issue while installing CentOS6.5_x86_64 Host OS Windows 8.1 Hardware: Samsung NP270E5E - (Intel Core i5-3230M CPU 2.60GHz / 8GB Ram / 700 GB Hard drive) Virtualbox:4.3.12 AntiVirus: Avast

by clubbing80s, 10 years ago

Attachment: VBox.3.log added

Clubbing80s VBox.log

by clubbing80s, 10 years ago

Attachment: applications1.vbox added

Clubbing80s - VM Configuration

comment:18 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

by JN, 4 years ago

Attachment: Vbox.log added

by JN, 4 years ago

Attachment: Hardening.log added

comment:19 by JN, 4 years ago

I have this restart crash with Mint 20 Cinnamon and with Kubuntu 19.10, both on VirtualBox 6.1.10. And in Mint graphics acceleration is not working.

So, please re-open.

(I notice also that adding an attachment removes one's text and gives one no easy way back to the main view of the ticket.)

in reply to:  19 comment:20 by Frank Batschulat (Oracle), 4 years ago

Replying to JN:

I have this restart crash with Mint 20 Cinnamon and with Kubuntu 19.10, both on VirtualBox 6.1.10. And in Mint graphics acceleration is not working.

So, please re-open.

(I notice also that adding an attachment removes one's text and gives one no easy way back to the main view of the ticket.)

There is no point in re-opening an 8 year old and cluttered but against ancient versions of Virtualbox.

Please file a fresh new bug.

comment:21 by JN, 4 years ago

'Please file a fresh new bug.' I would have done. Yet, the existing report contained this: 'Please reopen if still relevant with a recent VirtualBox release.' But if the new advice is to create a new report then I will create one.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use