Custom Query (16363 matches)
Results (1504 - 1506 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1712 | obsolete | just launching vbox 1.62 causes host's wireless network to disconnect (USB nic conflict) | ||
| Description |
host: win xp sp3 using a belkin usb2 wifi dongle. as soon as i launch vbox 1.62, the wireless disconnects and i am unable to restore connection until i close out of vbox. after i close out of vbox, i am able to "repair" the connection (just resetting basically). but while vbox is running (without a single guest vm running), no internet. |
|||
| #10540 | duplicate | just another guru meditation | ||
| Description |
(I hope it's correct to file a new bug report for each guru meditation, unless there's a specific action or sequence of steps to trigger it which is not my case). This time it happened the next time I tried to boot the VM after a force close (i.e. after closing it without shutting down the guest OS). Needless to say this shouldn't cause a guru meditation. |
|||
| #10164 | wontfix | jumping to the BIOS power-on reset vector causes a CPU loop instead of a reboot | ||
| Description |
Apparently it should be possible to reboot a PC by jumping to the BIOS "power on restart" vector. I.e. "ljmp $0xf000, $0xfff0", with the CPU in real mode, perhaps after clearing the warm-boot flag in 0040h:0072h. This works fine on real PCs, including recent HP laptops, etc. However with VirtualBox since at least 4.0.4, and up to and including 4.1.8, this just puts the VM into an endless loop chewing CPU cycles. |
|||

