| 1 |
On 161025-19:35+0200, wabe wrote: |
| 2 |
> Am Dienstag, 25.10.2016 um 18:24 |
| 3 |
> schrieb Miroslav Rovis <miro.rovis@××××××××××××××.hr>: |
| 4 |
> |
| 5 |
> > The other correspondent in this thread, Michael Orlitzky, mentioned |
| 6 |
> > how 4.7.10 already works fine for him. |
| 7 |
> > |
| 8 |
> > I'll paste and ask him here: |
| 9 |
> > |
| 10 |
> > > > I'm testing 4.7.10 and will have it stabilized soon. |
| 11 |
> > > > |
| 12 |
> > > |
| 13 |
> > > FWIW, I've been panic-updating all of our x86/amd64 servers (mostly |
| 14 |
> > > HP Proliant) to 4.7.10 and nothing has blown up yet. |
| 15 |
> > |
| 16 |
> > Michael, |
| 17 |
> > |
| 18 |
> > are you talking about that bug: |
| 19 |
> > |
| 20 |
> > =sys-kernel/hardened-sources-4.7.6: Kernel panic when starting KVM |
| 21 |
> > guests |
| 22 |
> > > > https://bugs.gentoo.org/show_bug.cgi?id=597554 |
| 23 |
> > having been fixed in 4.7.10 |
| 24 |
> |
| 25 |
> Interesting. I'm using hardened-sources-4.7.6 and qemu-2.7.0-r4 and |
| 26 |
> don't have any problems so far. I'm using qemu VMs with xubuntu |
| 27 |
> 14.04 and 16.04. |
| 28 |
You mean your hardened-sources-4.7.6 are set up as grsecurity-hardened ? |
| 29 |
|
| 30 |
Or are they maybe SELinux hardened ? Or AppArmor hardened ? Or other? |
| 31 |
(really not familiar much with all the options in the hardened) |
| 32 |
|
| 33 |
Regards! |
| 34 |
-- |
| 35 |
Miroslav Rovis |
| 36 |
Zagreb, Croatia |
| 37 |
http://www.CroatiaFidelis.hr |
Archives