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.

Description of problem:
In rhel6, there is no Xen kernel any more, so that it's impossible for us to convert a local Xen virtualized guest.
It's better to erase 25.2.2. Converting a local Xen virtualized guest

(http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Virtualization/#chap-Virtualization-v2v-migration)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

  
Actual results:


Expected results:


Additional info:

This is still possible, because the host may have been upgraded in place from RHEL 5 to RHEL 6.

Oh, maybe I let you misunderstand. My point is we cannot convert Xen guests via running  'virt-v2v -ic xen:///localhost -op pool --bridge brname vm-name', because there is no Xen kernel in RHEL6. (also xen:///localhost should be xen:/// or xen:///system )

Ah, yes. I'd forgotten that was in there.

I think the section needs to stay because we still want to support upgrading from RHEL 5 to RHEL 6. However, there is no need to document the case where the Xen hypervisor is running as this isn't possible in RHEL 6 as you say.

David, can you fix this bug for RHEL and RHEV?

Chris

I have removed the xen:///localhost example from the RHEL 6 guide only. Fixed in build:

Red_Hat_Enterprise_Linux-Virtualization-6-web-en-US-0-44.el5

Verified: Red_Hat_Enterprise_Linux-Virtualization-6-web-en-US-0-47.el5

xen:/// removed, section remains :)

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.