Created attachment 411917 [details]
Description of problem:
My guest has many kernels installed, but some of them will be kernel panic after conversion
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.#virt-v2v -f virt-v2v.conf -o rhev -osd nfs:/export kvm-RHEL-3.9-32.raw
2.Import the vm to run on rhevm
all of the kernels in the guest can boot succuessfully
/etc/grub.conf from guest:
# 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/hda2
# initrd /initrd-version.img
title Red Hat Enterprise Linux AS (2.4.21-63.ELsmp)
kernel /vmlinuz-2.4.21-63.ELsmp ro root=LABEL=/
title Red Hat Enterprise Linux AS (2.4.21-60.EL)
kernel /vmlinuz-2.4.21-60.EL ro root=LABEL=/
title Red Hat Enterprise Linux AS (2.4.21-58.EL)
kernel /vmlinuz-2.4.21-58.EL ro root=LABEL=/
title Red Hat Enterprise Linux AS (2.4.21-50.ELsmp)
kernel /vmlinuz-2.4.21-50.ELsmp ro root=LABEL=/
title Red Hat Enterprise Linux AS (2.4.21-50.EL)
kernel /vmlinuz-2.4.21-50.EL ro root=LABEL=/
Created attachment 411918 [details]
screen shot from /etc/fstab
Created attachment 411919 [details]
virt-inspect.log before conversion
Created attachment 411920 [details]
conversion_trace.log during conversion
Can you confirm which kernels work and which don't? I suspect this is the same as bug 587619, meaning that only the default kernel will work.
(In reply to comment #4)
> Can you confirm which kernels work and which don't? I suspect this is the same
> as bug 587619, meaning that only the default kernel will work.
As the grub.conf described in Additional Info,the default kernel is 63.ELsmp, but it will become kernel panic.
Status of the coversion kernels:
63.ELsmp kernel panic
60.EL boot successfully
58.EL boot successfully
50.ELsmp kernel panic
50.EL kernel panic
Patch posted for this one here:
Fixed in 0.5.4
(In reply to comment #8)
> Fixed in 0.5.4
After you fix, does v2v still only support to convert the default kernel? Is it expected that only the default kernel can be booted successfully after conversion？
Yes. This isn't a fix for the general problem of multiple kernels. I still haven't decided what to do about that. I've left bug 587619 open to track that.
(In reply to comment #10)
> Yes. This isn't a fix for the general problem of multiple kernels. I still
> haven't decided what to do about that. I've left bug 587619 open to track that.
OK, with v2v-0.5.4, the default kernel can boot successfully after conversion.
This was released in virt-v2v-0.6.0-6.el5