Hi!
On Fri, Feb 24, 2012 at 03:41:27PM +0200, PaX Team wrote:
> well, as i suggested it in bugzilla, i'd need to capture information about
> the crash (probably triple fault), and the best approach would be some nested
> virtualization setup. i have no idea how to do it easily (one way would be to
> use bochs to run vmware if its vmx emulation is good enough but i guess the
> resulting speed would be unbearable).
That sounds too complex and slow.
> another (but still time consuming) approach would be to do a binary search on
> vmmon by stopping it at various points as it is about to launch a virtual
> machine,
> that would eventually narrow down the failing code too.
I probably can do this if you give me an example of how this should be
done - i.e. example of code snippet to insert into vmmon source to stop at
various point and start/end lines in code or involved function names where
to place that snippet.
BTW, I think it probably makes more sense to do a binary search from other
side - remove parts of hardened changes in kernel. We already know it's
not related to code disabled when PAX and GRSEC completely disabled in
kernel config, so probably there is not so many hardened changes left
which still active and may affect virtualization.
--
WBR, Alex.
