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.

Created attachment 661948 [details]
Error details during migration from 6.2 to 6.1

Description of problem:

Unable to migrate guest: internal error Process exited while reading console log output: Supported machines are:
pc         RHEL 6.1.0 PC (alias of rhel6.1.0)
rhel6.1.0  RHEL 6.1.0 PC (default)
rhel6.0.0  RHEL 6.0.0 PC
rhel5.5.0  RHEL 5.5.0 PC
rhel5.4.4  RHEL 5.4.4 PC
rhel5.4.0  RHEL 5.4.0 PC

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

How reproducible:
100%

Steps to Reproduce:
1. Create a VM on RHEL 6.2 host using virt-manager.
2. From the virt-manager GUI go to the VM created.
3. Right click and migrate to other host(RHEL 6.1).
  
Actual results:
Unable to migrate guest: internal error Process exited while reading console

Expected results:
Migration should be successful as the supported RHEL version is listed in the error.


Additional info:
Verified on multiple VM's. Here is the list of VM's:
1.	RHEL   6.2 32 Bit
2.	RHEL 6.2 64 Bit
3.	RHEL 5.8 32 Bit
4.	RHEL 5.8 64 Bit
5.	Windows 2003 32Bit
6.	Windows 2003 64Bit
7.	Windows 2008 64Bit
8.	Windows 7 32Bit
9.	Windows 7 64Bit

The error is same.

Migrating from newer release to older is only supported if either the VM was
originally created on the older release and migrated to newer or if it was
created on the newer release with compatibility in mind. And the
"compatibility in mind" means that the VM must not make use of new features
introduced in the new release and it must be created with machine type that is
supported on the older release. And this last condition was not satisfied
since qemu-kvm on 6.1 complains that it does not know the machine type used by
your VM. Creating a new VM in virt-manager automatically sets its machine type
to the newest one (i.e, rhel6.2.0), which is not compatible with qemu-kvm from
RHEL-6.1. You can change the machine type manually using 'virsh edit VM' and
change machine attribute in domain/os/type element to 'rhel6.1.0'.

Note, that machine describes a version of virtual hardware provided to the VM
and also the format of migration data.

Anyway, this works as expected.