Am Dienstag, 25.10.2016 um 20:17 schrieb Miroslav Rovis <miro.ro...@croatiafidelis.hr>:
> On 161025-19:35+0200, wabe wrote: > > Am Dienstag, 25.10.2016 um 18:24 > > schrieb Miroslav Rovis <miro.ro...@croatiafidelis.hr>: > > > > > The other correspondent in this thread, Michael Orlitzky, > > > mentioned how 4.7.10 already works fine for him. > > > > > > I'll paste and ask him here: > > > > > > > > I'm testing 4.7.10 and will have it stabilized soon. > > > > > > > > > > > > > FWIW, I've been panic-updating all of our x86/amd64 servers > > > > (mostly HP Proliant) to 4.7.10 and nothing has blown up yet. > > > > > > Michael, > > > > > > are you talking about that bug: > > > > > > =sys-kernel/hardened-sources-4.7.6: Kernel panic when starting KVM > > > guests > > > > > https://bugs.gentoo.org/show_bug.cgi?id=597554 > > > having been fixed in 4.7.10 > > > > Interesting. I'm using hardened-sources-4.7.6 and qemu-2.7.0-r4 and > > don't have any problems so far. I'm using qemu VMs with xubuntu > > 14.04 and 16.04. > You mean your hardened-sources-4.7.6 are set up as > grsecurity-hardened ? > > Or are they maybe SELinux hardened ? Or AppArmor hardened ? Or other? > (really not familiar much with all the options in the hardened) I'm using grsecurity but I don't have PAX_MEMORY_SANITIZE enabled. According to PaX Teams reply to my last message this is the reason why I don't have problems with qemu. -- Regards wabe
