Custom Query (16363 matches)
Results (841 - 843 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #719 | obsolete | unable to run as service in win w2k3 host, w2k3 guest | ||
| Description |
Installing as service with srvany, per these instructions http://www.tacktech.com/display.cfm?ttid=197. The application is a batch file that calls vboxvrdp -startvm w2k3, after creating machine etc. After starting service, I attempt to connect via rdp and get no result. please note that this works fine run at the command line. My prefered fix would be for the gui or vboxmanger to have the ability to install a machine as a service. The batch files log shows: VirtualBox VRDP Headless Interface 1.5.0 (C) 2005-2007 innotek GmbH All rights reserved Failed to create VirtualBox object! No error information available (rc = 0x80004005). batch file below: c: cd c:\Program Files\innotek VirtualBox\ echo off echo ---Virtual Box Service--- echo set some properties for virtual box "C:\Program Files\innotek VirtualBox\vboxmanage" setproperty vdifolder L:\VirtualBox\VDI\ "C:\Program Files\innotek VirtualBox\vboxmanage" setproperty machinefolder L:\VirtualBox\machines\ del /Q /f L:\VirtualBox\machines\w2k3-projectServer echo copy machine xcopy /Y /H /R /E /C /I L:\VirtualBox\machines\w2k3-projectServer-template L:\VirtualBox\machines\w2k3-projectServer\ echo unregister disk image to machine "C:\Program Files\innotek VirtualBox\vboxmanage" modifyvm w2k3-ProjectServer -hda none echo unregister image "C:\Program Files\innotek VirtualBox\vboxmanage" unregisterimage disk L:\VirtualBox\VDI\w2k3.vdi echo unregisterVM "C:\Program Files\innotek VirtualBox\vboxmanage" unregistervm w2k3-ProjectServer echo register machine "C:\Program Files\innotek VirtualBox\vboxmanage" registervm L:\VirtualBox\machines\w2k3-projectServer\w2k3-ProjectServer.xml echo register disk image "C:\Program Files\innotek VirtualBox\vboxmanage" registerimage disk L:\VirtualBox\VDI\w2k3.vdi echo register disk image to machine "C:\Program Files\innotek VirtualBox\vboxmanage" modifyvm w2k3-ProjectServer -hda L:\VirtualBox\VDI\w2k3.vdi echo start machine "C:\Program Files\innotek VirtualBox\VBoxVRDP" -startvm w2k3-ProjectServer >L:\scripts\Vboxservice.log |
|||
| #720 | fixed | Failed assertion in current svn | ||
| 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 | ||
| 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. |
|||

