Page 1 of 1

VBox 3.2/4.04 + kernel panic + VirtualBox maintenance mode

Posted: 28. Feb 2011, 11:30
by mrpink
Im running Windows 7 64 bit guest on Solaris 11 Express (issue also exists on OpenIndiana 147/148) using VBox versions 3.2/4.04 in headless mode. Hardware AMD 3800+ EE / Abit nForce 550 MCP Motherboard. Im starting the session via ssh from a ubuntu machine with

Code: Select all

vnohup VBoxHeadless -startvm windows7 < /dev/null > /dev/null 2>&1 &
Kernel panics occur every 10-15 hours or so, after the system reboots (see extract from /var/adm/messages). After reboot, Im not able to start the vm, "svcs -xv" reveals that VirtualBox Zone Access Service is in maintenance mode (see below).

I have to do a full power cycle (poweroff server and unplug) then reboot until it works again.

Any ideas? :cry:


#tail /var/adm/messages

Code: Select all

Feb 28 02:48:42 sun unix: [ID 836849 kern.notice] 
Feb 28 02:48:42 sun ^Mpanic[cpu1]/thread=ffffff02e24d43a0: 
Feb 28 02:48:42 sun genunix: [ID 683410 kern.notice] BAD TRAP: type=d (#gp General protection) rp=ffffff00111f4b30 addr=ffffff02d80bac68
[....]
Feb 28 02:48:42 sun unix: [ID 100000 kern.notice] 
Feb 28 02:48:42 sun genunix: [ID 672855 kern.notice] syncing file systems...
Feb 28 02:48:42 sun genunix: [ID 904073 kern.notice]  done
Feb 28 02:48:43 sun genunix: [ID 111219 kern.notice] dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
[....]
Feb 28 02:50:55 sun PLATFORM: System-Product-Name, CSN: System-Serial-Number, HOSTNAME: sun
Feb 28 02:50:55 sun SOURCE: software-diagnosis, REV: 0.1
Feb 28 02:50:55 sun EVENT-ID: 599c54ab-63d0-ed9d-d8d6-a0aecdf5dc75
Feb 28 02:50:55 sun DESC: A service failed - the instance is restarting too quickly.
Feb 28 02:50:55 sun   Refer to http://sun.com/msg/SMF-8000-YX for more information.
Feb 28 02:50:55 sun AUTO-RESPONSE: The service has been placed into the maintenance state.
Feb 28 02:50:55 sun IMPACT: svc:/application/virtualbox/zoneaccess:default is unavailable.
Feb 28 02:50:55 sun REC-ACTION: Run 'svcs -xv svc:/application/virtualbox/zoneaccess:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted.
andreas@sun:~# fmdump -m

Code: Select all

SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
EVENT-TIME: Mon Feb 28 02:50:54 CET 2011
PLATFORM: System-Product-Name, CSN: System-Serial-Number, HOSTNAME: sun
SOURCE: software-diagnosis, REV: 0.1
EVENT-ID: 599c54ab-63d0-ed9d-d8d6-a0aecdf5dc75
DESC: A service failed - the instance is restarting too quickly.
  Refer to http://sun.com/msg/SMF-8000-YX for more information.
AUTO-RESPONSE: The service has been placed into the maintenance state.
IMPACT: svc:/application/virtualbox/zoneaccess:default is unavailable.
REC-ACTION: Run 'svcs -xv svc:/application/virtualbox/zoneaccess:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted.
andreas@sun:~# svcs -xv

Code: Select all

svc:/application/virtualbox/zoneaccess:default (VirtualBox Zone Access Service.)
 State: maintenance since February 28, 2011 02:50:54 AM CET
Reason: Restarting too quickly.
   See: http://sun.com/msg/SMF-8000-L5
   See: /var/svc/log/application-virtualbox-zoneaccess:default.log
Impact: This service is not running.
andreas@sun:~# tail /var/svc/log/application-virtualbox-zoneaccess:default.log

Code: Select all

[ Feb 28 02:50:43 Executing start method ("/opt/VirtualBox/VBoxZoneAccess"). ]
[ Feb 28 02:50:43 Method "start" exited with status 0. ]
[ Feb 28 02:50:43 Stopping because all processes in service exited. ]
[ Feb 28 02:50:43 Executing stop method (:kill). ]
[ Feb 28 02:50:44 Executing start method ("/opt/VirtualBox/VBoxZoneAccess"). ]
[ Feb 28 02:50:54 Method or service exit timed out.  Killing contract 103. ]
[ Feb 28 02:50:54 Method "start" exited with status 0. ]
[ Feb 28 02:50:54 Stopping because all processes in service exited. ]
[ Feb 28 02:50:54 Executing stop method (:kill). ]
[ Feb 28 02:50:54 Restarting too quickly, changing state to maintenance. ]

Re: VBox 3.2/4.04 + kernel panic + VirtualBox maintenance mode

Posted: 5. Mar 2011, 17:22
by mrpink
running version 3.1.8 for 4 days now without problems. Reverting back seems to be the only way then.