search

onlyfang / VBoxVmService

Windows Service to run VirtualBox VMs automatically
328 stars 48 forks source link

Not able to Show/control VMs after upgrading to virtualbox 7 #76

Open nanderer opened 1 year ago

nanderer commented 1 year ago

On my windows server 2019 i upgraded to Virtualbox Version 7.0.8 r156879 together with latest VBoxVmService version (is not shown in the log file unfortunately). I possible should have stayed back with good old version 6 because now i have the problem that i am unable to control the vm/show the vm window of vms startet through VBoxVmService and even with vms started with virtualbox manager.

I worked around the issue by stoping VBoxVmService and VirtualBox system service and then killing all remaining virtualbox processes, starting the virtualbox manager, starting one vm and after it is was running (this time with a window to control it) i started VBoxVmService again. Then i was again able to control even the vms managed by VBoxVmService using the Virtualbox Manager, but that kind of defies the purpose of VBoxVmService to have vms autostart even before signing in.

I hope my description of the issue is understandable otherwise please ask for more info, any idea what causes this behaviour and how to fix it?

Thanks a lot in advance,

nandaerer

JohnnyPicnic commented 1 year ago

Same here. Using 7.06. Also tried 7.08.

iperrealistico commented 1 year ago

I think this needs to be updated

pchenriques commented 9 months ago

Same issue with VirtualBox 7.0.12.

38Cherry commented 8 months ago

same. Tray shows a pause symbol and start option when VM is running. Can not stop the vm unless use CLI command.
Screenshot 2023-12-25 202500

pedrospinto commented 3 months ago

I had the same issue. Turns out I had deleted a VM in virtualbox, but forgot to remove it from the VBoxVmService.ini config file. Once I did so, I got back control over the VMs in the tray icon list.

GCustom commented 2 weeks ago

I had the same issue. Turns out I had deleted a VM in virtualbox, but forgot to remove it from the VBoxVmService.ini config file. Once I did so, I got back control over the VMs in the tray icon list.

This was my problem, I changed out the first entry but left the 2nd from the default file, tons of errors that didn't indicate missing VM but after reading your comment I deleted the extra and the service fired right up.