[VBoxVmService] -> Discussion & Support

Discussions related to using VirtualBox on Windows hosts.

Re: [VBoxVmService] -> Discussion & Support

Postby utushalla » 26. Mar 2016, 16:46

Hi all.
Have BSoD when start VM(windows 7 emu)

PC: Windows server 2003, 4GB RAM,i7 920 2.67\2.67
Code: Select all   Expand viewCollapse view
c84.1118: Log file opened: 5.0.16r105871 g_hStartupLog=00000fe0 g_uNtVerCombined=0x520ece20
c84.1118: \SystemRoot\System32\ntdll.dll:
c84.1118:     CreationTime:    2003-04-03T12:00:00.000000000Z
c84.1118:     LastWriteTime:   2011-11-22T16:29:04.000000000Z
c84.1118:     ChangeTime:      2013-03-20T16:08:10.953125000Z
c84.1118:     FileAttributes:  0x20
c84.1118:     Size:            0xbdc00
c84.1118:     NT Headers:      0xe0
c84.1118:     Timestamp:       0x4ecbcdd1
c84.1118:     Machine:         0x14c - i386
c84.1118:     Timestamp:       0x4ecbcdd1
c84.1118:     Image Version:   5.2
c84.1118:     SizeOfImage:     0xc3000 (798720)
c84.1118:     Resource Dir:    0x90000 LB 0x2e250
c84.1118:     ProductName:     Microsoft® Windows® Operating System
c84.1118:     ProductVersion:  5.2.3790.4937
c84.1118:     FileVersion:     5.2.3790.4937 (srv03_sp2_gdr.111121-0236)
c84.1118:     FileDescription: NT Layer DLL
c84.1118: \SystemRoot\System32\kernel32.dll:
c84.1118:     CreationTime:    2012-10-03T07:26:19.000000000Z
c84.1118:     LastWriteTime:   2012-10-03T07:26:19.000000000Z
c84.1118:     ChangeTime:      2013-03-20T16:28:33.484375000Z
c84.1118:     FileAttributes:  0x20
c84.1118:     Size:            0xfd800
c84.1118:     NT Headers:      0xf0
c84.1118:     Timestamp:       0x506be89c
c84.1118:     Machine:         0x14c - i386
c84.1118:     Timestamp:       0x506be89c
c84.1118:     Image Version:   5.2
c84.1118:     SizeOfImage:     0x102000 (1056768)
c84.1118:     Resource Dir:    0x90000 LB 0x6a6c8
c84.1118: supR3HardenedWinFindAdversaries: 0x400
c84.1118: \SystemRoot\System32\drivers\MpFilter.sys:
c84.1118:     CreationTime:    2012-08-30T12:03:50.000000000Z
c84.1118:     LastWriteTime:   2013-01-20T05:59:04.000000000Z
c84.1118:     ChangeTime:      2013-03-19T17:14:13.250000000Z
c84.1118:     FileAttributes:  0x20
c84.1118:     Size:            0x2fae0
c84.1118:     NT Headers:      0x268
c84.1118:     Timestamp:       0x509173a2
c84.1118:     Machine:         0x14c - i386
c84.1118:     Timestamp:       0x509173a2
c84.1118:     Image Version:   6.2
c84.1118:     SizeOfImage:     0x2b400 (177152)
c84.1118:     Resource Dir:    0x27200 LB 0x928
c84.1118:     ProductName:     Microsoft Malware Protection
c84.1118:     ProductVersion:  4.2.0206.0
c84.1118:     FileVersion:     4.2.0206.0
c84.1118:     FileDescription: Microsoft antimalware file system filter driver
c84.1118: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume2\VirtualBox'
c84.1118: Calling main()
c84.1118: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
c84.1118: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume2\VirtualBox'
c84.1118: SUPR3HardenedMain: Respawn #1
c84.1118: System32:  \Device\HarddiskVolume1\WINDOWS\system32
c84.1118: WinSxS:    \Device\HarddiskVolume1\WINDOWS\WinSxS
c84.1118: KnownDllPath: C:\WINDOWS\system32
c84.1118: '\Device\HarddiskVolume2\VirtualBox\VirtualBox.exe' has no imports
c84.1118: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\VirtualBox\VirtualBox.exe)
c84.1118: supR3HardNtEnableThreadCreation:
c84.1118: supR3HardNtDisableThreadCreation: pvLdrInitThunk=7c81a176 pvNtTerminateThread=7c827a8d
c84.1118: supR3HardenedWinDoReSpawn(1): New child 105c.11b8 [kernel32].
c84.1118: supR3HardNtChildGatherData: PebBaseAddress=7ffd7000 cbPeb=0x230
c84.1118: supR3HardNtPuChFindNtdll: uNtDllParentAddr=7c800000 uNtDllChildAddr=7c800000
c84.1118: supR3HardenedWinSetupChildInit: uLdrInitThunk=7c81a176
c84.1118: supR3HardenedWinSetupChildInit: Start child.
c84.1118: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
c84.1118: supR3HardNtChildPurify: Startup delay kludge #1/0: 518 ms, 0 sleeps
c84.1118: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
c84.1118:  *00000000-fffeffff 0x0001/0x0000 0x0000000
c84.1118:  *00010000-0000efff 0x0004/0x0004 0x0020000
c84.1118:   00011000-00001fff 0x0001/0x0000 0x0000000
c84.1118:  *00020000-0001efff 0x0004/0x0004 0x0020000
c84.1118:   00021000-00011fff 0x0001/0x0000 0x0000000
c84.1118:  *00030000-fff31fff 0x0000/0x0004 0x0020000
c84.1118:   0012e000-0012cfff 0x0104/0x0004 0x0020000
c84.1118:   0012f000-0012dfff 0x0004/0x0004 0x0020000
c84.1118:  *00130000-0012afff 0x0002/0x0002 0x0040000
c84.1118:   00135000-ffe69fff 0x0001/0x0000 0x0000000
c84.1118:  *00400000-00400fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   00401000-00477fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   00478000-00478fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   00479000-004b2fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004b3000-004b3fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004b4000-004b4fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004b5000-004b5fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004b6000-004b6fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004b7000-004bbfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004bc000-004befff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   004bf000-00502fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume2\VirtualBox\VirtualBox.exe
c84.1118:   00503000-a0a05fff 0x0001/0x0000 0x0000000
c84.1118:  *60000000-5fff9fff 0x0080/0x0080 0x0040000 !!
c84.1118: supHardNtVpScanVirtualMemory: Unmapping exec mem at 60000000 (60000000/60000000 LB 0x6000)
c84.1118:   60006000-4380bfff 0x0001/0x0000 0x0000000
c84.1118:  *7c800000-7c800fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\WINDOWS\system32\ntdll.dll
c84.1118:   7c801000-7c889fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\WINDOWS\system32\ntdll.dll
c84.1118:   7c88a000-7c88ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\WINDOWS\system32\ntdll.dll
c84.1118:   7c890000-7c8c2fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\WINDOWS\system32\ntdll.dll
c84.1118:   7c8c3000-791d5fff 0x0001/0x0000 0x0000000
c84.1118:  *7ffb0000-7ff8bfff 0x0002/0x0002 0x0040000
c84.1118:   7ffd4000-7ffd0fff 0x0001/0x0000 0x0000000
c84.1118:  *7ffd7000-7ffd5fff 0x0004/0x0004 0x0020000
c84.1118:   7ffd8000-7ffd0fff 0x0001/0x0000 0x0000000
c84.1118:  *7ffdf000-7ffddfff 0x0004/0x0004 0x0020000
c84.1118:  *7ffe0000-7ffdefff 0x0002/0x0002 0x0020000
c84.1118:   7ffe1000-7ffd1fff 0x0001/0x0002 0x0020000
c84.1118: VirtualBox.exe: timestamp 0x56d9bd6d (rc=VINF_SUCCESS)
c84.1118: '\Device\HarddiskVolume2\VirtualBox\VirtualBox.exe' has no imports
c84.1118: '\Device\HarddiskVolume1\WINDOWS\system32\ntdll.dll' has no imports
c84.1118: supR3HardNtChildPurify: cFixes=1 g_fSupAdversaries=0x400
utushalla
 
