VirtualBox

Opened 15 years ago

Closed 15 years ago

#5170 closed defect (worksforme)

Unexpected Crash on ubuntu 8.04 LTS

Reported by: tril Owned by:
Component: other Version: VirtualBox 3.0.8
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

After updating our servers today (VM and Host), the VM crash after some minutes (3~5 min) uptime. (it goes just down, no error messages or somethink). Network of Host is down after crash for some minutes (2~3 min), then it comes back and the host runs normaly.

I disabled ioapic, pae, nestedpaging, vtxvpid and the 2 nic's, but the vm crashed again. I cannot disable hardwarevirtualisation because the guest System is 64bit. So i gues, its not a problem with the network configuration.

This error comes with VirtualBox 2.2.2, 2.2.4 and 3.0.8 !


Host System OS is ubuntu Hardy 8.04 LTS amd64
Kernel 2.6.24-23-generic and 2.6.24-24-generic

Guest System OS is gentoo hardened amd64
Kernel 2.6.26-hardened


A core dump was not generated, mayby because i start the vm with VBoxHeadless?

The message

[  170.012090] VBoxNetFlt: dbg - g_abExecMemory=ffffffff88420900
[  170.042164] VBoxNetAdp: dbg - g_abExecMemory=ffffffff8843c140

in the dmesg log comes after startup of host (not at vm startup). After vm startup there are no new messages in dmesg or messages log.

Attachments (4)

cpuinfo.txt (1.6 KB ) - added by tril 15 years ago.
cpuinfo of host
dmesg.log (54.9 KB ) - added by tril 15 years ago.
dmesg of host
VBox.log (36.0 KB ) - added by tril 15 years ago.
vbox log
VBoxSettings.txt (1.7 KB ) - added by tril 15 years ago.
vbox configuration

Download all attachments as: .zip

Change History (8)

by tril, 15 years ago

Attachment: cpuinfo.txt added

cpuinfo of host

by tril, 15 years ago

Attachment: dmesg.log added

dmesg of host

by tril, 15 years ago

Attachment: VBox.log added

vbox log

by tril, 15 years ago

Attachment: VBoxSettings.txt added

vbox configuration

comment:1 by Frank Mehnert, 15 years ago

These messages are harmless. Please could you follow these instructions and try to generate a core dump?

comment:2 by tril, 15 years ago

As i write, a core dump was not generated if i follow the instructions to generate a core dump. But this morning we find out, that one of the two hard discs of the host has an read error. If i dd the VM HardDrive File to /dev/null, the host goes down after some GB for some minutes and comes back after, like i describe first.

Its a real confusing error, ping the host just work the whole "blackout"-time, but no other network connections.

So i dont think any more, this is a real virtualbox error. I report if the vm works, after the hard disc of the host is replaced and raid is resynched.

comment:3 by tril, 15 years ago

ok, the new hd is installed and running and the vm is running on virtualbox 3.0.8 :-)

sry for this mistake.

comment:4 by Frank Mehnert, 15 years ago

Resolution: worksforme
Status: newclosed

Thanks for the clarification!

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy