VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1561 - 1563 of 16363)

Ticket Resolution Summary Owner Reporter
#8662 obsolete weird PID in exception raised by mach.LockMachine vila
Description

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 <module>

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 "<XPCOMObject method 'lockMachine'>", 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.

#8665 obsolete Display options erratic in machine settings ebonweaver
Description

I have 3 Windows 7 machines created, and each one of them behaves entirely different in the Display section. While all 3 machines have the 3D option disabled, two of them have it enabled whiles being disabled. In other words, the box is checked and can not be unchecked, while the third is unchecked and can not be checked. Two of them state that 36mb is required for 2D acceleration, the third does not. The "third" in each of these cases is a different machine, creating 3 entirely difference behavior sets for no apparent reason. All other settings are identical. All machines work the same when booted, but these settings are all different and can not be made the same, so it's not clear what is broken or what settings they are actually using when powered on.

#8666 obsolete OpenGL calls fail starting with VBox 4.x Mark Vejvoda
Description

I am an opensource developer working on an RTS game called Megaglest (see megaglest.org). In previous versions of Virtual Box i was able to successfully test under virtual box using client extensions and 3d support. My host is Linux and guests are Windows XP and also many flavours of Linux including Ubuntu 8 - current. Starting in Virtualbox 4.x the game gets weird OpenGL errors returned, but the same binaries run fine on the native operating systems and ran fine in 3.x.

I refer to v3.4.0 and the current developer svn version. Source code is available at sourceforge.net here: http://sourceforge.net/projects/megaglest/develop, our dev wiki is here: http://glest.wikia.com/wiki/MG/Development

*NOTE: When disabling 3D guest additions the game does not work as it requires open GL 1.3 or higher reported by the OS.

For additional details join us on freenode.net IRC channel #glest

Thanks

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy