Opened 17 years ago

Closed 11 years ago

#719 closed defect (obsolete)

unable to run as service in win w2k3 host, w2k3 guest

Reported by: luke Owned by:
Component: other Version: VirtualBox 1.5.0
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

Installing as service with srvany, per these instructions

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

Change History (4)

comment:1 by ericallard, 17 years ago

I would use VBOX on a windows 2003 server if I could start VMs as Services. Now, I don't have a clue on how to start a VBox Vm without having to keep a permanent session opened on the server. Any clue on when you will fix this. I LOVE your tech, and would love to FLUSH Virtual Server 2005. Cheers, -Eric

comment:2 by Josh Langner, 15 years ago

A BIG vote for this. VirtualBox needs the ability to run individual instances as separate named services in the background on all Windows OS's. In my case I need it to work with Windows 2008 64-bit.

This needs to be done without the use of a third-party service wrapper.

comment:3 by ponetale, 15 years ago

I have to agree with this. I am running on Windows Home Server (WHS) which is a slight variant of Windows Server 2003 R2 (w2k3r2). I have been trying to dump Virtual Server 2005 for awhile now with no luck. The only thing standing in the way of using VirtualBox full time is the inability for VBoxHeadless to run truly disconnected. Right now the cleanest kludge I have found to run VBoxHeadless from HKLM\Software\Windows\CurrentVersion\Run ... however this leaves a cmd window on the desktop for each VM I start.

comment:4 by Frank Mehnert, 11 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use