VirtualBox

Ticket #4403 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

crash in VB 3.0.0: VBoxREM.so

Reported by: stephanecharette Owned by:
Component: other Version: VirtualBox 3.0.10
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

VB 3.0.0, both host and guest are Ubuntu 9.04 64-bit.

After several hours of use, my guest window crashes. Complete crash, where the window disappears and nothing about the crash is logged to VBox.log.

In the host, the following is logged to dmesg:

[286059.813502] VirtualBox[1000]: segfault at 0 ip 00007ffc0b8089f0 sp 00007ffc0b262d70 error 4 in VBoxREM.so[7ffc0b7f6000+7a000]

Attachments

VBox.log.1 Download (38.2 KB) - added by stephanecharette 11 years ago.
app1-2009-11-02-16-07-45.log Download (39.0 KB) - added by alexblack 11 years ago.
startup log of the virtual machine that died

Change History

Changed 11 years ago by stephanecharette

comment:1 Changed 11 years ago by ni81036

You'd better mentioned that use 4 vCPU guest config. Guest SMP is still experimental and WIP. Do you see the same problem in 1 vCPU config?

comment:2 Changed 11 years ago by frank

... and does anything change with VBox 3.0.2?

comment:3 Changed 11 years ago by frank

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

I assume this is fixed as there was no response for 2 month.

comment:4 Changed 11 years ago by alexblack

  • Status changed from closed to reopened
  • Resolution fixed deleted

I'm experiencing this problem:

  • Host operating system: Ubuntu Desktop 9.04 x64
  • Guest operating system: Ubuntu Server 9.04 x64
  • VirtualBox 3.0.10 r549097

Yesterday my machine auto-updated to a new version of VirtualBox, the guest server has died twice since then.

From /var/log/syslog:

Nov 3 12:35:12 alex-pc1 kernel: [1039134.249546] VBoxHeadless[15220]: segfault at ffffffff ip 00007f46d27c4595 sp 00007f46d23ecec0 error 4 in VBoxREM.so[7f46d27b8000+7a000]

Changed 11 years ago by alexblack

startup log of the virtual machine that died

comment:5 Changed 11 years ago by sandervl73

A core dump would be very helpful.

comment:6 Changed 11 years ago by sandervl73

  • priority changed from blocker to critical

comment:7 Changed 11 years ago by alexblack

I don't think it created one yet. I read up on this:  http://www.virtualbox.org/wiki/Core_dump and hopefully it will dump core next time it crashes. I imagine the core dump will be huge though.

comment:8 Changed 11 years ago by frank

  • Version changed from VirtualBox 3.0.0 to VirtualBox 3.0.10

If you can provide a core dump please contact me via frank _dot_ mehnert _at_ sun _dot_ com. I can tell you a server where you can upload the file.

comment:9 Changed 10 years ago by frank

Still relevant with VBox 3.1.4?

comment:10 Changed 10 years ago by stephanecharette

As the OP, I don't think I've seen this since the 3.0.0 days in July 2009.

comment:11 Changed 10 years ago by frank

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

Thanks. Others in this ticket: Please reopen if necessary. In that case please contact me for providing a core dump.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use