Custom Query (16363 matches)
Results (2491 - 2493 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8508 | fixed | Guest Additions 4.0.4 cause BSOD - IRQL_NOT_LESS_OR_EQUAL | ||
| Description |
Upgraded virtual box from 3.2.8 to 4.0.4. No problems. Then upgraded the guest additions to 4.0.4. Guest now gives BSOD - IRQL_NOT_LESS_OR_EQUAL - Stop 0A. Disabling the VT-x/AMD-V allows to boot into Windows, but causes a different stop when shutting down. Host: Windows 7 64bit Home Premium Guest: Windows XP SP 3 All drivers etc are up to date. No problems with 4.0.4 or guest additions with Ubuntu or Ubuntu Server64 |
|||
| #5048 | worksforme | Host freeze if intel VT is enabled | ||
| Description |
Host: Gigabyte GA-G33M-DS2R, 4 GB Corsair RAM, Ubuntu 9.04 i386 Kernel 2.6.28-15-generic and 2.6.31-10 (same problem), VirtualBox 3.0.6 Guest: Windows XP Professional SP3 up-to-date After a suspension to RAM (S3 state), only if VT-x is enabled in Processor Options, the Host immediately freeze when the Guest is started. In the case the virtual machine is running before get suspension, the Host won't resume, requiring an hard reset. |
|||
| #14563 | fixed | Symbolic links with `..` result in `protocol error` on vboxsf + 5.0.4 | ||
| Description |
When creating a symlink that contains cd /vagrant ; mkdir test ; cd test ; ln -s ../Vagrantfile . ln: failed to create symbolic link `./Vagrantfile': Protocol error
This also happens when linking It may be related to the following: Note: if the symlink is made on the host FS (and not created on the VM), it seems to behave normally/correctly. Host for our tests is Mac OS X 10.10, guest is Debian Jessie. |
|||

