Custom Query (16363 matches)
Results (2359 - 2361 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4345 | fixed | Invalid hostkey results in startup-crash (bus error) => Fixed in SVN/3.1.6 | ||
| Description |
If I change the HostKey parameter in VirtualBox.xml to an (appearantly) invalid number, I get a "bus error" when starting the GUI. mcie:VirtualBox tebokkel$ grep HostKey VirtualBox.xml
<ExtraDataItem name="GUI/Input/HostKey" value="126"/>
mcie:VirtualBox tebokkel$ /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
Bus error
While on the topic, please also see #979, which caused me to go look for other options. |
|||
| #4346 | fixed | Debian kernel panics | ||
| Description |
I'm getting kernel panics with the 2.6.26-2-686 kernel on Debian Sid. Windows XP Pro SP 3 as the host, Debian unstable as the guest. Attached is the VBox.log of a successful startup and unsuccessful startup. The kernel panics seems completely sporadic. After stopping and starting the Debian guest, it might panic again, might not. This past time, it took several attempts before it started booting. Guest additions are installed. This has affected version 3 as well as the past 2 versions of VirtualBox. |
|||
| #4348 | fixed | unable to start Windows 2000 installation with IO-APIC enabled -> fixed in SVN/3.0.2 | ||
| Description |
I tried to install Windows 2k and it fails after loading all drivers and before you can select the drive/partition. It shows something like "starting Windows 2000" and dies with 100% CPU-load on one emulated core. The problem can be tracked back to IO-APIC support, which is needed for SMP support. Setting it to 1 CPU and deactivating V-tx but leaving IO-APIC on doesn't solve the problem. Host: Windows Vista x64 SP2, Intel Xeon X3220 (Quad-Core), 8GB RAM Guest: Windows 2k (Installer) with integrated SP4 |
|||

