virtualbox.org

by **mattz** » 12. Aug 2008, 21:00

how many times....?

1. post your VBoxVmService.ini-file!

2. check your VirtualBox.xml-file for relative links and change them to absolute values (as described by nimrod three or four posts earlier)

3. try using BRUTEFORCE as a startup option parameter (all caps)

---mattz

by **diogoscs** » 12. Aug 2008, 21:39

Sorry

like we said in my land "foi mal!!"

This is my .ini file....

Code: Select all Expand view Collapse view: [Settings] ServiceName=VBoxVmService PathToVBoxSDL=C:\Program Files\Sun\xVM VirtualBox\VBoxSDL.exe PathToVBoxVRDP=C:\Program Files\Sun\xVM VirtualBox\VBoxHeadless.exe PathToVBoxManage=C:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe RunAsUser=administrador RunAtDomain=ibeu UserPassword=******* [Vm0] VmName=Bibsrv CommandLineUp=C:\Program Files\Sun\xVM VirtualBox\vms\startup.exe 0 BRUTEFORCE CommandLineDown=C:\Program Files\Sun\xVM VirtualBox\vms\shutdown.exe 0 WorkingDir=C:\Program Files\Sun\xVM VirtualBox\vms StartupMethod=vrdp ShutdownMethod=savestate VrdpPort=3390

I read about the relatives names, but to me everything's ok...

Code: Select all Expand view Collapse view: <MachineEntry uuid="{ca2410bc-85e9-4572-b798-7058a40f3f83}" src="C:\Documents and Settings\administrador\.VirtualBox\Machines\Bibsrv\Bibsrv.xml"/> ..... <VirtualDiskImage filePath="C:\Documents and Settings\administrador\.VirtualBox\VDI\Bibsrv.vdi"/>

by **mattz** » 12. Aug 2008, 22:19

ok, this seems to be ok so far... next steps:

1. check your service control manager for vboxvmservice. it needs to be registered there to work properly.

2. open up a console, cd to your vms dir and try kicking up your vm manually with "startup_cli 0" (optionally add BRUTEFORCE)

does this work?

by **diogoscs** » 13. Aug 2008, 00:09

mattz wrote:ok, this seems to be ok so far... next steps:

1. check your service control manager for vboxvmservice. it needs to be registered there to work properly.

2. open up a console, cd to your vms dir and try kicking up your vm manually with "startup_cli 0" (optionally add BRUTEFORCE)

does this work?

In fact no... When I run the startup_cli 0 open the promtp with...

Code: Select all Expand view Collapse view: No previously started VM operations to wait for. Continuing... Reading global parameters... Reading parameters for VM0... Using custom VRDP-Port: 3390 C:\Program Files\Sun\xVM VirtualBox\vms\tmp\u_0_sub.bat ==> C:\Program Files\Sun\xVM VirtualBox\vms\tmp\u_0_sub.exe (-hidden) C:\Program Files\Sun\xVM VirtualBox\vms\tmp\u_0_run.bat ==> C:\Program Files\Sun\xVM VirtualBox\vms\tmp\u_0_run.exe (-hidden) Installing temporary service "runserv"... Shutting down "runserv" to avoid malfunctions... Restarting "runserv"... Starting VM: "Bibsrv" via vrdp as a service using account: "administrador"... Moving lockfile: STARTUP to RUN Shutting down "runserv"... Removing temporary service "runserv"... Removing temporary helpfiles... Done. -- Hit any key to quit --

I look for some VBoxHeadless.exe in taskmanager but he not show, only vboxsvc (he disapear some times )

And the service is ok... he start when I turn on the machine, don't create any message in Event Viewer he start vboxsvc too but not the VBoxHeadless.exe

by **originofstorms** » 15. Aug 2008, 10:24

