Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1412470 - Keyboard hang after migration with kernel-irqchip=split
Keyboard hang after migration with kernel-irqchip=split
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev (Show other bugs)
7.4
x86_64 Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Peter Xu
xianwang
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-01-12 01:25 EST by Peter Xu
Modified: 2017-08-01 23:17 EDT (History)
9 users (show)

See Also:
Fixed In Version: qemu-kvm-rhev-2.9.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 19:42:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2392 normal SHIPPED_LIVE Important: qemu-kvm-rhev security, bug fix, and enhancement update 2017-08-01 16:04:36 EDT

  None (edit)
Description Peter Xu 2017-01-12 01:25:55 EST 
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 06:09:39 EDT 
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 19:42:15 EDT 
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-01 21:19:54 EDT 
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-01 22:11:53 EDT 
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-01 22:52:40 EDT 
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-01 23:17:22 EDT 
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.
First Last Prev Next    This bug is not in your last search results.