VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (703 - 705 of 16363)

Ticket Resolution Summary Owner Reporter
#720 fixed Failed assertion in current svn ugemkow
Description

The following Assert failure happens in current svn

VMMR0.r0 is importing SUPR0LowFree which we couldn't find

!!Assertion Failed!!
Expression: <NULL>
Location  : /u/user/Build/vbox/src/VBox/HostDrivers/Support/SUPLib.cpp(1377) int supLoadModuleResolveImport(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*)
VMMR0.r0 is importing SUPR0LowFree which we couldn't find

The full logfile is attached

#722 fixed VBoxVRDP unnecessarily connects to an X server on Linux Robert Bordelon
Description

When starting headless sessions, VBoxVRDP apparently connects to the X server if possible, even though it does not actually use it (since that's the whole point of having a headless session.)

This behavior causes any headless sessions started from a graphical environment (i.e. one which has a valid DISPLAY environment variable) to be termimated (and marked "aborted") if the X server is shut down -- for instance if the user logs out. This problem is present whether VBoxVRDP is started directly or via "VBoxManage startvm <Session> -type vrdp".

Here is a log snippet of such a session:

VirtualBox VRDP Headless Interface 1.5.0
(C) 2005-2007 innotek GmbH
All rights reserved

Listening on port 3393

<X server is shut down>

X connection to hostbox:0.0 broken (explicit kill or server shutdown).

This problem can be worked around by unsetting the DISPLAY environment variable before starting headless sessions, or by starting from an non-graphical session, but I believe a more roubust solution would be to have VBoxVRDP not connect to the X server in the first place since such a connection is not needed.

#723 fixed VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH) Ralf Mayer
Description

After a succesfull installation of VirtualBox in a openSuSE 10.2 64bit environment, after installing requested 32-bit drivers and Kernel-sources I can't go further.

Starting a recently created VM( for WinXP, I get the following error message. Since internet search on VERR_VM_DRIVER_VERSION_MISMATCH doesn't get any result, I hope to get a usefull hint from here. Thanks in advance!

Unknown error initializing kernel driver (VERR_VM_DRIVER_VERSION_MISMATCH). VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).

Fehlercode: 0x80004005 Komponente: Console Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

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