Custom Query (16363 matches)
Results (16 - 18 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15914 | fixed | Windows 10 BSOD while system idle 100% CPU on restart with 5.1.5 | ||
| Description |
Upgraded to 5.1.5-110527 to resolve ticket 15677. Several BSODs (Blue screen with sad face) since upgrade. Most recent BSOD occurred overnight when system was idle. Have not previously had any BSODs. Nothing in Windows event log. On first reset after BSOD Windows hangs with 100% CPU. Successful startup on second reset. |
|||
| #15998 | fixed | segfault at 18 in libc-2.19.so with VB 5.1.6 | ||
| Description |
Guest and all VBox controls totally unresponsive. Had to kill VBoxSVC from another session to regain control. CPU was NOT at 100% as in previous freezes. Sep 26 16:44:20 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech Sep 27 10:00:40 Gull2 kernel: EMT-0[1624]: segfault at 18 ip 00007f94cfcd3b48 sp 00007f949e15a6e0 error 4 in libc-2.19.so[7f94cfc5b000+19e000] Sep 27 10:00:40 Gull2 kernel: device Net1 left promiscuous mode Sep 27 10:00:40 Gull2 kernel: vboxnetflt: 0 out of 15388517 packets were not sent (directed to host) Sep 27 10:01:06 Gull2 kernel: vboxdrv: ffffffffa14a1020 VMMR0.r0 Sep 27 10:01:06 Gull2 kernel: vboxdrv: ffffffffa15a0020 VBoxDDR0.r0 Sep 27 10:01:06 Gull2 kernel: VBoxNetFlt: attached to 'Net1' / ec:b1:d7:37:82:1c Sep 27 10:01:07 Gull2 kernel: vboxdrv: ffffffffa001e020 VBoxEhciR0.r0 Sep 27 10:01:07 Gull2 kernel: device Net1 entered promiscuous mode Sep 27 15:37:56 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech Sep 27 15:44:30 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech A VBox.Log is attached. However, this is from after the restart. It looks like the log from the fault was overwritten. |
|||
| #16047 | duplicate | Error deleting a snapshot -> duplicate of #15831 | ||
| Description |
Linux host with windows guest and three .vdi disks. If I try to delete the snapshot the process starts, but after merging the first image the progress window closes but the screen still shows the snapshot as existing. However, the first snapshot physical file has been deleted from the disk, but not removed from the .vbox configuration file. The other two .vdi files are untouched. I can no longer start the VM. This has happened on multiple different VMs. |
|||