Posts: 1
Joined: 26. Mar 2016, 16:25

Re: [VBoxVmService] -> Discussion & Support

Postby iZE » 19. Apr 2016, 22:28

Hi Mattz and everyone else!

I have a problem and I think VBoxVmService could be an excellent tool to solve my problem. I want to start a docker image on bootup on a Windows machine. It must start up even if noone logs in on the machine.

When i run "docker-machine start" from the command line it starts up a Virtual Box machine (called default) and this machine is used to run docker images. When I use the command line tool (docker-machine.exe) I can see reflected in the VirtualBox GUI that the machine got started. Everything works as intended in this case.
If I start the machine from the VirtualBox the command line tool also works entirely as intended.
If i use VBoxVmService starting the virtual machine does not update anything in the VirtualBox GUI. The command line tool for docker will not work and thinks that the virtual machine has not been started. But the thing is, it has been started. I can see the VirtualBoxHeadless running. If i try to start the machine from the GUI (when already started by the service) the startup fails.

My belief is that the command-line tool asks VirtualBox if the machine is started or not. If VirtualBox replies it is not started it simply gives up. So my question is, is this behaviour by design? Is it meant that when a machine is started using the service it should not be reflected in the GUI? Is there any way to change this behaviour?

My config file is extremely simple:
Code: Select all   Expand viewCollapse view
[Settings]
VBOX_USER_HOME=C:\Users\persm_000\.VirtualBox
RunWebService=no
PauseShutdown=5000

