Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
As this issue still exists on rhel6.3,so clone this bug to rhel6.3.
+++ This bug was initially created as a clone of Bug #742757 +++
Created attachment 525937[details]
output of the conversion run with LIBGUESTFS_TRACE=1
Description of problem:
virt-v2v always use the first kernel (0th kernel) instead of the default kernel (ex: default=1).
Version-Release number of selected component (if applicable):
virt-v2v-0.7.1-4.el5
How reproducible:
Always.
Steps to Reproduce:
Before migration: - note that running kernel is in position 1
p652900@qvlsbd01:~$ uname -r
2.6.18-194.26.1.el5
p652900@qvlsbd01:~$ sudo cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/vg_system_01/root_vol
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-194.17.4.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.17.4.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.17.4.el5.img
title Red Hat Enterprise Linux Server (2.6.18-194.26.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.26.1.el5.img
title Red Hat Enterprise Linux Server (2.6.18-194.3.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.3.1.el5.img
After migration:
[root@qvlsbd01 ~]# uname -r
2.6.18-194.17.4.el5
[root@qvlsbd01 ~]# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/vg_system_01/root_vol
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-194.17.4.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.17.4.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.17.4.el5.img
title Red Hat Enterprise Linux Server (2.6.18-194.26.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.26.1.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.26.1.el5.img
title Red Hat Enterprise Linux Server (2.6.18-194.3.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/vg_system_01/root_vol divider=10 clocksource=acpi_pm
initrd /initrd-2.6.18-194.3.1.el5.img
Can only boot off 2.6.18-194.17.4.el5, if i boot from the other 2 i get a kernel panic, screen shot attached.
To resolve the issue, i need to mkinitrd the latest kernel, then it boots fine if i set it as default.
Expected results:
virt-v2v should use the default kernel to create new migrated VM.
Additional info:
--- Additional comment from mbooth on 2012-04-23 06:10:37 EDT ---
Users are encouraged to use virt-v2v from RHEL 6.
Comment 2RHEL Program Management
2012-12-14 06:50:30 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.