Custom Query (16363 matches)
Results (1204 - 1206 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1231 | fixed | evdev scancode support for VBoxSDL (USB keyboards) (patch supplied) | ||
| Description |
evdev is a common Xorg input driver for USB devices (in this case, keyboards). VBoxSDL is hard-coded for X11 scancodes. This patch provides support for evdev scancodes via a command line switch (-evdevkeymap) |
|||
| #1232 | fixed | NAT don't work | ||
| Description |
After upgrade to VirtualBox 1.5.6 my guests don't have networking using NAT. My host is Kubuntu 7.10 and my guest are Windows 2003, Windows XP and SuseLinux 10.3. I tried the proposed solution in other trouble ticket: downloading the last binaries, however I still have the error. This is a serious problem because the guests don't have Internet Access and cannot download updates. |
|||
| #1233 | duplicate | Virtual Box Eats up CPU when guest idle | ||
| Description |
Host: Ubuntu X86_64 'Gutsy Gibbon' 7.10 running Virtualbox 1.5.6 Supports AMD-V. 64bit processor Dual core CPU, 8Gb Ram, 4Tb HDD Guest: Windows 2003 Server Standard Running with 512Mb of Memory When the guest is idling, the host shows a contant 15-25% CPU usage on one core. This happens if I run it headless using VRDP or when I run it under the GUI. I have tried enabling and disabling AMD-V and it makes no difference. Actually I can't really tell a difference in speed between these two modes. Without it enabled, it seems to boot faster which supports the claim in the FAQ that Virtualbox's own 'tricks' are less expensive than hardware virtualization. I have disabled clipboard sharing as well. Guest Additions have been installed. I even dropped host to 4Gb of ram (I've had machines where if you put more than 4Gb, even though they say they support it AND I run a 64bit os, weird things happen like the raid controller stopping or the network card not working!). This means if I run 4 guests, both cores use up huge amounts of cpu for idle guests. This particular image is one I converted from a qcow2 image which I ran under KVM. If I run it (I sitll have the original image) under kvm, the host cpu is about 1-2% during guest idle (and in fact it drops off top completely so probably even less). Let me know if theres anything else I can provide. I've chosen priority of Major because it limits the amount of guests that one can run. I actually ran 13 guests with KVM and I don't think I'm going to be able to achieve that with Virtualbox. Brendan Grieve |
|||