[Vm0]
VmName=default
ShutdownMethod=acpipowerbutton
AutoStart=yes



I am using the latest release VBoxVmService-5.0-Litchi and my VirtualBox is version 5.0.16.

When running my log file is empty from error messages:
Code: Select all   Expand viewCollapse view
04/19/2016, 22:25:56 - C:\vms\VBoxVmService64.exe
04/19/2016, 22:25:56 - C:\vms\VBoxVmService.ini
04/19/2016, 22:25:56 - C:\vms\VBoxVmService.log
04/19/2016, 22:25:56 - VBoxVmService started.
04/19/2016, 22:26:07 - List all the VMs found by VBoxVmService
04/19/2016, 22:26:07 -   VM0: default is powered off.
04/19/2016, 22:26:09 -   VM default has been started up.
04/19/2016, 22:26:23 - Received control command: list
04/19/2016, 22:26:23 - List all the VMs found by VBoxVmService
04/19/2016, 22:26:23 -   VM0: default is running.


So my question boils down to why the VirtualBox GUI doesn't update the machine status.

Best regards,
Per Smitt
iZE
 
Posts: 1
Joined: 19. Apr 2016, 21:58

Re: [VBoxVmService] -> Discussion & Support

Postby Temo » 25. Apr 2016, 23:06

Did you ever get this issue with docker resolved?
Temo
 
Posts: 1
Joined: 25. Apr 2016, 23:04

Re: [VBoxVmService] -> Discussion & Support

Postby FB2000 » 14. Jul 2016, 14:02

VBoxVmService 5.1 - Codename: "Plum" has arrived.

Read the announcement here:

LINK: https://forums.virtualbox.org/viewtopic.php?f=6&t=8595&p=366553#p366553
FB2000
 
Posts: 90
Joined: 10. Sep 2009, 13:27
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: CentOS

Re: [VBoxVmService] -> Discussion & Support

Postby Irdeto2 » 23. Jul 2016, 11:43

I have installed VirtualBox 5.1, VBoxVmService 5.1 and phpvirtualbox 5.0.5. When VM "xp" started as service, I can connect via RDP. But in browser via phpvirtualbox VM status "off".
I think the problem is the old version of phpvirtualbox? In addition, there is a message displayed on the incompatibility of versions, but everything else works fine.
Irdeto2
 
Posts: 10
Joined: 23. Jan 2015, 23:11

Re: [VBoxVmService] -> Discussion & Support

Postby mribichich » 2. Aug 2016, 03:03

Hi there. I been running vboxvmservice along side phpvirtualbox and they show the same vms state. They are both running with the same user.
But when I open vbox gui the state is not shared even though is the same user.

Is there a way to make them share the state?

I know its probably something to do with user permissions, even when I use the same user for everything the service and the gui dont share state.

Anybody knows if there is something to do?

thanks
mribichich
 
Posts: 4
Joined: 1. Aug 2016, 20:26

Re: [VBoxVmService] -> Discussion & Support

Postby seanvree » 15. Apr 2017, 04:48

I have the same question....along with, IS this still the best option to run VV as a windows Service?
seanvree
 
