So? Is there any decision what we are doing? Branching? Releasing? Postponing?
2011/12/20, caemyr@myopera.com caemyr@myopera.com:
Please DO NOT tie this bug with VT-x. On iCore series CPU host, this bug will happen even with VT-x is enabled. In this case, only nested paging enabled will mitigate the bug.
If nested paging will stop helping in this case for any reason, my testbot machine is out of business.
On Mon, Dec 19, 2011, at 04:30 PM, victor martinez wrote:
Wasn't the best way to avoid the issue just to disable VT-X in the VM configuration under VBOX?Or doesn't this trick work always? We can add a explicit message as "Ey,you!If you are using VboX greater than 4.0 and you face this issue, just disable VT-X for now and done!" If there is a way that any tester can use the VM...where is the big drama?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- With best regards Caemyr
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev