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 1657130 - Can't migrate from rhel8 to rhel7 when guest xml has device "sound"
Summary: Can't migrate from rhel8 to rhel7 when guest xml has device "sound"
Keywords:
Status: CLOSED DUPLICATE of bug 1655820
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Dr. David Alan Gilbert
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-07 07:51 UTC by gaojianan
Modified: 2019-11-14 23:41 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-10 04:06:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
target and source migrate log (27.07 KB, text/plain)
2018-12-07 07:51 UTC, gaojianan
no flags Details

Description gaojianan 2018-12-07 07:51:56 UTC
Created attachment 1512407 [details]
target and source migrate log

Description of problem:
As subject

Version-Release number of selected component (if applicable):
libvirt-4.9.0-1.module+el8+2241+fdba4e12.x86_64
qemu-kvm-3.1.0-0.module+el8+2266+616cf026.next.candidate.x86_64

qemu-kvm-rhev-2.12.0-19.el7_6.2.x86_64
libvirt-4.5.0-10.el7_6.2.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a guest xml with device "video" in rhel8.
[root@localhost ~]# virsh list
 Id   Name    State   
-----------------------
 38   demo1   running 

[root@localhost ~]# virsh dumpxml demo1
...
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
...

2.Do migrate from rhel8 to rhel7.
[root@localhost ~]# virsh migrate demo4 --live --verbose qemu+ssh://10.66.4.170/system  --copy-storage-all
root.4.170's password:
Migration: [100 %]error: internal error: qemu unexpectedly closed the monitor: 2018-12-04T06:45:11.296515Z qemu-kvm: Failed to load hda-audio:st
2018-12-04T06:45:11.296751Z qemu-kvm: error while loading state for instance 0x0 of device 'hda-audio'
2018-12-04T06:45:11.296809Z qemu-kvm: warning: TSC frequency mismatch between VM (3092982 kHz) and host (2659999 kHz), and TSC scaling unavailable
2018-12-04T06:45:11.297457Z qemu-kvm: warning: TSC frequency mismatch between VM (3092982 kHz) and host (2659999 kHz), and TSC scaling unavailable
2018-12-04T06:45:11.297627Z qemu-kvm: load of migration failed: No such file or directory

Actual results:
As above

Expected results:
Can migrate successfully without error.

Additional info:

Comment 2 gaojianan 2018-12-10 04:06:06 UTC

*** This bug has been marked as a duplicate of bug 1655820 ***


Note You need to log in before you can comment on or make changes to this bug.