Description of problem:
When installing a new kernel, grubby will only activate it if the package matches the DEFAULTKERNEL definition in /etc/sysconfig/kernel.
The default kernel on a paravirtualized XEN-VM is "kernel-xen".
The default kernel on a KVM-VM is "kernel".
virt-v2v does change the installed kernel and updates the grub configuration, but does not update /etc/sysconfig/kernel accordingly. Therefore updated kernel are not activated by default.
Version-Release number of selected component (if applicable):
Migrate a paravirtualized VM from XEN to RHEV / KVM.
Steps to Reproduce:
/etc/sysconfig/kernel contains "DEFAULTKERNEL=kernel-xen"
/etc/sysconfig/kernel contains "DEFAULTKERNEL=kernel"
I was so sure that we did this already, but I have
just checked the upstream code and this file is not
*** This bug has been marked as a duplicate of bug 609526 ***