Posts: 15
Joined: 21. Dec 2016, 18:50

Re: [VBoxVmService] -> Discussion & Support

Postby brooksly » 24. Aug 2017, 20:48

I have VirtualBox installed on d:\ I know I need to set the path but I'm not clear on how to do it. The .VirtualBox directory is in the default location in my profile directory. I tried to place the full path to the vm in the VmName= entry in the ini but it still does not locate it. Can someone point out my fatal error?
brooksly
 
Posts: 2
Joined: 24. Aug 2017, 20:20

Re: [VBoxVmService] -> Discussion & Support

Postby scottgus1 » 24. Aug 2017, 21:05

Probably installing Virtualbox on anything but the default location "C:\Program Files\Oracle\Virtualbox". Virtualbox only takes up a couple hundred MB and should always be in the default location, even though you can install it anywhere. Third-party programs working with Virtualbox may not be easily configurable for a non-default install location.

You can uninstall and reinstall Virtualbox into the default location without losing your guests. You can set Virtualbox to make new guests on the D drive - see the main Virtualbox window, File menu, Preferences, General, Default machine Folder. New guests will go there. Existing guests will stay where they are. To move an existing guest see Moving a VM This tutorial is also good re-interpreted as "Backing Up a VM".
running version 5.1.6 & 5.0.24
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
 
Posts: 3455
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: XP SBS2003 Win7

Re: [VBoxVmService] -> Discussion & Support

Postby brooksly » 24. Aug 2017, 21:33

OK, I'll give that a try. Thanks scottgus1
brooksly
 
Posts: 2
Joined: 24. Aug 2017, 20:20

Re: [VBoxVmService] -> Discussion & Support

Postby mholownych » 25. Aug 2017, 18:50

Hello,

Running latest version of VirtualBox and VBoxVmService (5.1). NAT Port forwarding doesn't seem to work. Machine status between VBoxVmService and GUI is not shared.
According the the VBoxVmService.log and VBoxSVC.log (attached) the guest is running and port forwarding has been enabled, though GUI shows powered off and not able to ssh to the guest from the host or other computers(screenshot attached).

VBoxVmService.log
(4.09 KiB) Downloaded 6 times

VBoxSVC.log
(2.59 KiB) Downloaded 4 times

GUI.png
GUI.png (64.8 KiB) Viewed 695 times


[*Update*]

Setting the VBoxVmService Windows Service to run as the my local user, manually killing all processes (through Task Manager) and restarting the service has allowed me to connect via SSH.. though machine status still is not shared with the GUI.
GUI now shows status as aborted.
mholownych
 
Posts: 1
Joined: 25. Aug 2017, 18:31

Re: [VBoxVmService] -> Discussion & Support

Postby fabiomcz » 29. Sep 2017, 20:04

Hello everyone, first of all sorry for my English it was done by the translator.
I am having trouble starting my virtual machine, after migrating my backup to another machine I could not boot, it is resetting all the time it loads the bar completely and it restarts again I am using Win7 and I am without perpectiva of finding the error since it does not me returns no error message, thanks.
fabiomcz
 
Posts: 1
Joined: 29. Sep 2017, 19:56

Re: [VBoxVmService] -> Discussion & Support

Postby socratis » 2. Oct 2017, 02:03

fabiomcz
Are you using the VBodVmService? Is that your problem? Or you have a problem with stand-alone VirtualBox?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12649
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: [VBoxVmService] -> Discussion & Support

Postby jimmypham9461 » 9. Oct 2017, 10:04

Thanks for the install guide. I 'm blind in Virtual Book.
I have been tried to install one on my laptop before, but i dont know how and why go to next step. then I stop.
Now I sure I will keep continue.
jimmypham9461
 
Posts: 2
Joined: 22. Sep 2017, 10:51

Re: [VBoxVmService] -> Discussion & Support

Postby FB2000 » 19. Oct 2017, 15:32

VBoxVmService 5.2 - Codename: "Jujube" has arrived.

Read the announcement here:

LINK: https://forums.virtualbox.org/viewtopic.php?f=6&t=8595&p=404385#p404385
FB2000
 
Posts: 90
Joined: 10. Sep 2009, 13:27
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: CentOS

PreviousNext

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: dbarit, Reno Drums, Wicky, Yahoo [Bot] and 47 guests