[VBoxVmService] -> Discussion & Support
-
- Posts: 15
- Joined: 22. Feb 2010, 15:57
- Primary OS: MS Windows 2003
- VBox Version: PUEL
- Guest OSses: Ubuntu 8.04
Re: [VBoxVmService] -> Discussion & Support
Hello,
I am using savestate with timeout set to 50000. I am also getting error 1053 when closing 2 vm's I have changed the reg key to 50000.
I was wondering if it was possible to have two services one for each vm rather than a single service running 2 vm's. Can I simply duplicate the vms directory and create a new service?. this would be useful for me as I need to stop and start the services independently.
thanks
Paul
I am using savestate with timeout set to 50000. I am also getting error 1053 when closing 2 vm's I have changed the reg key to 50000.
I was wondering if it was possible to have two services one for each vm rather than a single service running 2 vm's. Can I simply duplicate the vms directory and create a new service?. this would be useful for me as I need to stop and start the services independently.
thanks
Paul
Cheers,
Paul Dennis, London England.
http://www.completepicture.co.uk
http://www.hausproject.com
http://www.onionaccounts.com
Paul Dennis, London England.
http://www.completepicture.co.uk
http://www.hausproject.com
http://www.onionaccounts.com
-
- Posts: 39
- Joined: 9. Sep 2010, 11:29
- Primary OS: MS Windows XP
- VBox Version: PUEL
- Guest OSses: WinXP
Re: [VBoxVmService] -> Discussion & Support
Hello Paul,
Am just dropping by to check any new updates on the VboxVmService.
Saw your post. I do not know your objective by running 2 services at the same time but are you aware that the VBoxVmService can start and stop individual VMs thru the command line via the -sd n (shutdown) & -su n (startup) command (n=VM number)? I believe these commands should do, if I understand your concerns correctly.
For the savestate timeout, I guess you need to set this VM delay value much shorter than the registry value, giving enough time for your VMs to shutdown/savestate before Windows kicks-in to terminate the VM. As I understand in your setting (VM delay=registry delay), you will get the 1053 error like I did. I had my VM delay = registry delay before as well at 20s.
Am just dropping by to check any new updates on the VboxVmService.
Saw your post. I do not know your objective by running 2 services at the same time but are you aware that the VBoxVmService can start and stop individual VMs thru the command line via the -sd n (shutdown) & -su n (startup) command (n=VM number)? I believe these commands should do, if I understand your concerns correctly.
For the savestate timeout, I guess you need to set this VM delay value much shorter than the registry value, giving enough time for your VMs to shutdown/savestate before Windows kicks-in to terminate the VM. As I understand in your setting (VM delay=registry delay), you will get the 1053 error like I did. I had my VM delay = registry delay before as well at 20s.
-
- Posts: 92
- Joined: 10. Sep 2009, 13:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: CentOS
Re: [VBoxVmService] -> Discussion & Support
VBoxVmService 2.1 - Codename: "Reindeer" has arrived.
Read the announcement here:
LINK: http://forums.virtualbox.org/viewtopic. ... 95#p167819[/quote]
Read the announcement here:
LINK: http://forums.virtualbox.org/viewtopic. ... 95#p167819[/quote]
-
- Posts: 95
- Joined: 18. Feb 2008, 11:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WinXP/Debian/OSX
- Location: Germany
- Contact:
Re: [VBoxVmService] -> Discussion & Support
PLEASE NOTE THAT REINDEER HAS NOT BEEN TESTED OR APPROVED FOR VIRTUALBOX 4.0 SO FAR.
SO FOR NOW AND UNTIL WE APPROVE VIRTUALBOX 4.0 TO WORK WITH VBOXVMSERVICE 2.1 REINDEER, YOU WILL USE IT AT YOUR OWN RISK!!!
-- Merry Christmas to all of you! Mattz
SO FOR NOW AND UNTIL WE APPROVE VIRTUALBOX 4.0 TO WORK WITH VBOXVMSERVICE 2.1 REINDEER, YOU WILL USE IT AT YOUR OWN RISK!!!
-- Merry Christmas to all of you! Mattz
-
- Posts: 2
- Joined: 27. Dec 2010, 06:51
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: windows 2003
Re: [VBoxVmService] -> Discussion & Support
tried out the vboxvmservice 2.1 Reindeer on windows 7 x64 WITH the LATEST virtual box 4.0.0
Service starts up and stops nicely, but a virtual machine never gets started. The only thing suspicious that I can detect in the log file is the following:
12/26/2010, 20:31:52 - Running coomand: '-nologo modifyvm "vZing" --vrdpport 3002'.
12/26/2010, 20:31:52 - Running coomand: '-nologo startvm "vZing" --type vrdp'.
12/26/2010, 20:31:52 - Unknown VM index number. Are you sure it is defined in the VBoxVmService.ini file?
12/26/2010, 20:32:07 - Received control command: start 0
All the information about each available VM gets dumped just fine, but the following command:
VmServiceControl.exe -su 0
produces the same issue.
If anyone has any ideas, I will experiment.....
Service starts up and stops nicely, but a virtual machine never gets started. The only thing suspicious that I can detect in the log file is the following:
12/26/2010, 20:31:52 - Running coomand: '-nologo modifyvm "vZing" --vrdpport 3002'.
12/26/2010, 20:31:52 - Running coomand: '-nologo startvm "vZing" --type vrdp'.
12/26/2010, 20:31:52 - Unknown VM index number. Are you sure it is defined in the VBoxVmService.ini file?
12/26/2010, 20:32:07 - Received control command: start 0
All the information about each available VM gets dumped just fine, but the following command:
VmServiceControl.exe -su 0
produces the same issue.
If anyone has any ideas, I will experiment.....
-
- Posts: 92
- Joined: 10. Sep 2009, 13:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: CentOS
Re: [VBoxVmService] -> Discussion & Support
The released Reindeer version doesn't work with VirtualBox 4.0.0, due to changes on command line switches happened on 4.0.
VBoxVmService SVN revision 50 fixed that. It is not released, yet. To use it, you'll need to check out the executable files from SVN.
See instructions of using SVN at: http://sourceforge.net/projects/vboxvmservice/develop.
VBoxVmService SVN revision 50 fixed that. It is not released, yet. To use it, you'll need to check out the executable files from SVN.
See instructions of using SVN at: http://sourceforge.net/projects/vboxvmservice/develop.
-
- Posts: 2
- Joined: 27. Dec 2010, 06:51
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: windows 2003
Re: [VBoxVmService] -> Discussion & Support
Beauty! Thanks for the tip. Checked out, copied, executed, worked like a champ. Ship it!
-
- Posts: 10
- Joined: 4. Jan 2011, 15:36
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Fedora 14, Windows 2008 R2
Re: [VBoxVmService] -> Discussion & Support
Version 50 is working for me, although I am getting an "Unknown VM index number" message in the log. However, both the VirtualBox GUI and VBoxManage don't report the VM as running. Is that a VirtualBox bug? Is it because the service runs as the system user? Shouldn't the status of a VM be global?
-
- Posts: 2
- Joined: 5. Jan 2011, 03:54
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: Windows Home Server / Ubuntu
Re: [VBoxVmService] -> Discussion & Support
I'm successfully starting VMs as services, but I get the same "Unknown VM index number" message and the services are not indicated in the GUI. One of the VMs does not appear to be logging into the network, I can't find it's IP address. The mac address in the configuration does not show up as having received a IP lease. Any idea why this might be?
thanks.
thanks.
-
- Posts: 92
- Joined: 10. Sep 2009, 13:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: CentOS
Re: [VBoxVmService] -> Discussion & Support
As long as VMs can start up, "Unknown VM index number" message is nothing to worry about. We are working on better way to make VirtualBox GUI and VBoxManage aware of VMs started by VBoxVmService, but so far don't have much progress, yet.
ydol, I have no idea why other VMs can get IP except one. I would suggest remove all other VMs from VBoxVmService.ini first and debug.
ydol, I have no idea why other VMs can get IP except one. I would suggest remove all other VMs from VBoxVmService.ini first and debug.
-
- Posts: 10
- Joined: 4. Jan 2011, 15:36
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Fedora 14, Windows 2008 R2
Re: [VBoxVmService] -> Discussion & Support
If you execute VBoxManage as Local System it will show the VMs started by VBoxVmService as running. I think it's a defect in VB that running status is not visible to all users and I submitted a ticket.
I hope this gets fixed, but meanwhile, I think VBoxVmService could work around the problem by having an Owner or User setting for each VM in the ini file and impersonating that user when the VM is started instead of starting the VM as Local System.
I hope this gets fixed, but meanwhile, I think VBoxVmService could work around the problem by having an Owner or User setting for each VM in the ini file and impersonating that user when the VM is started instead of starting the VM as Local System.
-
- Posts: 2
- Joined: 5. Jan 2011, 03:54
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: Windows Home Server / Ubuntu
Re: [VBoxVmService] -> Discussion & Support
Thanks for the suggestions. VM startup without logging into network was fixed by changing the host VBoxVmService startup type to "Automatic (Delayed Start)". Guess host needed a while to configure itself before clients could start up reliably.
Looks like all is well. Thanks.
Looks like all is well. Thanks.
-
- Posts: 92
- Joined: 10. Sep 2009, 13:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: CentOS
Re: [VBoxVmService] -> Discussion & Support
VBoxVmService 2.2 - Codename: "Fireworks" has arrived.
Read the announcement here:
LINK: http://forums.virtualbox.org/viewtopic. ... 15#p170618
Read the announcement here:
LINK: http://forums.virtualbox.org/viewtopic. ... 15#p170618
-
- Posts: 2
- Joined: 13. Jan 2011, 14:40
- Primary OS: MS Windows 7
- VBox Version: OSE Debian
- Guest OSses: XP
Re: [VBoxVmService] -> Discussion & Support
I am using Windows 2003 Server, VirtualBox VBoxVmService 4 and 2.2 but does not work.
VBoxVmService.exe -i
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.exe
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.ini
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.log
01/13/2011, 09:16:24 - VBoxVmService
01/13/2011, 09:16:24 - StartServiceCtrlDispatcher failed, error code = 1063
VBoxVmService.ini
[Settings]
ServiceName=VBoxVmService
PathToVBoxSDL=C:\Arquivos de programas\Oracle\VirtualBox\VBoxSDL.exe
PathToVBoxHeadless=C:\Arquivos de programas\Oracle\VirtualBox\VBoxHeadless.exe
PathToVBoxManage=C:\Arquivos de programas\Oracle\VirtualBox\VBoxManage.exe
VBOX_USER_HOME=C:\Documents and Settings\MJSTUDIOS\.VirtualBox
PauseShutdown=5000
[Vm0]
VmName=XP
WorkingDir=E:\vms\
ShutdownMethod=savestate
VrdpPort=3001
VBoxVmService.exe -i
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.exe
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.ini
01/13/2011, 09:16:24 - E:\vms\VBoxVmService.log
01/13/2011, 09:16:24 - VBoxVmService
01/13/2011, 09:16:24 - StartServiceCtrlDispatcher failed, error code = 1063
VBoxVmService.ini
[Settings]
ServiceName=VBoxVmService
PathToVBoxSDL=C:\Arquivos de programas\Oracle\VirtualBox\VBoxSDL.exe
PathToVBoxHeadless=C:\Arquivos de programas\Oracle\VirtualBox\VBoxHeadless.exe
PathToVBoxManage=C:\Arquivos de programas\Oracle\VirtualBox\VBoxManage.exe
VBOX_USER_HOME=C:\Documents and Settings\MJSTUDIOS\.VirtualBox
PauseShutdown=5000
[Vm0]
VmName=XP
WorkingDir=E:\vms\
ShutdownMethod=savestate
VrdpPort=3001
-
- Posts: 92
- Joined: 10. Sep 2009, 13:27
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: CentOS
Re: [VBoxVmService] -> Discussion & Support
Hi mjstudios?
It appears you are still using a config file from the old versions. Just replace it with the VBoxVmService.ini file that comes with latest release and modify items accordingly.
Best regards, FB2000
It appears you are still using a config file from the old versions. Just replace it with the VBoxVmService.ini file that comes with latest release and modify items accordingly.
Best regards, FB2000