[VBoxVmService] -> Discussion & Support

Discussions related to using VirtualBox on Windows hosts.

Re: [VBoxVmService] -> Discussion & Support

Postby macbean » 5. Nov 2017, 18:02

Host OS: Windows 10
Virtualbox version: 5.2

using jujube for 5.2

Everything works exactly as described however I have one issue.

within my linux guest (ubuntu 16.04) with guest additions and extension pack installed I have three mapped drives using vboxsf. When I manually start the system, these drives mount fine. When I start it using vboxvmservice, they do not mount automatically, nor do they mount manually. I think the error is 'protocol error' but realistically, i'm fairly certain it is because the guest os does not see shared drives via vboxsf when started using vboxvmservice. The error I receive is the same one I saw when trying to mount the drives when I hadn't actually shared them via the gui.

is there some extra step involved when using vboxvmservice AND drives mapped through vboxsf?
macbean
 
Posts: 1
Joined: 5. Nov 2017, 17:56

Re: [VBoxVmService] -> Discussion & Support

Postby Fabian07 » 18. Dec 2017, 12:23

Hi,

I have a VB running on a Win Server 2008 Server as a service with VBoxVmService.
This was working already working. But now (I don't really know when it changed) it has a network problem.

If I start the VB manually all works as expected.

But started as a service I have limited network functions only:
- I can ping the VB from its 2008 host
- I can ping the host from the VB
- I can als connect to the VB via RDP and SSH from its host

But I'm not able:
- to ping or connect VB from another PC within same network
- to ping gateway or any other IP within same network from the VB

Sounds like a firewall problem, therfore I switched off Windows Firewall completly, but with no success.
And there's no other firewall on this server.
And there are other services on this server which work normally.

I don't really know what changed and I have neither an idea what can force this behaviour nor do I have an idea how to find a solution.

Any ideas?

Regards
Fabian
Fabian07
 
Posts: 2
Joined: 18. Dec 2017, 12:09

Re: [VBoxVmService] -> Discussion & Support

Postby Fabian07 » 18. Dec 2017, 15:25

FYI: after uninstalling Windows Update KB4034664 VB service works again as before.

Regards
Fabian
Last edited by socratis on 18. Dec 2017, 15:28, edited 1 time in total.
Reason: Added missing URL.
Fabian07
 
Posts: 2
Joined: 18. Dec 2017, 12:09

Re: [VBoxVmService] -> Discussion & Support

Postby timblaktu » 16. Jan 2018, 01:48

Bump. I'd like to see an answer to this, as I'm setting up linux guest to auto run using VBoxVmService and I also use vboxsf mounts normally and want to know if I can expect these to work, or if I'll need to use some other method.

macbean wrote:Host OS: Windows 10
Virtualbox version: 5.2

using jujube for 5.2

Everything works exactly as described however I have one issue.

within my linux guest (ubuntu 16.04) with guest additions and extension pack installed I have three mapped drives using vboxsf. When I manually start the system, these drives mount fine. When I start it using vboxvmservice, they do not mount automatically, nor do they mount manually. I think the error is 'protocol error' but realistically, i'm fairly certain it is because the guest os does not see shared drives via vboxsf when started using vboxvmservice. The error I receive is the same one I saw when trying to mount the drives when I hadn't actually shared them via the gui.

is there some extra step involved when using vboxvmservice AND drives mapped through vboxsf?
timblaktu
 
Posts: 9
Joined: 5. Mar 2010, 20:59
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Debian Stretch

Re: [VBoxVmService] -> Discussion & Support

Postby timblaktu » 16. Jan 2018, 02:56

More information: in my case, I am successfully AutoStart-ing a Debian Stretch guest on a Windows 10 host using VBox 5.2 and VBoxVmService 5.2. I have 5 vboxsf mounts set up for that machine, and the AutoStarted guest appears to have successfully mounted all of them:

Code: Select all   Expand viewCollapse view
tblack@tblack-stretch:~$ sudo mount | grep vboxsf
C_Users_tblack on /media/sf_C_Users_tblack type vboxsf (rw,nodev,relatime)
E on /media/sf_E type vboxsf (rw,nodev,relatime)
Engineering on /media/sf_Engineering type vboxsf (rw,nodev,relatime)
LST on /media/sf_LST type vboxsf (rw,nodev,relatime)
Purgatory on /media/sf_Purgatory type vboxsf (rw,nodev,relatime)


I can read/write from the mounts that are local on the host machine, however I encounter "Operation not permitted" when I try to read from _SOME OF_ the mounts that are network shares. In this case: Engineering, LST, and Purgatory are all Windows shares that I've specified in the VM settings. Purgatory I can read/write to, but Engineering and LST I cannot even read from.

I don't (yet) see the difference in the perms on these shares that could cause this, and am suspecting this is caused by VBoxVmService running my VM as LOCAL SYSTEM user as stated on the wiki. https://sourceforge.net/p/vboxvmservice/wiki/Home/ The wiki also states that "If for some reason, you need to run it with other account, you can change the user it run as at Computer Management Console.", however, I have no idea what the Computer Management Console is. Can someone please enlighten me?
timblaktu
 
Posts: 9
Joined: 5. Mar 2010, 20:59
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Debian Stretch

Re: [VBoxVmService] -> Discussion & Support

Postby timblaktu » 16. Jan 2018, 03:32

timblaktu wrote:I don't (yet) see the difference in the perms on these shares that could cause this, and am suspecting this is caused by VBoxVmService running my VM as LOCAL SYSTEM user as stated on the wiki. https://sourceforge.net/p/vboxvmservice/wiki/Home/ The wiki also states that "If for some reason, you need to run it with other account, you can change the user it run as at Computer Management Console.", however, I have no idea what the Computer Management Console is. Can someone please enlighten me?


I think this is referring to the "Computer Management" built-in Windows program. There I can see VBoxVmService under "Services", and its "Properties" have the option in the "Log On" tab to use the current user account instead of "Local System account".

I just tried this to see if my shares start working better.. it only allowed me to enter my username whne I prefixed it with "<my-domain>\" but after that it gave me a dialog that said "The account <my-domain>\tblack has been granted the Log On As A Service right."

I then restarted the service and when I ssh'd into the AutoStarted guest, can verify that ALL shares are now working, just like I had manually started the Vm.
timblaktu
 
Posts: 9
Joined: 5. Mar 2010, 20:59
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Debian Stretch

Previous

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 55 guests