Custom Query (16363 matches)
Results (235 - 237 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2732 | obsolete | keyboard locks caps in windows vista host | ||
| Description |
when running a solaris or linux guest on a Windows Vista host, sometimes (not always) the keyboard in the *host* OS is locked to capitals (as if caps-lock was pressed). Pressing SHIFT or CAPS-LOCK key toggles the keyboard, so that now keyboard in the guest OS behaves exactly the opposite than in host os. |
|||
| #2752 | obsolete | serial port in linux guest gives "serial8250: too much work for irq4" | ||
| Description |
With kernel 2.6.27.6 and a serial port enabled the following error message is given many times on the kernel log: serial8250: too much work for irq4 A similar discussion related to qemu is here: http://kerneltrap.org/mailarchive/linux-kernel/2008/2/5/735714 The port works without problems. |
|||
| #2754 | obsolete | Windows XP Host Crash on connecting USB HDD in VBOX | ||
| Description |
I am experiencing same problem as that notified in ticket 1654. USB ports are enabled and USB flash drives connect fine. It is when connecting an external USB hard drive is when the host system reboots. Note that the USB HDD is visible and usable in the host environment. The USB HDD details are: Name: In-Systems Design USB Storage Adapter Vendor: 05AB Product ID: 0060 Revision: 1110 Manufacturer: In-Systems Design Product: USB Storage Adapter Serial: 2BFFU118031FA7BB Port: Remote: No The USB HDD does not require any special drivers for Windows XP. I have tried using another driver but this does not cure the problem. As the host crashed, on reboot Windows comes up with the request window to notify Microsodt of the problem. I did this and received the following message back: "You received this message because a hardware device, its driver, or related software has caused a blue screen error. This type of error means the computer has shut down abruptly to protect itself from potential data corruption or loss. In this case, we were unable to detect the specific device or driver that caused the problem." As ticket 1654 has been outstanding for some months now, any immediate help would be appreciated. Thanks. |
|||

