Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

Hi,

On Mon, Mar 04, 2019 at 04:22:19PM -0500, Karl Johnson wrote:

On Mon, Mar 4, 2019 at 6:13 AM Anthony PERARD <[1]anthony.perard@citrix.com> wrote:

 On Wed, Feb 27, 2019 at 03:12:40PM -0500, Karl Johnson wrote:
 > I built 4.9.161, works for me on el6:
 >
 > [root@node-tmp1 ~]# cat /proc/version
 > Linux version 4.9.161-34.el6.x86_64
 ([2]mockbuild@build.aerisnetwork.net) (gcc
 > version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP Wed Feb 27
 09:48:40
 > EST 2019
 >
 > Only one strange thing, I had to run grub-install because Grub
 couldn't
 > find root device after reboot, not sure this has something to do with
 the
 > kernel upgrade.
 > Kernel 4.9.161 doesn't have the patch for CVE-2019-8912 yet so we
 might
 > wait until it get released.
 >
 > I updated my PR: [3]https://github.com/CentOS-virt7/xen-kernel/pull/18

 Hi Karl, I've build and tested your PR, but without the GCC7 patch, and
 when I've tested it on el6, none of the guests had network access.
 I had to revert the bridge changes to have them working
 (CONFIG_BRIDGE_NETFILTER=m and CONFIG_BRIDGE=m).

 Why did you want the BRIDGE built-in instead of a module?

 Maybe you have something to setup the bridge (probably filter) properly,
 or maybe something is different in the xen package between el6 and el7.
 Any idea?

 I still have to investigate the Xen pkg, and have a closer look at those
 tests I'm running.

Hum strange. I switched from module to built-in because I always had a deprecated warning about bridge when booting CentOS 6 (and I guess everyone needs bridge?). I don't remember what was the exact warning because it's been a long time since I switched it. I don't mind to put it back as a module, both works for me but the warning is gone when built-in.

Yeah better to keep things as modules, like they have been.

btw upstream Linux 4.9 LTS kernel is now at 4.9.162 :)

Karl

-- Pasi