VirtualBox

Changes between Initial Version and Version 1 of Ticket #18387, comment 2


Ignore:
Timestamp:
02/18/2019 10:54:52 PM (3 years ago)
Author:
Josh 123
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18387, comment 2

    initial v1  
    11Just want to add, I've also tested this with "Windows Hypervisor Platform" feature (different from Hyper-V Platform) enabled as well, in additional to the entire Hyper-V feature node. 
    22 
    3 This was on Windows 1809, with Vritualbox 6.0.1 and 6.0.4 both exhibiting the same behaviour. I also investigated disabling "Control Flow Guard" for all the VBox services and process as per the line of thinking in this Hyper-V related issue: https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt  
     3This was on Windows 1809, with Vritualbox 6.0.1 and 6.0.4 both exhibiting the same behaviour. I also investigated disabling "Code Flow Guard" for all the VBox services and process as per the line of thinking in this Hyper-V related issue: https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt  
    44 
    55This also had no affect. Hyper-V works fine, but the VBox guests freeze as noted by others.  

www.oracle.com
ContactPrivacy policyTerms of Use