okay, at long last, figured out why runasv wasnt behaving for me. after quite a bit of detective work, i found that despite running as user micah, and being able to do things that only user micah can do, runasv gaves me the profile of Default User in windows 2003 server. so, i used the same fsutils technique to hardlink ~\.VirtualBox\VirtualBox.xml as Documents and Settings\Default User\.VirtualBox\VirtualBox.xml. ta da.

many thanks to nimrod for the "> output.log" suggestion. that put me on the right track. sticking the output of "vboxmanage list vms" and "vboxmanage list systemproperties" into that log was very helpful too.

by **diogoscs** » 15. Aug 2008, 20:41

originofstorms wrote:okay, at long last, figured out why runasv wasnt behaving for me. after quite a bit of detective work, i found that despite running as user micah, and being able to do things that only user micah can do, runasv gaves me the profile of Default User in windows 2003 server. so, i used the same fsutils technique to hardlink ~\.VirtualBox\VirtualBox.xml as Documents and Settings\Default User\.VirtualBox\VirtualBox.xml. ta da.

many thanks to nimrod for the "> output.log" suggestion. that put me on the right track. sticking the output of "vboxmanage list vms" and "vboxmanage list systemproperties" into that log was very helpful too.

I didn't uderstand something... where exactly I put the "> output.log", I didn't find the u_0_sub.bat...

by **mattz** » 9. Oct 2008, 23:53

There is no more need to patch VBoxVmService yourself, in order to obtain more or more detailed information on the status of it's components. The logging within the new release 20081009 now combines all component feedback into one single logfile.

--mattz

by **jstanko** » 13. Dec 2008, 20:44

I am at a total loss. I have one vm that I am trying to control. The vm starts when the computer starts, but never restores from the save state. Whether it is not saving the state on shutdown or ignoring upon start I can't figure out. (I am using XP SP3 as a host os with vbox 2.0.6.)

Code: Select all Expand view Collapse view: [Settings] ServiceName=VBoxVmService PathToVBoxSDL=C:\Program Files\Sun\xVM VirtualBox\VBoxSDL.exe PathToVBoxHeadless=C:\Program Files\Sun\xVM VirtualBox\VBoxHeadless.exe PathToVBoxManage=C:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe RunAtDomain=Apollo-8 RunAsUser=RemotePC UserPassword=******* [Vm0] VmName=RemotePC CommandLineUp=C:\Documents and Settings\RemotePC\vboxvms\startup.exe 0 BRUTEFORCE CommandLineDown=C:\Documents and Settings\RemotePC\vboxvms\shutdown.exe 0 WorkingDir=C:\Documents and Settings\RemotePC\vboxvms StartupMethod=vrdp ShutdownMethod=savestate VrdpPort=6000

Code: Select all Expand view Collapse view: <MachineEntry uuid="{8f9ad6a6-54d5-4181-b592-1b08749855d9}" src="C:\Documents and Settings\RemotePC\.VirtualBox\Machines\RemotePC\RemotePC.xml"/> ... <VirtualDiskImage filePath="C:\Documents and Settings\RemotePC\.VirtualBox\VDI\RemotePC.vdi"/>

