Custom Query (16363 matches)
Results (763 - 765 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #638 | duplicate | IO APIC eat 100% (32 bits guests) -> duplicate of 4392 | ||
| Description |
Fedora 7 host, Macbook Pro. If i enable option IO APIC VirtualBox eat all CPU, independ my windows guest work or in idle state. |
|||
| #639 | invalid | OpenBSD guests... still not quite usable (VT-x/AMD-V works) | ||
| Description |
I'm having annoying problems with an OpenBSD 4.1 guest on Ubuntu Feisty AMD64 host. The install went fine, unlike with previous version, but when using the installed quest, I'm having regular segmentation fault while using various programs inside that OS. On a regular computer, I would immediately suspect an hardware problem. The crashes are occasional and random, and I can't reproduce them with regularity. The only way I can get a reliable crash is by extracting OpenBSD sources from CVS. I will attach the last few lines of a ktrace dump, done by calling cvs. I'm not BSD expert. I've installed this guest to learn about OpenBSD, but I believe those crash make VBox unfit for that OS as a guest, and that is why I honnestly believe this is a major bug. |
|||
| #640 | fixed | USB connect fails after initial VBoxUSB install (windows host) | ||
| Description |
On the Windows version of VirtualBox, when I try to connect a USB device, a "Found New Hardware" message appears. After I install "VirtualBox USB", the USB still doesn't work. |
|||

