The GUI and the command line vboxmanage report different status of VM

[Hammerhead2006]

I have RHEL 7 and VirtualBox-5.0-5.0.6_103037_el7-1.x86_64.rpm installed.

I found that the GUI and the cli(vboxmanage) are reporting the VM as "powered off" but as you can see from the attachment and the "ps" below it is indeed running. If I "start" the VM from either the GUI or the cli, while the VM is running, it will start another instance of the VM.

#> ps -ef |grep VB
cgreen    3637  3619  2 Oct15 ?        05:16:13 /usr/lib/virtualbox/VBoxHeadless --comment dhcp02-mmr --startvm 6f889019-5659-4587-836e-1044e8f30703 --vrde config

[Hammerhead2006]

picture of GUI showing VM "powered off", when it is NOT.

[Hammerhead2006]

Linux vserver02.prtc.lowcountry.com 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux

VirtualBox Version 5.0.6 r103037

[Frank Mehnert]

Are you sure that the VirtualBox selector and VBoxHeadless run as the same user? Could you add the output of another command?

ps -ef|grep -E "VB|Virt"

Actually your above command seems to indicate that there is also no VBoxSVC process running -- did it crash for some reason? Check if the process is running and if 'dmesg' contains any hint about a crashed process. If VBoxSVC crashes the I would be interested in a VBoxSVC.log file (in ~/.VirtualBox or ~/.config/VirtualBox) together with a VBoxSVC core dump.

[Hammerhead2006]

Here is the output of the ps command.

Also, I installed the newer 5.0.8_103449_el7-1.x86_64.rpm version and it is failing in that version as well. Where does the GUI get its status from. How else can I help?

[cgreen@vserver02 Downloads]$ ps -ef|grep -E "VB|Virt" cgreen 5765 19959 0 10:15 ? 00:00:00 /usr/lib/virtualbox/VirtualBox cgreen 5779 1 0 10:15 ? 00:00:00 /usr/lib/virtualbox/VBoxXPCOMIPCD cgreen 5784 1 0 10:15 ? 00:00:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown cgreen 9813 22494 0 11:46 pts/1 00:00:00 grep --color=auto -E VB|Virt root 25020 2 0 Nov05 ? 00:00:00 [iprt-VBoxWQueue] root 25024 2 0 Nov05 ? 00:00:00 [iprt-VBoxTscThr] cgreen 25861 1 0 Nov05 ? 00:02:05 /usr/lib/virtualbox/VBoxXPCOMIPCD cgreen 25866 1 0 Nov05 ? 00:04:11 /usr/lib/virtualbox/VBoxSVC --auto-shutdown cgreen 25901 25866 2 Nov05 ? 00:19:55 /usr/lib/virtualbox/VirtualBox --comment Actelis --startvm d4575997-a5de-4f7d-9d89-c84ac96f7179 --no-startvm-errormsgbox cgreen 25947 25866 39 Nov05 ? 06:26:47 /usr/lib/virtualbox/VirtualBox --comment Streaming_Server --startvm 8118c79f-05a9-4e31-83dc-10fb090827d2 --no-startvm-errormsgbox cgreen 26264 25866 1 Nov05 ? 00:17:37 /usr/lib/virtualbox/VirtualBox --comment Gestio_IP_Database --startvm ffd3daf9-8cc8-4442-a76f-ccaca4f438c7 --no-startvm-errormsgbox cgreen 26315 25866 3 Nov05 ? 00:30:20 /usr/lib/virtualbox/VirtualBox --comment dhcp02-mmr --startvm 6f889019-5659-4587-836e-1044e8f30703 --no-startvm-errormsgbox cgreen 30050 25866 3 08:09 ? 00:07:02 /usr/lib/virtualbox/VirtualBox --comment NVR01 --startvm f5e7779e-9c83-49d9-8c81-172459b3684d --no-startvm-errormsgbox [cgreen@vserver02 Downloads]$

[Hammerhead2006]

ps command output asked for

[Hammerhead2006]

Diff, VBoxSVC is running as me and it's doing the same thing. Let me know if you need any other logs from this system. I am very anxious to help get this solved.

[Hammerhead2006]

Streaming_Server_Log

[Hammerhead2006]

Streaming_Server_Shovminfo.txt

[Hammerhead2006]

2 instances of the same VM running.

[Frank Mehnert]

Weird. Your host runs two instances of VBoxSVC and VBoxXPCOMIPCD. Are you running some kind of containers on the host? Also, could you do attach the output of

netstat -lp | grep vbox

And are you able to start several instances of VBoxSVC from the terminal? That is, open a terminal and start VBoxSVC. Then, as the same user, open another terminal and try to start another instance of VBoxSVC. It should fail like this:

VBoxSVC: error: Failed to register the server name "VBoxSVC-5.0.8" (rc=NS_ERROR_FAILURE)!
VBoxSVC: error: Is another server already running?
XPCOM server has shutdown.

If it does NOT fail like this, then we need to debug this behavior.