(I'm not sure where the log starts and stops so I have just cut a portion.)

Code: Select all Expand view Collapse view: 12/13/2008, 09:58:01 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/13/2008, 09:58:01 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/13/2008, 09:58:01 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/13/2008, 09:58:01 - VBoxVmService BRUTEFORCE: Killing all existing run- / lockfiles for this VM... killing: "C:\Documents and Settings\RemotePC\vboxvms\run\*.vm0" No previously started VM operations to wait for. Continuing... Reading global parameters... Reading parameters for VM0... VirtualBox Command Line Management Interface Version 2.0.6 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. [!] FAILED calling virtualBox->FindMachine (Bstr(argv[0]), machine.asOutParam()) at line 2551! [!] Primary RC = E_INVALIDARG (0x80070057) - One or more arguments are invalid [!] Full error info present: true , basic error info present: true [!] Result Code = E_INVALIDARG (0x80070057) - One or more arguments are invalid [!] Text = Could not find a registered machine named 'RemotePC' [!] Component = VirtualBox, Interface: IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} [!] Callee = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} Using custom VRDP-Port: 6000 VirtualBox Command Line Management Interface Version 2.0.6 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. [!] FAILED calling virtualBox->FindMachine(Bstr(argv[0]), machine.asOutParam()) at line 4508! [!] Primary RC = E_INVALIDARG (0x80070057) - One or more arguments are invalid [!] Full error info present: true , basic error info present: true [!] Result Code = E_INVALIDARG (0x80070057) - One or more arguments are invalid [!] Text = Could not find a registered machine named 'RemotePC' [!] Component = VirtualBox, Interface: IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} [!] Callee = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} Installing temporary service "runserv"... Shutting down "runserv" to avoid malfunctions... 12/13/2008, 09:58:12 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/13/2008, 09:58:12 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/13/2008, 09:58:12 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/13/2008, 09:58:12 - VBoxVmService 12/13/2008, 09:58:12 - Killed service runserv Restarting "runserv"... 12/13/2008, 09:58:15 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/13/2008, 09:58:15 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/13/2008, 09:58:15 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/13/2008, 09:58:15 - VBoxVmService 12/13/2008, 09:58:15 - Ran service runserv Starting VM: "RemotePC" via vrdp as a service using account: "RemotePC"... Moving lockfile: STARTUP to RUN Shutting down "runserv"... 12/13/2008, 09:58:34 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/13/2008, 09:58:34 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/13/2008, 09:58:34 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/13/2008, 09:58:34 - VBoxVmService 12/13/2008, 09:58:34 - Killed service runserv Removing temporary service "runserv"... Removing temporary helpfiles...

Any ideas?

Thanks in advance,
Jared

by **jstanko** » 14. Dec 2008, 02:37

UPDATE: If I manually shut down the vboxvmservice it will save the state and work properly. (I can just restart the service or I can reboot (after stopping manually) and it will start properly.)

Any ideas?

Thanks in advance,
Jared

by **mattz** » 15. Dec 2008, 00:19

did you link the file as described in the docs? seems to me, that vb doesn't seem to find a registered machine called "RemotePC". this usually indicates, that a wrong VirtualBox.xml-file is parsed....

by **jstanko** » 15. Dec 2008, 01:38

UPDATE: I checked the hardlink to Virtualbox.xml and there didn't appear to be any problem.

I recently decided to shutdown the service manually and compare that log to a windows shutdown. The following are the differences.

Manual service shutdown:

Code: Select all Expand view Collapse view: No previously started VM operations to wait for. Continuing... Reading global parameters... Reading parameters for VM0... Generating temporary helpfiles... Installing temporary service "runserv"... Shutting down "runserv" to avoid malfunctions... 12/14/2008, 18:03:21 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:03:21 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:03:21 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:03:21 - VBoxVmService 12/14/2008, 18:03:21 - Killed service runserv Restarting "runserv"... 12/14/2008, 18:03:24 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:03:24 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:03:24 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:03:24 - VBoxVmService 12/14/2008, 18:03:24 - Ran service runserv Shutting down serviced VM: "RemotePC" with option savestate running on account: "RemotePC"... Removing lockfile: RUN Removing lockfile: SHUTDOWN Shutting down "runserv"... 12/14/2008, 18:03:43 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:03:43 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:03:43 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:03:43 - VBoxVmService 12/14/2008, 18:03:43 - Killed service runserv Removing temporary service "runserv"... Removing temporary helpfiles... 12/14/2008, 18:05:39 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:05:39 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:05:39 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:05:39 - VBoxVmService BRUTEFORCE: Killing all existing run- / lockfiles for this VM...

VS

Direct windows xp shutdown:

