Custom Query (16363 matches)
Results (103 - 105 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12912 | obsolete | VBoxSVC locks with more than 63 VM`s running on the same host | ||
| Description |
Hi, I´ve being experiencing problems with VBoxSVC when more than 63 VM´s running ( the issue begins when the 64th VM is started) , it locks with 13 to 15 % of system resource utilization, and if I try to stop or save one VM, it keeps locking the files preventing to change configurations/restarting the VM. The only way to unlock the files is to stop all VM´s and reboot the Host (killing VBoxSVC after all VM´s down just messes up everything ). I use this environment to test our multiuser application , and I need an environment with 70-80 VM´s running (heterogeneous , with Windows XP, 2003 and 7 as guests ), memory is not an issue, as with all VM´s running I still have 15Gb free on the host. The host is a Core i7 4870K , with 64Gb of memory running Windows 2012R2 Enterprise. The vhd/vdi files are stored in a RAID 5 array . If , for example, a new VM is created after the issue is triggered, and a new VM is created , after attaching the VHD, the VBox Manager frozen, i´ve killed it and opened a new one, when i tried to change the VM settings, i got this message > Failed to open a session for the virtual machine Microsoft2. The machine 'Microsoft2' is already locked for a session (or being unlocked). Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} In this case, I´ve saved all running VM´s, but all VirtualBox.exe still running ( but no program shows on the task manager ), i´ve attached both print screen. The only solution i found so far, is to reboot the host, after saving all running VM´s when the host is rebooted, a Vbox Error popup showed up many times ( it seems one per "lost" running VirtualBox.exe process ) , attached the print screen. No core dumps were generated. This issue happens since version 4.0 ( i´ve tested all up to 4.3.11 ) Let me know which steps/information is needed in order to pinpoint the root cause and help you fixing this issue. |
|||
| #2143 | duplicate | Creating OS/2 Warp 3 guest crashes VirtualBox 2.0 on OS X Leopard | ||
| Description |
When I launched VirtualBox 2.0 on Mac OS X Leopard (Intel, Mac Mini Core Duo 1.66 GHz with 2 GB RAM) it works fine for the most part. I have an MS-DOS 6.22 (with Windows for Workgroups 3.11) guest which works fine and a Windows XP Pro with Service Pack 3 guest which works fine as well. However, when I go to create an OS/2 Warp 3 guest, it crashes when I go to make the virtual hard disk drive. I go with the new, dynamically expanding one using the default values for RAM and disk space. As soon as I hit the next button, VirtualBox quits. No errors shown, etc. it just quits. I have more than sufficient disk space free on the host. I tried to get a Core Dump but this is all I got: anthonys-mac-mini:Applications anthony$ ls V* VirtualBox.app: Contents anthonys-mac-mini:Applications anthony$ ulimit -c unlimited anthonys-mac-mini:Applications anthony$ VirtualBox VirtualBox(361,0xa0271fa0) malloc: * mmap(size=2147487744) failed (error code=12) * error: can't allocate region * set a breakpoint in malloc_error_break to debug Bus error anthonys-mac-mini:Applications anthony$ |
|||
| #6348 | fixed | linux host hangs when using shared folders | ||
| Description |
Frequently, when using a machine shared folder in the windows guest, the Linux host hangs completely, with no info the linux system logs. |
|||

