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 1412470 - Keyboard hang after migration with kernel-irqchip=split
Summary: Keyboard hang after migration with kernel-irqchip=split
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.4
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Peter Xu
QA Contact: xianwang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-12 06:25 UTC by Peter Xu
Modified: 2017-08-02 03:17 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-rhev-2.9.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 23:42:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2392 0 normal SHIPPED_LIVE Important: qemu-kvm-rhev security, bug fix, and enhancement update 2017-08-01 20:04:36 UTC

Description Peter Xu 2017-01-12 06:25:55 UTC 
Description of problem:

When VM is setup with split kernel irqchip, keyboard will stop responding after migration.

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

All versions until now, as long as with kernel-irqchip=split parameter.

How reproducible:

100%

Steps to Reproduce:

1. Start VM1 with parameter:

$qemu -M q35,kernel-irqchip=split -enable-kvm \
      -netdev user,id=net0 \
      -device e1000,netdev=net0 \
      -m 512M -monitor stdio \
      /var/lib/libvirt/images/vm1.qcow2

   wait until it boots up.

2. Start destination VM2 (suppose locally):

$qemu -M q35,kernel-irqchip=split -enable-kvm \
      -netdev user,id=net0 \
      -device e1000,netdev=net0 \
      -m 512M -monitor stdio \
      -incoming tcp:0:6666 \
      /var/lib/libvirt/images/vm1.qcow2

3. migrate VM1 -> VM2 by running HMP command on VM1:

(qemu) migrate tcp:0:6666

Actual results:

After migration finish, keyboard will stop working on VM2, and all ioapic interrupts are lost on VM2.

Expected results:

After migration finish, keyboard should not stop working.
Comment 3 yilzhang 2017-05-11 10:09:39 UTC 
This bug has been verified on x86 platform.

Bug reproduced in x86 platform:
Version-Release number of selected component (if applicable):
Host:
kernel: 3.10.0-632.el7.x86_64
qemu-kvm-rhev-2.8.0-6.el7.x86_64
Guest:
3.10.0-632.el7.x86_64

Steps to Reproduce:
The same with bug reported(by Peter)

Actual results:
The same with bug reported (After migration finish, keyboard stops working on VM2, and all ioapic interrupts are lost on VM2) 

======================Bug verify in x86 platform======================
Bug is verified in following version:
Host:
kernel： 3.10.0-663.el7.x86_64
qemu-kvm-rhev-2.9.0-3.el7.x86_64
Guest:
3.10.0-663.el7.x86_64

steps:
the same as bug reproduced.

Actual results:
Migration successed and the VM2 runs well
In dst HMP:
(qemu) info status
VM status: running
In destination VM2, keyboard works well

So, this bug is fixed.
Comment 5 errata-xmlrpc 2017-08-01 23:42:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 6 errata-xmlrpc 2017-08-02 01:19:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 7 errata-xmlrpc 2017-08-02 02:11:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 8 errata-xmlrpc 2017-08-02 02:52:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Comment 9 errata-xmlrpc 2017-08-02 03:17:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2392
Note You need to log in before you can comment on or make changes to this bug.