+++ This bug was initially created as a clone of Bug #594010 +++ Created an attachment (id=415380) virt-v2v.conf Description of problem: The virt-v2v.conf is lower than the guest, so the guest is downgraded to a lower version of kernel. Version-Release number of selected component (if applicable): v2v-libvirt-0.8.1-1.el5 virt-v2v-0.6.0-1.el5 How reproducible: always Steps to Reproduce: 1. In guest: rhn_register to register rhn 2. convert the guest registered rhn #virt-v2v -f virt-v2v.conf -i libvirtxml -o rhev -osd nfs:/export domain_xml 3. Actual results: the guest is still installed the kernel specified in virt-v2v.conf although it is registered rhn. Expected results: the guest registered rhn should Additional info: Convert the guest without registering rhn, I'll get the error message: virt-v2v -f /etc/virt-v2v.conf -i libvirtxml -o rhev -osd nfs:/export /tmp/xen-RHEL-4.8-32-pv.raw.xml virt-v2v: Failed to install packages using up2date. Error message was: command: at /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/GuestOS/RedHat.pm line 773. --- Additional comment from rwu on 2010-05-20 06:39:44 EDT --- Created an attachment (id=415381) log from LIBGUESTFS_TRACE=1 during conversion --- Additional comment from rwu on 2010-05-20 06:42:37 EDT --- Created an attachment (id=415382) log from virt-inspect before conversion --- Additional comment from llim on 2010-05-20 08:56:38 EDT --- Please include the yum.log or up2date log so we can see if the update is successful.
Could you please include LIBGUESTFS_TRACE=1 output for the RHEL 4 failure?
Created attachment 415564 [details] log during conversion from LIBGUESTFS_TRACE=1
Created attachment 415620 [details] xenpv-rhel48-rhn log
It's unclear to me why this was cloned. It looks like a straight dupe of 594010, just that it happens to affect a different guest type?
That wasn't clear at the time I cloned it :) However, it can be closed now. *** This bug has been marked as a duplicate of bug 594010 ***