VirtualBox

Ticket #8850 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

FreeBSD Guest freezes completely

Reported by: erik12321 Owned by:
Priority: major Component: guest smp
Version: VirtualBox 4.0.6 Keywords: FreeBDS freezes completely
Cc: Guest type: BSD
Host type: Linux

Description

We have one or more times a week a complete freeze (guru meditation) in one or more of our guest FreeBSD systems. It occurs only in SMP configurations (in our case we have 2xCPU in the FreeBSD guests).

In this situation the virtualbox process for the guest is consuming a lot of cpu time. A trace of this proces is attached.

When we start a debug session for the guest during freeze (a coredump is attached), you can solve the freeze by doing a stop and a step (t). Sometimes you have to switch CPU and repeating the same. The freeze is solved and the machine will run again.

On the guest we use the guest additions for keeping the time right. We also tested this without these additions and using ntpd, then the same freeze problem happens. It happens for FreeBSD 7.2, 8.1 and 8.2 (and probably other versions as well).

The freeze seems to occur when we do snapshots and stopping and resuming of guests.

Our FreeBSD systems run very well on VirtualBox. With this bug we cannot use FreeBSD for production in combination with FreeBSD.

Hope this problem can be solved!

Attachments

strace.vb.out Download (180.3 KB) - added by erik12321 3 years ago.
Trace of process on host system during freeze
freebsd1-2011-05-08-08-01-11.log Download (64.1 KB) - added by erik12321 3 years ago.
VBox.log corresponding with freeze2, core included (freeze2.gz)
readelf.out.txt Download (3.3 KB) - added by erik12321 3 years ago.
result of #readelf -a freebsd1.core

Change History

Changed 3 years ago by erik12321

Trace of process on host system during freeze

comment:1 Changed 3 years ago by erik12321

The coredump is downloadable here:  http://www.cakologics.com/wp-content/uploads/freeze.gz

It is about 282MB.

comment:2 Changed 3 years ago by frank

Which host is that? And please attach a VBox.log file for such a session.

comment:3 Changed 3 years ago by frank

  • Component changed from other to guest smp

comment:4 Changed 3 years ago by frank

Could be related to #7619.

comment:5 Changed 3 years ago by erik12321

The host: Linux 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux Centos 5

The logfiles corresponding to the freeze were already overwritten (sorry for that).The next time the error occurs I will provide the VBox.log for this issue.

Changed 3 years ago by erik12321

VBox.log corresponding with freeze2, core included (freeze2.gz)

comment:6 Changed 3 years ago by erik12321

The coredump corresponding with VBox.log freebsd1-2011-05-08-08-01-11.log can be downloaded here:  http://www.cakologics.com/wp-content/uploads/freeze2.gz

It is about 300MB.

comment:7 Changed 3 years ago by frank

Thanks for the core dump. For some reason my gdb cannot properly interpret this file (warning: Couldn't find general-purpose registers in core file and Cannot access memory at address 0xd87f045e3901c38b). Can you open that core dump on your host yourself?

comment:8 Changed 3 years ago by erik12321

I have the warning, but not the error "Cannot access memory at address...".

I can read the core with readelf. I will attach the result of readelf -a. (I hope it is of any use).

If I need to provide further information, please let me know!

Changed 3 years ago by erik12321

result of #readelf -a freebsd1.core

comment:9 Changed 3 years ago by frank

Still relevant with VBox 4.0.12?

comment:10 Changed 3 years ago by frank

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

No response, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use