borsitsb / virtualboxservice Goto Github PK

What steps will reproduce the problem?
1. Start Vbox in services control
2.
3.

What is the expected output? What do you see instead?
The log has an error, but the vbox starts OK.
-- Log snippet
VirtualBoxService.MachineController Verbose: 20230 : [3/17/2012 11:19:27 PM] 
Remaining time for current operation: 00:00:01
VirtualBoxService.MachineController Warning: 20201 : [3/17/2012 11:19:37 PM] 
Boot on machine "OEL1" timed out.


What version of the product are you using? On what operating system?
virtualboxservice v0.1
Vbox 4.1.10
Windows 7 64bit


Please provide any additional information below.
Best vbox service utility yet, thanx

I am running this on my laptop so it starts slow. I think I just need
to be able to set the start timeout longer.

I have a VM that depends on another, it would be great if there was a delayed 
start option to allow the first VM to start up (from save state) before 
starting the second VM.

What steps will reproduce the problem?
1. Install the service on Windows 7 x64
2. Starting the service shows this error in my application log (eventlog). 
Service cannot be started. System.Security.SecurityException: Requested 
registry access is not allowed.
   at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
   at VBoxWrapper.COMInterface.VBoxComUtils.GetVirtualBoxAppIDKey()
   at VBoxWrapper.COMInterface.ComMachineProxyListBuilder.initVirtualBox()
   at VirtualBoxService.Service.configureVBoxWrapper()
   at VirtualBoxService.Service.startMachineController()
   at VirtualBoxService.Service.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
The Zone of the assembly that failed was:
MyComputer

What version of the product are you using? On what operating system?
latest

What steps will reproduce the problem?
1. Run installer from C:\
2. Click Install
3. Enter windows account credentials & wait... 

What is the expected output? What do you see instead?
Event logs > Application logs > Application error:
Faulting application name: VirtualBoxService.exe, version: 1.0.0.0, time stamp: 
0x4e52a7cb
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 
0x4e2111c0
Exception code: 0xe0434352
Fault offset: 0x0000d36f
Faulting process id: 0x1f84
Faulting application start time: 0x01cdabf36155fcaa
Faulting application path: C:\VirtualBoxService.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a4e09200-17e6-11e2-9407-0018f35eb562

.NET Runtime error:
Application: VirtualBoxService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.AddressAlreadyInUseException
Stack:
   at System.ServiceModel.Channels.TransportManager.Open(System.ServiceModel.Channels.TransportChannelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(System.ServiceModel.Channels.SelectTransportManagersCallback)
   at System.ServiceModel.Channels.TransportChannelListener.OnOpen(System.TimeSpan)
   at System.ServiceModel.Channels.ConnectionOrientedTransportChannelListener.OnOpen(System.TimeSpan)
   at System.ServiceModel.Channels.NamedPipeChannelListener`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnOpen(System.TimeSpan)
   at System.ServiceModel.Channels.CommunicationObject.Open(System.TimeSpan)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(System.TimeSpan)
   at System.ServiceModel.Channels.CommunicationObject.Open(System.TimeSpan)
   at System.ServiceModel.ServiceHostBase.OnOpen(System.TimeSpan)
   at System.ServiceModel.Channels.CommunicationObject.Open(System.TimeSpan)
   at VirtualBoxService.InstallGui.ElevatedServiceHost.RunServer()
   at VirtualBoxService.Program.Main(System.String[])


What version of the product are you using? On what operating system?
VirtualBox service v0.1.  Windows 7 SP1

Please provide any additional information below.
.NET 4 installed

Can support be added for VirtualBox 4.2.x

The Virtualboxservice is unable to auto-start due to logon failure.
Tried manual start of service but "Service could not be started due to log on 
failure" 

virtualboxservice-v0.1 installed in Windows 7 Pro x64 

Please suggest as I suspect Login credentials of FreeNAS server installed over 
FreeBSD in Virtualbox have been changed that is leading to the problem.

thanks in advance. 

Hi Team, just wondering if this has been working with a wireless NIC. I am 
trying to work with my laptop connected to wireless LAN rather than the 
ethernet switch and I get no networking from the VM when it is running from the 
service.  

What steps will reproduce the problem?
1. Configure WiFi 802.11 type NIC to access your network
2. Remove physical ethernet cable
3. Reconfigure VM to use bridged Wireless adapter or NAT
4. Start VM using your service
5. Log on to VM and run IPCONFIG from a window

What is the expected output? What do you see instead?
Expected output would be that the VM has received a valid IP address.  What I 
see is a 169.254.x.x address indicating no network connectivity.



What version of the product are you using? On what operating system?
Version is 0.1
Host Operating system is Windows 7 Home Premium(64 bit)
Guest OS is Windows 7 Professional (32 bit)

Please provide any additional information below.

I have also attempted to configure a second adapter for wireless also but in 
the VM this never shows up as a valid adapter.
This configuration works if I start the VM from the VirtualBox application.

Also I notice that when I restart the Virtual Box application after running the 
VM the networking has sometimes been reset to 'bridged' on the ethernet adapter 
and any configuration for the second adapter is disabled.


Surely I am not the only person to try this so I suspect I am doing something 
wrong in the configuration.  Any ideas?

Many Thanks
LP