I propose to branch right today (unless there are strong reasons not to)
and wait till time decided on the meeting for the fix/hackfix expires.
When the (hack)fix is found it would just be merged in to the release
branch, or when the time expires the branch is going to be released as
is (as decided on the meeting).
WBR,
Aleksey Bragin.
On 21.12.2011 17:43, Igor Paliychuk wrote:
So? Is there any decision what we are doing? Branching? Releasing? Postponing?
2011/12/20, [email protected]<[email protected]>:
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
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev
--
With best regards
Caemyr
_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev
