Solaris 10 Host reboot - after kernel panic...

[JensMR]

After patching our Solaris System 10 with the actual patch cluster (21.5.2012) and updating VirtualBox to version 4.1.16 our server crashes. In the system messages we always find the attached message ahead of the crash. The referenced CPU number varies and so do the addresses. But the rest is 'stable'.

Since January we used VirtualBox v4.1.8 without any crashes. And after having troubles with version 4.1.16 I reinstalled v4.1.8 but the crashes persist.

System is a SunFire X4600M2 with 8 sockets (Opteron 8356) and 256GB ECC memory. No hardware changes between the running and the crashing system.

The guest systems did not change (predominant is WinXP, but linux systems are also running -- sometimes). The logfiles of the users VMs do not show additional messages. It does not seem to be load-dependent - right now only a small number of users is working on the system (load < 20%).

Did somebody else experience this? Any ideas? Please let me know, if you need additional logfiles, stats or data.

[JensMR]

extract of message log

[JensMR]

extract of message log (VirtBox 4.1.8)

[JensMR]

extract of message log (VirtBox 4.1.16)

[Ramshankar Venkataraman]

Could you please upload VBox.log for the VM that ran when the kernel panicked?

[JensMR]

vbox.log files 04.06.2012 separated by =====

[JensMR]

vbox.log files 06.06.2012 separated by =====

[JensMR]

You will find two new files attached. Each one containing the vbox.log files of the open sessions at the relevant date and time. Within the attached files the logfiles are separated by ===========

Replying to ramshankar:

Could you please upload VBox.log for the VM that ran when the kernel panicked?

[JensMR]

New errors with the new patchset. Previously installing a patch (147441-??) fixed the problem - at least until I installed the recommended patchset from December. Now the problem is back - but this time it is only after having installed the patchset, no changes to VirtualBox.

_The following lines are from the messages file and show what's been happening the first time the system crashed (last lines show the boot process) : See file 28_12_2012.txt

_The second crash shows a Panic (again the last lines show the boot process): See file 31_12_2012.txt

So it seems to be the same error message as in June...

[JensMR]

extract of messages after system crash

[JensMR]

extract of messages after system crash #2

[Frank Mehnert]

Can you be more specific about the patchset you installed? We need a scenario to reproduce the problem and the VBox version for which you saw the problem. A VBox.log of such a VM session would also be helpful.

[JensMR]

Replying to frank:

Can you be more specific about the patchset you installed? We need a scenario to reproduce the problem and the VBox version for which you saw the problem. A VBox.log of such a VM session would also be helpful.

The patchset is the recommended patchset for Oracle Solaris (x86-64):

Title on Oracle Support website: "Patch Recommended OS Patchset Solaris 10 x86: Recommended Patchset for Solaris 10 x86 (Solaris Operating System patches only)"

Last Updated	19-Dec-2012 13:00
Product	Solaris Operating System
Release	Solaris 10 Operating System
Platform	Oracle Solaris on x86-64 (64-bit)		

After installation we have "SunOS mri000 5.10 Generic_147441-27 i86pc i386 i86pc"

The installed VirtualBox worked fine from June until December 27th. After installing the Solaris patchset the whole system crashes - not only the VirtualBox-Processes.

pkginfo -l SUNWvbox gives me (comment for hotline and email removed):

   PKGINST:  SUNWvbox
      NAME:  Oracle VM VirtualBox
  CATEGORY:  application
      ARCH:  i386
   VERSION:  4.1.16,REV=2012.05.22.15.07.78094
   BASEDIR:  /
    VENDOR:  Oracle Corporation
      DESC:  A powerful PC virtualization solution
    PSTAMP:  vbox20120522150817_r78094
  INSTDATE:  Jun 08 2012 15:59
    STATUS:  completely installed
     FILES:      427 installed pathnames
                  10 linked files
                  22 directories
                  43 executables
                  12 setuid/setgid executables
              500411 blocks used (approx)

VBox.log files will be uploaded soon...

[JensMR]

Series of VBOX.log of different users...

[JensMR]

Series of VBOX.log of different users...

[JensMR]

The VBOX.log file has been added twice...

[Frank Mehnert]

Thanks for the logs. Btw, the files VBOX.logs and VBOX.2.logs have the same content.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.