Custom Query (16363 matches)
Results (1963 - 1965 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16393 | duplicate | Windows 10 15007: Guest additions cause BSOD/GSOD | ||
| Description |
The guest additions (5.1.12 & 5.1.13) cause a freeze after starting Windows 10 15003/15007 (Insider Preview) as a guest and a BSOD/GSOD shows up after a few seconds. After removing the guest additions via safe mode, everthing works 'fine' again. |
|||
| #16391 | invalid | Installation MSI files are still signed with SHA1 and not SHA256 | ||
| Description |
The MSI files for vbox 4.3.40 & 5.1 (only checked these) are only signed with SHA1 where as files such as common.cab is signed also with SHA256 for example: VirtualBox-5.1.0-108711-Win.exe --extract look inside %temp%\Virtualbox\ see files signature: VirtualBox-5.1.0-r108711-MultiArch_amd64.msi VirtualBox-5.1.0-r108711-MultiArch_x86.msi |
|||
| #16389 | obsolete | guest kernel panic on continious high usage | ||
| Description |
Host machine runs Debian Jessie 64 bit and Guest machine the same. from time to time I am experiencing a kernel panic on the guest, making the virtual machine unresponsive. A soft reset from VirtualBox GUI will not work for the vm in question, the process has to be killed from console entirely and started again. The other running VMs are not affected when this even occurs. I can't find relevant info in the vbox.log files on the host so I am attaching a print screen with the call trace that is shown on the guest console. |
|||

