Custom Query (16363 matches)
Results (2374 - 2376 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4373 | fixed | Opaque (i.e. unusable display) when using VB 3.0.0 r49315 on X11 radeonhd | ||
| Description |
When trying to use VB 3.0.0 r49315 on my (K)unbuntu 9.04 (jaunty) x86_64 (aka amd64) system, I hardly see anything because most of the guest OS (e.g. Windows XP) is opaque. Net result is that VB is unsuable with radeonhd X11 driver (with enabled DRI, 3d support, accelerated). In contrast, if I'm using the radeon X11 driver (without DRI (?), no 3d support, but accelerated), the display looks all right. In this case, it is no problem to use the VB guest OS. I trying to add some screenshots of this... |
|||
| #4376 | fixed | Vbox 3.0.0: Keyboard is so sensitive that I can't login into guest => Please try 3.0.2 | ||
| Description |
Hi, after upgrading vbox 2.2.4 to vbox 3.0.0 keyboard become so sensitive that I can't login into Ubuntu guest anymore. For example if I type admin as userid I get something like: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaddddddddddddddddddddmmmmmmmmmmmmmmmmmmmiiiiiiiiiinnnnnnnnnnnn It looks all keys in keyboard are very sensitive, because <backspace> also deletes multiple characters. Host (Windows XP) keyboard sensitivity is working OK. Keyboard sensitivity was also working OK on host and guset in vbox 2.2.4. So this is new bug in 3.0.0. Host: Windows XP SP3 Guest: Ubuntu 9.04 desktop 32-bit VM: VitualBox 3.0.0 Regards |
|||
| #4377 | fixed | guest hangs on IO operations | ||
| Description |
I cannot reproduce the problem but it seems to be related to IO, most probably network. At some point after a few hours of working the guest hangs almost completely. It still answers to ping for example and if I have a console opened I can still type a few commands. But once something requires some IO, it hangs. For example, direct login on tty accepts u/p then says: "Login timed out after 60 seconds". I managed only to see the list of processes in D (hundreds of them) and for example strace on an httpd instance shows it blocked in accept(... There is nothing in dmesg on either the guest or the host. VBox.log is also clean. This exact configuration worked fine until ver 3.0.0, so it looks like a bug in the latest version. Apparently it doesn't depend on any hardware virtualization features since it showed even in 2 CPUs with all the options enabled and 1 CPU with none of the options. I'll try downgrading to 2.2.4 to see if it solves the problems, but it might take a while until I can be sure of the outcome. |
|||

