Opened 9 years ago
Closed 5 years ago
#15243 closed defect (obsolete)
VBManage stops working
| Reported by: | Jordi | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 5.0.16 |
| Keywords: | headless VBoxManage | Cc: | garsax@… |
| Guest type: | all | Host type: | Linux |
Description
Ok, I don't know how to describre this so I'll try my best here.
First, the host it's an Ubuntu Server 14.04.4 LTS (trusty), kernel version is now 3.13.0-49 (but this happens on any other version too). The VirtualBox version is now 5.0.14 (again, this happens on any other 5.x or 4.3.x version too).
When I start the server machine I launch several virtual guests (most of them are Windows but 2 of them are Linux). All of them are headless. All Windows guests are accessed using VRDP only. Linux guests are accessed using ssh.
Everything is fine for several hours but, usually the day after, I'm unable to use VBoxManage at all. The already started guests are working perectly fine but I can't launch any other guests, I can't clone disks, I can't even list vms:
jordi@sol:~$ VBoxManage list vms VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available) VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
As said, at the very same time there are at least 20 guests working ok (I can reboot them but if I dare to shut them off I won't be able to start them again...)
I noticed that VirtualBox temp dir is empty:
jordi@sol:~$ ls -l /tmp/.vbox-jordi-ipc/ total 0
This is what top shows (extract):
5776 jordi 20 0 2789904 1.085g 1.044g S 98.2 3.5 1267:04 VBoxHeadless 5914 jordi 20 0 2724236 1.097g 1.044g S 83.6 3.5 304:50.73 VBoxHeadless 5605 jordi 20 0 2721160 1.097g 1.044g S 11.7 3.5 90:44.65 VBoxHeadless 6378 jordi 20 0 2721160 1.092g 1.044g S 6.7 3.5 94:44.73 VBoxHeadless 6426 jordi 20 0 2724236 1.082g 1.044g S 2.7 3.5 177:01.78 VBoxHeadless 4094 jordi 19 0 3784004 2.044g 2.007g S 2.0 6.5 206:35.12 VBoxHeadless 3979 jordi 20 0 1110960 16560 5448 S 1.7 0.1 35:33.19 VBoxSVC 7797 jordi 20 0 2721160 1.084g 1.044g S 1.7 3.5 89:18.60 VBoxHeadless 3925 jordi 20 0 1193320 14144 6148 S 1.3 0.0 4:09.97 vboxwebsrv 3927 jordi 20 0 127704 5680 3384 S 1.0 0.0 18:13.86 VBoxXPCOMIPCD 5222 jordi 20 0 2721160 1.097g 1.044g S 1.0 3.5 78:55.10 VBoxHeadless 5483 jordi 20 0 2786828 1.086g 1.044g S 1.0 3.5 86:01.28 VBoxHeadless 7833 jordi 20 0 2724236 1.091g 1.044g S 1.0 3.5 81:33.54 VBoxHeadless 7872 jordi 20 0 2724236 1.098g 1.044g S 1.0 3.5 199:19.86 VBoxHeadless 7914 jordi 20 0 2724236 405228 374072 S 1.0 1.2 79:37.66 VBoxHeadless 8015 jordi 20 0 3321092 1.723g 1.679g S 1.0 5.5 76:13.41 VBoxHeadless 8052 jordi 20 0 2721160 1.079g 1.044g S 1.0 3.4 77:41.11 VBoxHeadless 8121 jordi 20 0 2728332 1.094g 1.048g S 1.0 3.5 71:13.51 VBoxHeadless
So far, the only workaround I found it's to reboot the host machine but this is not an option when in production....
Any help would be much appreciated.
Change History (5)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Looks to me like something on your system is wiping important things from /tmp, sabotaging VirtualBox. Not default behavior of the typical distributions.
comment:3 by , 9 years ago
The interesting information would be the output of
lsof|grep "\/tmp\/\.vbox"
when this happens. Looks to me like VBoxSVC or VBoxXPCOM crashes. In that case there should be also core dumps generated.
comment:4 by , 9 years ago
You got it:
root@sol:/home/jordi# lsof|grep "\/tmp\/\.vbox" VBoxXPCOM 4228 jordi 3wW REG 8,3 5 4325393 /tmp/.vbox-jordi-ipc/lock (deleted) VBoxXPCOM 4228 jordi 4u unix 0xffff8807ee84b480 0t0 15074 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 5u unix 0xffff8807f25f7a80 0t0 15075 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 6u unix 0xffff8807ee84bb80 0t0 9057 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 7u unix 0xffff8807ee653b80 0t0 24732 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 8u unix 0xffff8807ee84a680 0t0 9069 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 9u unix 0xffff8807ee991180 0t0 26672 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 10u unix 0xffff880688e2e200 0t0 52496 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 11u unix 0xffff8807eef9e900 0t0 47753 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 12u unix 0xffff880688e2ad80 0t0 52646 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 13u unix 0xffff8807eeffb480 0t0 52793 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 14u unix 0xffff8807eef9d080 0t0 46850 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 15u unix 0xffff8807ee94db00 0t0 53976 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 16u unix 0xffff8807ee94f380 0t0 54044 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 17u unix 0xffff8807eeff8380 0t0 54122 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 18u unix 0xffff8807eeffbf00 0t0 63219 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 19u unix 0xffff8807ee94f700 0t0 63397 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 20u unix 0xffff8807ee94a680 0t0 68162 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 21u unix 0xffff8807f25f6c80 0t0 68786 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 22u unix 0xffff88064de18000 0t0 66420 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 23u unix 0xffff8807ee94c980 0t0 72877 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 24u unix 0xffff8807ee84ad80 0t0 74757 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 25u unix 0xffff880688d95400 0t0 72196 /tmp/.vbox-jordi-ipc/ipcd VBoxXPCOM 4228 jordi 26u unix 0xffff8807ee94aa00 0t0 74214 /tmp/.vbox-jordi-ipc/ipcd
comment:5 by , 5 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Tested with VirtualBox version 5.0.16 and got the same issue.