Custom Query (16363 matches)
Results (2266 - 2268 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4122 | fixed | Networking doesn't work at all on Windows 7 RC1 x64 Host. | ||
| Description |
The Internal Networking doesn't work at all. NAT doesn't work at all. Bridging doesn't work at all. Also, the "VirtualBox Bridged Networking Driver" causes the system to lose network conectivity completely. The adapter(s) that have that driver enabled are reported in Win7 just as being "Enabled". There's no DHCP request and no activity at all. (See Screenshot1). Disabling the "VirtualBox Bridged Networking Driver" makes the networking on the host system work again. |
|||
| #4123 | fixed | high CPU usage on Ubuntu | ||
| Description |
After upgrade VirtualBox from 2.1.2 to 2.2.2 on Ubuntu 8.10 and install MS Windows as guest i found that guest OS takes 10% of CPU usage in 'top'.May be this is normal but i see that host OS works very slow now and i can't start any other programs.In this moment guest OS works good and fast.On 2.1.2 all was fine. |
|||
| #4124 | fixed | VBoxManage controlvm $uuid savestate hangs due to 2D enabled => Fixed in SVN | ||
| Description |
When I try to save my VM's state, the VBoxManage command simply hangs: $ VBoxManage controlvm 4a908f7b-53d3-420f-9c6a-066d62c118f8 savestate VirtualBox Command Line Management Interface Version 2.2.2 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. And that's it. There I sit, presumably forever, waiting for it to take effect. It never does. This is pretty reproducable. It simply happens after the guest's console has been battered with output from the (guest of course) Linux kernel. |
|||

