Subject: | |
From: | |
Reply To: | |
Date: | Thu, 20 Jan 2011 17:52:55 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Thu, Jan 20, 2011 at 9:30 AM, Troy Dawson <[log in to unmask]> wrote:
> Hello,
> We have had our first kernel security update following the release of SL
> 5.6. We have tested it on a SL5.0 machine. It installs, runs and openafs
> works on it. I would feel much better if others ran it to make sure it
> works for them.
>
> Can others test this kernel out on their machines to make sure it doesn't
> break something we didn't expect.
>
> I have also put the new kvm into the x86_64 testing area with the kernel.
I installed the following updates on a SL 5.5 x86_64 system:
kernel-2.6.18-238.1.1.el5.x86_64.rpm
kernel-devel-2.6.18-238.1.1.el5.x86_64.rpm
kernel-headers-2.6.18-238.1.1.el5.x86_64.rpm
kmod-kvm-83-224.el5.x86_64.rpm
kvm-83-224.el5.x86_64.rpm
kvm-qemu-img-83-224.el5.x86_64.rpm
kvm-tools-83-224.el5.x86_64.rpm
I noticed kvm.ko was built against the 2.6.18-238 kernel. A correct
symlink was created for the 2.6.18-238.1.1 kernel. One odd
observation is that kvm.ko of the earlier kernels (2.6.18-194.xx) now
points to non-existing files (broken symlinks). This may not be a
problem unique to SL but was probably inherited from TUV.
In any event, kvm guests run fine without any problem under the kernel
2.6.18-238.1.1.
Akemi
|
|
|