Custom Query (16363 matches)
Results (2176 - 2178 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15887 | fixed | VBox 5.1.4 Segmentation fault on debian 8.0 | ||
| Description |
Windows 10 guest is suddenly crashed on VBox 5.1.4 with Debian 8.0 At that time,it is never logged anything as normal on Virtual Box log. But when guest is crashed,syslog is always logged below message. Sep 5 19:20:06 svyomo2 kernel: [809769.955405] EMT-3[27279]: segfault at 10 ip 00007f6b8b60d43a sp 00007f6ba3cfbbd0 error 4 in VBoxDD.so[7f6b8b4f9000+289000] Sep 5 19:20:06 svyomo2 kernel: [809770.088679] device eth0 left promiscuous mode Sep 5 19:20:06 svyomo2 kernel: [809770.116004] vboxnetflt: 0 out of 248332 packets were not sent (directed to host) |
|||
| #15886 | obsolete | Debian Jessie hangs on boot with VB 5.1.x | ||
| Description |
Since I upgraded to VB 5.1, my Debian Jessie hangs on boot with a SATA error. If I downgrade to VB 5.0.26, this guest machine works well. |
|||
| #15884 | worksforme | Attaching a BIOS file to a VM does not work in VirtualBox 5.1.4 | ||
| Description |
In VirtualBox 5.0.x it is possible to use the command This feature is broken in VirtualBox 5.1.4. When the command is applied, the VM hangs during startup and does not boot the guest OS. (The same VM does boot the guest OS when no BIOS file is attached to it.) The problem seems to be independent from the BIOS file, since it occurs even if the file bios.bin is an unaltered copy of VirtualBox 5.1.4's own BIOS (as it can be extracted from VBoxDD2.dll). |
|||

