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 1657436 - migration with shmem device is not supported
Summary: migration with shmem device is not supported
Keywords:
Status: CLOSED DUPLICATE of bug 1657651
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.3
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Jing Qi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-08 05:54 UTC by wuaq
Modified: 2018-12-10 09:07 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description wuaq 2018-12-08 05:54:57 UTC
Description of problem:
     It report use migration with shmem device is not supported , when I use the command "virsh migrate --live" to migrate a VM to another host.  
     Migration succeed when I use the same command in ubuntu
           

Version-Release number of selected component (if applicable):
     libvirt 3.9.0
     qemu-kvm  2.8.1

How reproducible:
     

Steps to Reproduce:


1.prepare ivshmem-sever
  get qemu code from  https://download.qemu.org/
  version is 2.8.1  
  ivshmem-sever is in the path qemu-2.8.1\contrib\ivshmem-server.
  compile ivshmem-server.c and main.c 

2. prepare guest with ivshmem-doorbell:
  <shmem name='shmem_server'>
      <model type='ivshmem-doorbell'/>
      <server path='/tmp/ivshmem_socket'/>
      <msi vectors='2' ioeventfd='on'/>
  </shmem> 

3.virsh start vm

4.virsh migrate --live vm qemu+ssh://target/system

Actual results:
     error: Requested operation is not valid: migration with shmem device is not supported

Expected results:
      

Additional info:

Comment 2 wuaq 2018-12-08 06:03:17 UTC
if the ivshmem is ivshmem-plain, it also cann't be migrated.
    <shmem name='my_shmem1'>
      <model type='ivshmem-plain'/>
      <size unit='M'>4</size>
    </shmem>

Comment 3 wuaq 2018-12-08 06:03:24 UTC
if the ivshmem is ivshmem-plain, it also cann't be migrated.
    <shmem name='my_shmem1'>
      <model type='ivshmem-plain'/>
      <size unit='M'>4</size>
    </shmem>

Comment 4 Jing Qi 2018-12-10 08:28:58 UTC
From the bug description, are you using the upstream qemu? With downstream version (qemu-kvm-rhev) and libvirt version, the shmem migration was disabled. It's not supported.

Comment 5 Jiri Denemark 2018-12-10 09:07:42 UTC
Closing as a duplicate of a newer bug 1657651, which has a better description.

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


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