Custom Query (16363 matches)
Results (2560 - 2562 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15244 | obsolete | VBoxNetAdp6.sys BSOD DRIVER_POWER_STATE_FAILURE Win7 Enterprise SP1 | ||
| Description |
Driver VBoxNetAdp6 causes BSOD DRIVER_POWER_STATE_FAILURE during shutdown of Win7 Enterprise SP1. Normal shutdown after uninstall of Virtual Box. Minidump analysis attached. |
|||
| #15243 | obsolete | VBManage stops working | ||
| 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. |
|||
| #15240 | worksforme | VirtualBox 5.0.16 kernel panic on Linux host (kernel 4.4.5 x86_64) | ||
| Description |
On my Linux host when I try to start any guest with VirtualBox 5.0.16 my host kernel panics immediately. |
|||

