Bug 1145583

Summary: xen kernel should be removed from boot menu after conversion by virt-v2v
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: codong, dyuan, juzhou, leiwang, mbooth, mzhan, ptoscano, rjones
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: V2V
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-20 12:24:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description tingting zheng 2014-09-23 10:30:48 UTC
Description
xen kernel should be removed from boot menu after conversion by virt-v2v

Version:
libguestfs-1.27.52-1.1.el7.x86_64
virt-v2v-1.27.52-1.1.el7.x86_64

How reproducible:
50%

Steps to Reproduce:
1.Use virt-v2v to convert a xen pv guest.
# virt-v2v -ic xen+ssh://10.66.106.64 -os default  pv-rhel58-nolvm
[   0.0] Opening the source -i libvirt -ic xen+ssh://10.66.106.64 pv-rhel58-nolvm
[  16.0] Creating an overlay to protect the source from being modified
[  30.0] Opening the overlay
[  52.0] Initializing the target -o libvirt -os default
[  52.0] Inspecting the overlay
[  76.0] Checking for sufficient free disk space in the guest
[  76.0] Estimating space required on target for each disk
[  76.0] Converting Red Hat Enterprise Linux Server release 5.8 (Tikanga) to run on KVM
This guest has virtio drivers installed.
[  90.0] Mapping filesystem data to avoid copying unused and blank areas
[  91.0] Closing the overlay
[  91.0] Copying disk 1/1 to /var/lib/libvirt/images/pv-rhel58-nolvm-sda (raw)
    (100.00/100%)
[ 216.0] Creating output metadata
Pool default refreshed

Domain pv-rhel58-nolvm defined from /tmp/v2vlibvirtfa2d3e.xml

2.After conversion,boot the guest.
# virsh start pv-rhel58-nolvm

3.After boot the guest,check the boot menu,there are still 2 kernel:both regular kernel and xen kernel.

Actual results:
As description.

Expected results:
xen kernel should be removed from boot menu after conversion by virt-v2v

Additional info:
If try to boot xen kernel,it will fail with error.

Comment 1 Richard W.M. Jones 2014-09-23 10:44:37 UTC
As this is cosmetic, I'm going to cond NACK (capacity) and
defer to a later RHEL release.

Comment 2 Richard W.M. Jones 2015-04-20 12:24:05 UTC
Since this involves more risky edits to the grub configuration
of the guest, I'm not going to do this.  There's too much risk
that removing bits from the grub config will break the guest or cause
conversion failures.

virt-v2v should (and currently does) select the correct non-Xen
kernel as default, so the guest will boot after conversion without
interaction [if that was not the case, it would be a bug].

If users manually select alternate Xen kernels and try to boot
with them, then that's just too bad.