id,summary,reporter,owner,description,type,status,priority,component,version,resolution,keywords,cc,guest,host
8662,weird PID in exception raised by mach.LockMachine,vila,,"From a script displaying the currently running VMs, I get a weird traceback under unclear circumstances (say once every 1000 run or something):
vboxslave.py running
Traceback (most recent call last):
File ""/caviar3/babune/bin/vboxslave.py"", line 505, in
run()
File ""/caviar3/babune/bin/vboxslave.py"", line 496, in run
cmd.run()
File ""/caviar3/babune/bin/vboxslave.py"", line 463, in run
self._run_for_slave(name, self.running)
File ""/caviar3/babune/bin/vboxslave.py"", line 376, in _run_for_slave
slave = VboxSlave(name)
File ""/caviar3/babune/bin/vboxslave.py"", line 146, in __init__
self.session = self.open(permit_sharing)
File ""/caviar3/babune/bin/vboxslave.py"", line 149, in open
session = vbox_manager.openMachineSession(self.guest, permit_sharing)
File ""/usr/lib/python2.6/dist-packages/vboxapi/__init__.py"", line 561, in openMachineSession
mach.lockMachine(session, type)
File """", line 3, in lockMachine
xpcom.Exception: 0x80070005 (An unexpected process (PID=0x00003768) has tried to lock the machine 'freebsd-8.0-64bits', while only the process started by launchVMProcess (PID=0xFFFFFFFF) is allowed)
I have no idea where to look for that in the code, but PID=0xFFFFFFFF probably indicates a bug somewhere.
At the very least, it shouldn't generate such a backtrace but point the user to something more meaningful about the cause.",defect,closed,major,other,VirtualBox 4.0.4,obsolete,,,other,other