VirtualBox

Ticket #2540 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Stopping VirtualBox Additions crashes guest

Reported by: nezroy Owned by:
Priority: major Component: guest additions
Version: VirtualBox 2.0.4 Keywords:
Cc: Guest type: other
Host type: other

Description

Using Ubuntu 8.04.1 (32-bit) as a guest on a Vista x64 host machine:

nezroy@rigel:~$ uname -a
Linux rigel 2.6.24-21-server #1 SMP Wed Oct 22 00:18:13 UTC 2008 i686
GNU/Linux
nezroy@rigel:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04.1"

The guest host was able to shutdown fine until I installed the Guest Additions. Now when it attempts to shutdown (shutdown -h now), it gets to the line:

Stopping VirtualBox Additions

and then crashes. The guest OS stops running and I get a Windows error popup with "virtualbox.exe has stopped working", with these details:

Problem signature:
 Problem Event Name:   APPCRASH
 Application Name:     VirtualBox.exe
 Application Version:  0.0.0.0
 Application Timestamp:        4900e8c6
 Fault Module Name:    VBoxVMM.dll
 Fault Module Version: 0.0.0.0
 Fault Module Timestamp:       4900e422
 Exception Code:       c0000005
 Exception Offset:     0000000000073310
 OS Version:   6.0.6001.2.1.0.256.1
 Locale ID:    4105
 Additional Information 1:     dfb3
 Additional Information 2:     dd9c0c95713b811348c36123088edffc
 Additional Information 3:     6e8f
 Additional Information 4:     768b4f65aa11fbcf9568d23b98e3d90f

Also attaching the log.

Attachments

VBox.log Download (35.0 KB) - added by nezroy 5 years ago.

Change History

Changed 5 years ago by nezroy

comment:1 Changed 5 years ago by marco.pallotta

The same thing happens in my Hardy Heron 8.04 (x86_64) host with the guest Hardy Heron server X86. VirtualBox 2.0.4 amd64. From guest console if I try to do a simple rmmod vboxadd the guest system crashes. I tryed to do a core file (following  http://www.virtualbox.org/wiki/Core_dump) but with no success (the core wasn't created but from the command line from which I launch "VirtualBox -startvm VM_NAME" I can see "Segmentation fault"). In Vbox.log I cannot see anything when the crash happens.

comment:2 in reply to: ↑ description Changed 5 years ago by marco.pallotta

The same thing happens in my Hardy Heron 8.04 (x86_64) host with the guest Hardy Heron server X86. VirtualBox 2.0.4 amd64. From guest console if I try to do a simple rmmod vboxadd the guest system crashes. I tryed to do a core file (following  http://www.virtualbox.org/wiki/Core_dump) but with no success (the core wasn't created but from the command line from which I launch "VirtualBox -startvm VM_NAME" I can see "Segmentation fault"). In Vbox.log I cannot see anything when the crash happens.

comment:3 Changed 5 years ago by frank

marco, the core file be indeed very useful for us. Are you sure that your ulimit settings are correct and that you did sudo echo -n 1 > /proc/sys/fs/suid_dumpable as root?

comment:4 Changed 5 years ago by marco.pallotta

Frank, I con confirm that (I tried again to do a core file):

  • user ulimit are unlimited
  • suid_dumpable was set to 1 with "echo -n 1"

When guest crashes no core file is created, maybe because VirtualBox GUI doesn't crash (but only guest gui).

comment:5 Changed 5 years ago by frank

Macro, start the VM with

VirtualBox -startvm VM_NAME

from your home directory. The core file (if some is generated) will then be generated in your home directory.

comment:6 Changed 5 years ago by marco.pallotta

Frank, I tried as you sayd but core file wasn't yet generated. I only have a "Segmantation fault" from command line. I don't really know how to help you to study the issue (I also tried to debug with strace but no useful info was generated)

comment:7 Changed 5 years ago by marco.pallotta

To avoid crashing of my guest system, but still using vboxadd-timesync feature, I remove vboxadd from runlevel 0 and 6 but I have found a strange behavior: if I do an "halt" of my guest and then I start-up it no issue happens (obviously as I removed vboxadd service) but if I do a "reboot" then at startup I have a guest crash at "loading hardware drivers" boot step.

comment:8 Changed 5 years ago by marco.pallotta

In Ubuntu desktop x86 8.04.1 the above issue doesn't happen. No crash!

comment:9 Changed 5 years ago by marco.pallotta

I want to specify my previous comment: in the Ubuntu desktop x86 8.04.1 guest operating system the issue doesn't happen (same host os as I specified on 10/31/08)

comment:10 Changed 5 years ago by marco.pallotta

I tested the issue on the newer VirtualBox 2.0.6 and I noticed no improvements:

  • with Ubuntu server 8.04.1 the problem happens
  • with Ubuntu desktop 8.04.1 the problem doesn't happen

comment:11 Changed 5 years ago by nezroy

I have also tested with 2.0.6 (still with Vista x64 as host), and both Ubuntu 8.04.1 server and Ubuntu 8.10 server guest OSes continue to have this same issue.

My current work-around is to simply comment out the "rmmod" line during the "stop" function for the vboxadd script. The guest OS then shuts down normally.

comment:12 follow-up: ↓ 13 Changed 5 years ago by marco.pallotta

nezroy, I found your same work-around as I explayned on 11/07/08 22:22:09, but then have you the same issue I have on guest reboot? From my above comment: " If I do an "halt" of my guest and then I start-up it no issue happens (obviously as I removed vboxadd service) but if I do a "reboot" then at startup I have a guest crash at "loading hardware drivers" boot step "

comment:13 in reply to: ↑ 12 Changed 5 years ago by nezroy

Replying to marco.pallotta:

nezroy, I found your same work-around as I explayned on 11/07/08 22:22:09, but then have you the same issue I have on guest reboot? From my above comment: " If I do an "halt" of my guest and then I start-up it no issue happens (obviously as I removed vboxadd service) but if I do a "reboot" then at startup I have a guest crash at "loading hardware drivers" boot step "

Yes, I'm also running into that too.

comment:14 follow-up: ↓ 15 Changed 5 years ago by michael

Is this still happening with the current version of VirtualBox?

comment:15 in reply to: ↑ 14 Changed 5 years ago by nezroy

Replying to michael:

Is this still happening with the current version of VirtualBox?

No, it seems to be working correctly now in 2.1.2. The rmmod line is no longer causing this crash.

comment:16 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thank you for the feedback. Closing this ticket.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use