V2V : virt-v2v failure - No bootable kernels installed, and no replacement is available.

Latest response

Hi

 

Attempting to use virt-v2v to migrate RH KVM guest to RHEV3. 

Everything seemed to be going well  but then fell in a heap. Any ideas ?

 

# virt-v2v -ic qemu+ssh://root@lhpkvm02a.pgds.local/system -o rhev -os lhprevm01.pgds.local:/rhev-export/export --network rhevm lhpbdsl01v

lhpbdsl01v-rootvg: 100% [========================================================================================================
lhpbdsl01v-appvg: 100% [=====================================================================================================================]D 0h49m06s
find: failed to restore initial working directory: Permission denied

virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing: rhel/5/kernel-2.6.18-128.el5.x86_64.rpm rhel/5/ecryptfs-utils-56-8.el5.x86_64.rpm rhel/5/ecryptfs-utils-56-8.el5.i386.rpm
virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing: rhel/5/kernel-2.6.18-128.el5.x86_64.rpm rhel/5/ecryptfs-utils-56-8.el5.x86_64.rpm rhel/5/ecryptfs-utils-56-8.el5.i386.rpm
virt-v2v: No bootable kernels installed, and no replacement is available.

Responses

Support case 00723173
 

I understand the "missing files" bit and will correct those but still unsure of the first error and if its fatal to the migration process.

 

find: failed to restore initial working directory: Permission denied

Missing RPM's were placed in the appropriate area on the v2v server (/var/lib/virt-v2v/software/rhel/5) but it still failed with "virt-v2v: No bootable kernels installed, and no replacement is available."

What I fail to fathom is why its even attempting to inject an earlier kernel than the one already installed on the VM (2.6.18-238.9.1.el5) as this clearly has the required virtio drivers.

Proof that it locates a later kernel , so why try and install an earlier one and then barf ?

 

command: command: warning: /transferngfQW5/rhel/5/kernel-2.6.18-128.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
        package kernel-2.6.18-194.8.1.el5.x86_64 (which is newer than kernel-2.6.18-128.el5.x86_64) is already installed
        package kernel-2.6.18-238.9.1.el5.x86_64 (which is newer than kernel-2.6.18-128.el5.x86_64) is already installed at /usr/share/perl5/vendor_perl/Sys /VirtConvert/GuestfsHandle.pm line 193.
 at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 1344
command: command: warning: /transferngfQW5/rhel/5/kernel-2.6.18-128.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
        package kernel-2.6.18-194.8.1.el5.x86_64 (which is newer than kernel-2.6.18-128.el5.x86_64) is already installed
        package kernel-2.6.18-238.9.1.el5.x86_64 (which is newer than kernel-2.6.18-128.el5.x86_64) is already installed at /usr/share/perl5/vendor_perl/Sys /VirtConvert/GuestfsHandle.pm line 193.
 at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 1344
virt-v2v: No bootable kernels installed, and no replacement is available.

 

 

Hi Richard,

 

Just confirmed this is not a known issue, so please open a support case with logs attached, so it can be properly investigated. 

 

Thanks,

Dan

Dan

 

I've been able to get my VM to migrate.

I suspect the failures I was seeing were due to some malformed initrd's in /boot of my VM which was sending the virt-v2v off track.

The initrd's were removed and the process ran without fault.

I'll do some further tests and will confirm the results.

 

Cheers

 

Hello

 

Three things were required to fix the virt-v2v migration :-

 

1)  Removal of old kernel
    # yum remove kernel-2.6.18-128.2.1.el5

 

2)  Removal of incorrecly named initrd's from /boot   ( wasn't me :-)  )
    # rm /boot/2.6.18-128.2.1.el5.img
    # rm /boot/2.6.18-128.el5.img

 

3)  Removal of redundant kernel parameter from /boot/grub/grub.conf (notsc divider = 10)
    kernel /vmlinuz-2.6.18-238.9.1.el5 ro root=/dev/SPlhpbdsl01vVG/Root rhgb quiet notsc divider = 10

 

Without action point 3), the virt-v2v will fail with error similar to:-

 

virt-v2v: augeas error for /etc/grub.conf: Iterated lens matched less than it should
error at line 16, char 0, file position 523
augeas lens: /usr/share/augeas/lenses/dist/grub.aug:180.14-.63:
augeas error for /boot/grub/menu.lst: Iterated lens matched less than it should
error at line 16, char 0, file position 523
augeas lens: /usr/share/augeas/lenses/dist/grub.aug:180.14-.63:

 

I guess the augeas lens for grub does not account for something in that param string. Probably the =

 

I must admit that this particular VM has been around a while (originally 5.2) and seen quite a bit of kernel churn in that time.

Thanks

Thanks for following up with the solution on this one, Rich.