| 1 |
On 15 Feb 2012 at 21:23, Alex Efros wrote: |
| 2 |
|
| 3 |
> So, I've just tested hardened vs non-hardened kernels using exactly same |
| 4 |
> vmware-modules. Result is same: on hardened kernel vmware reset host, |
| 5 |
> on gentoo kernel vmware works ok. |
| 6 |
> |
| 7 |
> If you've any ideas how to debug/fix this issue - I'm ready to test |
| 8 |
> anything you need. VMware is critical tool for my work, so without it |
| 9 |
> chances are I'll have to convert my system back to x86. :( |
| 10 |
|
| 11 |
well, as i suggested it in bugzilla, i'd need to capture information about |
| 12 |
the crash (probably triple fault), and the best approach would be some nested |
| 13 |
virtualization setup. i have no idea how to do it easily (one way would be to |
| 14 |
use bochs to run vmware if its vmx emulation is good enough but i guess the |
| 15 |
resulting speed would be unbearable). |
| 16 |
|
| 17 |
another (but still time consuming) approach would be to do a binary search on |
| 18 |
vmmon by stopping it at various points as it is about to launch a virtual machine, |
| 19 |
that would eventually narrow down the failing code too. |
| 20 |
|
| 21 |
> > > +CONFIG_IA32_AOUT=y |
| 22 |
> > btw, i don't think you need/want a.out support anywhere these days ;) |
| 23 |
> |
| 24 |
> Who knows. It shouldn't make any harm, anyway. I can remember about two |
| 25 |
> cases in last ~2-3 years when I did something with a.out. Don't remember |
| 26 |
> details, and that was surely very strange tasks, but it happens. |
| 27 |
|
| 28 |
that's weird, i don't think the toolchain can even produce anything but |
| 29 |
ELF for some time now ;). as for harm, the a.out loader has had its share |
| 30 |
of security vulnerabilities and has usually been disabled by security |
| 31 |
conscious distros such as Owl for many years now. but it's your risk&call ;). |
Archives