Hi, Today I tested again this with the same 2.6.23 kernel that I used the first time and virtualbox-ose 1.6.2-dfsg-1 (using a Windows 2000 SP4 guest). It seems that this bug is not reproducable any more. I guess virtualbox 1.6.0 solved the issue (as the changelog states many fixes for VT-x/SVM).
I guess this bug needs to be closed now. Regards, George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
