Custom Query (16363 matches)
Results (838 - 840 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10273 | obsolete | VirtualBox Support for ASLR | ||
| Description |
Windows Vista has introduced new memory security protections, such as DEP/NX, ASLR (Address Space Layout Randomization) and Heap Corruption Detection, which help to block exploits of common vulnerabilities. Unfortunately VirtualBox still is not compiled to take advantage of these security features. While VirtualBox's code doesn't exhibit any weaknesses, it would be beneficial to be able to use these OS security enhancements as a backstop in the event that the hypervisor is exploited. There are also reports of there being a similar incompatibility between VirtualBox and ASLR implementations in Linux as well. Currently, forcing these OS protection settings for VirtualBox's processes causes random and complete system halts. Support for ASLR is easy to accomplish and could probably make it into the next release as all that is needed for it to work is the turning on of a bit in the executable. |
|||
| #10483 | fixed | VirtualBox 4.1.12 r77245 - VBoxUSBMon.sys causes BSOD | ||
| Description |
My Host OS experiences BSODs intermittently, shortly after I shutdown any guest on the system. After looking at the Memory Dump, the BSOD related to VBoxUSBMon.sys. I do not have USB enabled for any of my guests when this happens. For reference, please take a look at this thread: https://forums.virtualbox.org/viewtopic.php?f=1&t=49213 I will attach an xp Guest Log and also the BSOD summary to this ticket for more information. |
|||
| #10735 | duplicate | Intermittent Host BSOD when Guest is shutting down | ||
| Description |
Hi, I experience host system crashes when I shutdown a guest on a frequent but not consistent basis. This has been happening across a number of Virtualbox versions. It doesn't matter what kind of guest os I happen to be running at the time when this happens. The problem according to bluescreenview is almost always labelled as a memory management error. Attached is the memory dump and logs. Please look into this as soon as you can. |
|||