Code: Select all Expand view Collapse view: No previously started VM operations to wait for. Continuing... Reading global parameters... Reading parameters for VM0... Generating temporary helpfiles... Installing temporary service "runserv"... Shutting down "runserv" to avoid malfunctions... 12/14/2008, 18:23:17 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:23:17 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:23:17 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:23:17 - VBoxVmService 12/14/2008, 18:23:17 - OpenSCManager failed, error code = 1115 12/14/2008, 18:23:17 - Failed to kill service runserv Restarting "runserv"... 12/14/2008, 18:23:20 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:23:20 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:23:20 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:23:20 - VBoxVmService 12/14/2008, 18:23:21 - OpenSCManager failed, error code = 1115 12/14/2008, 18:23:21 - Failed to run service runserv 12/14/2008, 18:24:10 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.exe 12/14/2008, 18:24:10 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.ini 12/14/2008, 18:24:10 - C:\Documents and Settings\RemotePC\vboxvms\VBoxVmService.log 12/14/2008, 18:24:10 - VBoxVmService BRUTEFORCE: Killing all existing run- / lockfiles for this VM...

(The virtualbox error about not finding the machine named "RemotePC" seemed to be a dead end because it appeared both when it didn't work and when it worked just fine.)

I put "OpenSCManager failed, error code = 1115" in google and was unfortunately unable to make heads or tails of the results. Any ideas?

Thanks for your time,
Jared

by **mattz** » 15. Dec 2008, 01:54

i found this article on msdn:
http://msdn.microsoft.com/en-us/library/ms684323(VS.85).aspx

apparently there is a problem accessing the windows service control manager on your host computer. since vboxvmservice seems to be unable to install/kill/reinstall runserv, it is impossible to issue the "runasv"-command, that would bring the VM up or down.

what exactly the problem is there is way out of my scope, since i am not familiar enough with windows' internal structures.... sorry...

any win32 developers reading this????

by **nabamer.** » 19. Dec 2008, 01:37

I'm trying to make run VirtualBox on Win Server 2008 as a server.

After initial pain I got the service installed and everything seems to be ok but VirtualBox process does not comes running.

The log:

Code: Select all Expand view Collapse view: 12/18/2008, 23:27:30 - C:\vms\VBoxVmService.exe 12/18/2008, 23:27:30 - C:\vms\VBoxVmService.ini 12/18/2008, 23:27:30 - C:\vms\VBoxVmService.log 12/18/2008, 23:27:30 - VBoxVmService BRUTEFORCE: Killing all existing run- / lockfiles for this VM... No previously started VM operations to wait for. Continuing... Reading global parameters... Reading parameters for VM0... VirtualBox Command Line Management Interface Version 2.0.6 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: lok Guest OS: Ubuntu UUID: 15bc75ba-dd27-4720-93ef-5fa2a2f21d46 Config file: C:\Windows\system32\config\systemprofile\.VirtualBox\Machines\lok\lok.xml Memory size: 512MB VRAM size: 8MB Boot menu mode: message and menu ACPI: on IOAPIC: off PAE: on Time offset: 0 ms Hardw. virt.ext: off Nested Paging: off State: aborted (since 2008-12-18T00:35:21.000000000) Monitor count: 1 Floppy: empty SATA: disabled Primary master: C:\VM\lok\lokfs.vdi (UUID: 9ae11b2c-e705-4766-84ef-37821f2eb4fe) DVD: empty NIC 1: MAC: 080027FDBD0E, Attachment: Host Interface 'VBOXNET1', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps NIC 2: disabled NIC 3: disabled NIC 4: disabled UART 1: disabled UART 2: disabled Audio: disabled (Driver: Unknown, Controller: Unknown) Clipboard Mode: Bidirectional VRDP: disabled USB: enabled USB Device Filters: <none> Shared folders: <none> Guest: Statistics update: disabled Using custom VRDP-Port: 3001 VirtualBox Command Line Management Interface Version 2.0.6 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Installing temporary service "runserv"... Shutting down "runserv" to avoid malfunctions... 12/18/2008, 23:27:32 - c:\vms\VBoxVmService.exe 12/18/2008, 23:27:32 - c:\vms\VBoxVmService.ini 12/18/2008, 23:27:32 - c:\vms\VBoxVmService.log 12/18/2008, 23:27:32 - VBoxVmService 12/18/2008, 23:27:32 - Killed service runserv Restarting "runserv"... 12/18/2008, 23:27:35 - c:\vms\VBoxVmService.exe 12/18/2008, 23:27:35 - c:\vms\VBoxVmService.ini 12/18/2008, 23:27:35 - c:\vms\VBoxVmService.log 12/18/2008, 23:27:35 - VBoxVmService 12/18/2008, 23:27:35 - Ran service runserv Starting VM: "lok" via vrdp as a service using account: "spyro"... Moving lockfile: STARTUP to RUN Shutting down "runserv"... 12/18/2008, 23:27:55 - c:\vms\VBoxVmService.exe 12/18/2008, 23:27:55 - c:\vms\VBoxVmService.ini 12/18/2008, 23:27:55 - c:\vms\VBoxVmService.log 12/18/2008, 23:27:55 - VBoxVmService 12/18/2008, 23:27:55 - Killed service runserv Removing temporary service "runserv"... Removing temporary helpfiles...

The config:

Code: Select all Expand view Collapse view: [Settings] ServiceName=VBoxVmService PathToVBoxSDL="C:\Program Files\Sun\xVM VirtualBox\VBoxSDL.exe" PathToVBoxHeadless="C:\Program Files\Sun\xVM VirtualBox\VBoxHeadless.exe" PathToVBoxManage="C:\Program Files\Sun\xVM VirtualBox\VBoxManage.exe" RunAtDomain=somemachinename RunAsUser=someuser UserPassword=somepwd [Vm0] VmName=lok CommandLineUp="c:\vms\startup.exe 0 BRUTEFORCE" CommandLineDown="c:\vms\shutdown.exe 0" WorkingDir=C:\vms StartupMethod=vrdp ShutdownMethod=poweroff VrdpPort=3001

VirtualBox 2.0.6 and
VBoxVmService (rel20081009)
is used.

Can anyone help ?

by **mattz** » 19. Dec 2008, 08:23

first off - i personally never used vboxvmservice on vista/2008srvr and therefore do not know whether it is going to work at all. reports have indicated that it is possible though.... there are some hints on the differences between a vista- and a winxp/2003-install in the SUPPLIED DOCUMENTATION, which i would REALLY advise you to re-read carefully.
after a quick glance at your logs and ini-file, allow me to point your special attention to section 9 - "installation & operation instructions":

Open up the "VBoxVmService.ini" file, located in the root directory of your installation.

Adjust the values within to suit your environment:

!!!IMPORTANT!!!

EVEN IF YOUR PATHVALUES OR VM-NAMES CONTAIN BLANKS:

DON'T USE QUOTES ("" or '') WITH THE VALUES YOU ENTER HERE!!!

now take a look at your post and tell me what you see there... seriously guys - i am always taking the time trying to help out, but if i see stuff like that posted here --- stuff that i especially pointed at in the docs --- it's kinda hard for me to bring up the motivation to even follow this thread in the future...

--- mattz

by **nabamer.** » 19. Dec 2008, 11:36

I'm sorry to insult you this way, my mistake that I did not removed "" from *.ini file however before I've put them there I've tried the same without quotes and result have been the same.
The other thing is that if there would be something wrong with those entries I would say log would be slightly different.

Seriously if someone is not happy to help then I'm not asking those for help and the flamewar answer style is much not appreciated. Before I asked the question here I went through all possibilities. I'm in development myself and I know how frustrating it is when your users does not spent time with documentation but believe me it is so much simpler for me to search for existing answer first than actually ask someone here.

I'm SORRY !

virtualbox.org

[VBoxVmService] -> Discussion & Support

runasv ran as Default User

Re: runasv ran as Default User

VM does not restore from savestate

VM does not restore from savestate

VM does not restore from savestate

VBoxVmService log looking ok but VM still not starting

Who is online