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.

Bug 1372154

Summary: guest with pci-bridge setting shutdown on the target host after migration when migration from rhel7.3 to rhel7.0.
Product: Red Hat Enterprise Linux 7 Reporter: yafu <yafu>
Component: libvirtAssignee: Laine Stump <laine>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: dgilbert, dyuan, fjin, mzhan, rbalakri, yanqzhan, zpeng
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-02 15:54:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description yafu 2016-09-01 04:09:30 UTC
Description of problem:
guest with pci-bridge setting shutdown on the target host after migration when migration from rhel7.3 to rhel7.0.

Source:
libvirt-2.0.0-6.el7.x86_64
qemu-kvm-rhev-2.6.0-22.el7.x86_64

target:
libvirt-1.1.1-29.el7_0.7.x86_64
qemu-kvm-rhev-1.5.3-60.el7_0.10.x86_64

How reproducible:
100%


Version-Release number of selected component (if applicable):
Source:
libvirt-2.0.0-6.el7.x86_64
qemu-kvm-rhev-2.6.0-22.el7.x86_64

target:
libvirt-1.1.1-29.el7_0.7.x86_64
qemu-kvm-rhev-1.5.3-60.el7_0.10.x86_64

How reproducible:
100%

Steps to reproduce:
1.Start a guest with pci-bridge setting:
 #virsh dumpxml mig1
  ...
 <controller type='pci' index='1' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </controller>
  ...

2.Do migration:
#virsh migrate mig1 qemu+ssh://10.66.144.29/system --live --verbose
Migration: [100 %]

4.Check the guest status on the target host:
#virsh list | grep mig1
no output

5.Check the qemu log on the target host:
...
Unknown savevm section or instance 'PCIBUS' 1
load of migration failed
2016-08-26 09:15:54.412+0000: shutting down
...


Actual results:
Migration failed

Expected results:
Migration complete correctly.

Comment 2 Fangge Jin 2016-09-02 13:04:43 UTC
This bug seems to have same cause with Bug 1172643 which was closed as WON'T FIX

Comment 3 Laine Stump 2016-09-02 15:54:31 UTC
Good catch!

From Bug 1172643, it sounds like the problem is in qemu-kvm-rhev 7.0, so that's where any fix would have to be, and since pci-bridge was only tech-preview then, it's unlikely any customer would encounter it in production.

I'm Cc'ing Dave Gilbert just in case his opinion has changed in the last year and a half.

Comment 4 Dr. David Alan Gilbert 2016-09-05 10:18:35 UTC
Yes that probably is the same as 1172643 - 7.0 had a problem with multiple PCI busses, and since bridges were tech-preview then it's a wontfix.