Ticket #10831 (new defect)

Opened 3 years ago

Last modified 3 years ago

VBoxSVC crashes randomly on Solaris host

Reported by: sunflower Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.18 Keywords: VBoxSVC
Cc: Guest type: Windows
Host type: Solaris

Description (last modified by ramshankar) (diff)

At random intervals (sometimes a few hours, sometimes days) VBoxSVC crashes, causing all VMS running on the host to PowerOff. We are running Windows 7 and Windows XP guests on the same server. Definition for all VM's is identical. On average 25 VM's running on host, with plenty of resources available. All VM's show exactly same error in the logs.

Extract from one of the VM logs
06:19:59.358 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes
06:20:02.391 RTC: period=0x20 (32) 1024 Hz
06:35:36.811 RTC: period=0x200 (512) 64 Hz
10:35:45.318 VirtualBoxClient: detected unresponsive VBoxSVC (rc=NS_ERROR_CALL_FAILED)
10:35:45.318 VBoxHeadless: VBoxSVC became unavailable, exiting.
10:35:45.319 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Running, InUninit=1)
10:35:45.319 VRDP: TCP server closed.
10:35:45.319 Changing the VM state from 'RUNNING' to 'POWERING_OFF'.
10:35:45.319 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The object is not
 ready}, preserve=false
10:35:45.319 ****************** Guest state at power off ******************
10:35:45.319 Guest CPUM (VCPU 0) state:
10:35:45.319 eax=0e9c4fbe ebx=ffdffc70 ecx=ffdffc70 edx=00005c82 esi=ffdffc50 edi=867c4948
10:35:45.319 eip=f1649162 esp=80551434 ebp=80551450 iopl=0         nv up ei pl zr na po nc
10:35:45.319 cs={0008 base=0000000000000000 limit=ffffffff flags=0000c09b} dr0=00000000 dr1=00000000


VBox.log Download (85.0 KB) - added by sunflower 3 years ago.

Change History

Changed 3 years ago by sunflower

comment:1 Changed 3 years ago by ramshankar

  • Description modified (diff)

comment:2 Changed 3 years ago by ramshankar

Core dump of the VBoxSVC process would be useful along with the VBoxSVC log (check ~/.VirtualBox/VBoxSVC.log*)

How to enable core dumps can be found here:

comment:3 follow-up: ↓ 4 Changed 3 years ago by sunflower

I attempted to upload a compressed core file, but I was limited by file size of the attachment facility. The core file is 6.6mb compressed. I have put it on our web site, you can download from here,

The VBoxSVC.log is difficult to get as the VM's immediately startup again once they have crashed overwriting the log files already there. I will see what I can do.

comment:4 in reply to: ↑ 3 Changed 3 years ago by ramshankar

Thanks for the core, will download it in a while.

Replying to sunflower:

The VBoxSVC.log is difficult to get as the VM's immediately startup again once they have crashed overwriting the log files already there. I will see what I can do.

The logs are rotated, the previous logs should be available with a ".x" appended to it's name, eg. VBoxSVC.log (current one), VBoxSVC.log.1 (previous), VBoxSVC.log.2 and so on. So you could provide the VBoxSVC.log.1 if it is the corresponding log when this crash happens.

comment:5 Changed 3 years ago by sunflower

I am aware of this, but for some reason when the fail happens, the broker immediately attempts to startup the VM's and I get 5 or 6 files that all have same contents which is the startup entries of the VBoxSVC. Example below. I am going to try and modify the broker to not startup VM's immediately, so I can preserve the logs.

VirtualBox (XP)COM Server 4.1.18 r78361 solaris.amd64 (Jun 5 2012 16:11:56) release log 00:00:00.000 main Log opened 2012-08-17T10:52:13.794898000Z 00:00:00.000 main OS Product: SunOS 00:00:00.001 main OS Release: 5.10 00:00:00.001 main OS Version: Generic_147441-12 00:00:00.001 main OS Service Pack: Generic_147441-12 00:00:00.001 main Executable: /opt/VirtualBox/amd64/VBoxSVC 00:00:00.001 main Process ID: 86 00:00:00.001 main Package type: SOLARIS_64BITS_GENERIC

comment:6 Changed 3 years ago by sunflower

Is there a restriction in VBox 4.1.18, as I have just noticed that I am unable to launch more than 24 VM's per host ? I have increased the default (sem-ids) semaphore count to 512, as we will need to run about 30-35 VM's per host but the problem still persists, I don't get semaphore errors. Unfortunately, I have had to rollback to 4.0.16, as the customer cannot have these crashes interfering in there production environment. I will have to setup a test environment in the next few days, to continue testing.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use