Bug 623172 - virt-v2v does not update the default kernel configuration
virt-v2v does not update the default kernel configuration
Status: CLOSED DUPLICATE of bug 609526
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-v2v (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Matthew Booth
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2010-08-11 10:19 EDT by Gunther Schlegel
Modified: 2010-09-06 05:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-06 05:52:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gunther Schlegel 2010-08-11 10:19:38 EDT
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):

How reproducible:
Migrate a paravirtualized VM from XEN to RHEV / KVM.

Steps to Reproduce:
Actual results:
/etc/sysconfig/kernel contains "DEFAULTKERNEL=kernel-xen"

Expected results:
/etc/sysconfig/kernel contains "DEFAULTKERNEL=kernel"

Additional info:
Comment 1 Richard W.M. Jones 2010-08-11 10:30:55 EDT
I was so sure that we did this already, but I have
just checked the upstream code and this file is not
Comment 2 Matthew Booth 2010-09-06 05:52:34 EDT

*** This bug has been marked as a duplicate of bug 609526 ***

Note You need to log in before you can comment on or make changes to this bug.