Custom Query (16363 matches)
Results (2017 - 2019 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11993 | fixed | VirtualBox 4.2.16 with Multi-CPU Guest does not use multiple host CPU. | ||
| Description |
I'm using VirtualBox 4.2.16 on Fedora 19 (kernel 3.9.9-302.fc19.x86_64) with a 64 bit Windows 7 2xCPU guest. On Fedora 17 with 4.2.16 this configuration works successfully, but on Fedora 19, only a single CPU is loaded even though a dual CPU guest is specified. The issue looks similar to an old issue, here: https://www.virtualbox.org/ticket/6936 If I revert to a single CPU (1xCPU, capped @95%) VirtualBox 4.2.16 works as expected. However, with a dual-CPU specification (2xCPU, capped 75%), a single CPU occupies 100% utilisation and the guest machine is noticeably slower than when configured with a single CPU. The host reports no problems in any logs. |
|||
| #13485 | obsolete | Software update kills host | ||
| Description |
When connected to a network that requires Web login e.g. a Wireless Network hosted with Forefront security, if not logged in then VirtualBox hangs and crasches within 10 seconds. Virtualbox probably thinks it got the update info response from the network but instead it got the Web login page... |
|||
| #16395 | invalid | VirtualBoxVM caused panic on OS X | ||
| Description |
VirtualBoxVM crashed my OS X. I do not know what was that because I was not watching it. The crash report should explain it. |
|||

