This bug was fixed in the package qemu - 1:2.2+dfsg-5expubuntu9.6
---
qemu (1:2.2+dfsg-5expubuntu9.6) vivid; urgency=low
* debian/patches/upstream-fix-irq-route-entries.patch
Fix "kvm_irqchip_commit_routes: Assertion 'ret == 0' failed"
(LP: #1465935)
-- Stefan Bader
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.20
---
qemu (2.0.0+dfsg-2ubuntu1.20) trusty; urgency=low
* debian/patches/upstream-fix-irq-route-entries.patch
Fix "kvm_irqchip_commit_routes: Assertion 'ret == 0' failed"
(LP: #1465935)
-- Stefan Bader
Fixed in QEMU 2.4.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
@chengyuanli
could you please verify this?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Status in QEMU:
New
Status in
This package is causing a regression in lp:qa-regression-testing's
scripts/test-qemu.py.
I'm running the testcase one more time (after having verified that the
current package did not suffer the same failure), then I'm going to mark this
verification-failed.
--
You received this bug
Hm, a second run did not reproduce the error. If I can't get it to
happen again in a few hours of re-trying, I'll assume it was a fluke or
related to the host.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I could not reproduce the original issue, but the new qemu packages
appear to be regression-free, so marked this verification-done on that
grounds. If the SRU team prefers to kick this package I'm ok with that
as well.
** Tags removed: verification-needed
** Tags added: verification-done
--
** Changed in: qemu (Ubuntu Utopic)
Importance: Undecided => High
** Changed in: qemu (Ubuntu Precise)
Importance: Undecided => High
** No longer affects: qemu (Ubuntu Precise)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Hello Li, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.20 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@Li Chengyuan, thank you for the clarification. So just formally I will
mark the Precise task of this report as invalid (since the qemu in
Precise is actually a different source package and also not affected as
far as I can tell). I will need to figure out how to ensure this fix is
also pulled
** Changed in: qemu (Ubuntu Vivid)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: qemu (Ubuntu Vivid)
Assignee: (unassigned) =>
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu9
---
qemu (1:2.3+dfsg-5ubuntu9) wily; urgency=low
* debian/patches/upstream-fix-irq-route-entries.patch
Fix "kvm_irqchip_commit_routes: Assertion 'ret == 0' failed"
(LP: #1465935)
-- Stefan Bader
Just saw kernel version 3.2 mentioned. So this seems to be a mix of
older base OS (Precise) and a more recent qemu (maybe from Trusty). I am
trying to clarify how far this needs to be backported. So I think the
original qemu version in Precise is unaffected.
--
You received this bug notification
@Li Chengyuan, is your host OS really 12.04 (aka Precise)? Because in
12.04 the qemu version is 1.0 and the fix would not apply. I am not sure
that old qemu is even affected since the code is very different.
Backports of the fix seem only to make sense up (or back) to 14.04 (aka
Trusty) which
@Stefan Bader,
The host OS is ubuntu 12.04, and we upgraded the QEMU to 2.0.0 from ubuntu
cloud-archive repo.
https://wiki.ubuntu.com/ServerTeam/CloudArchive
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
SRU Justification:
Impact: Moving around interrupt handling on SMP (like irqbalance does)
in qemu instances can cause the qemu guest to crash due to an internal
accounting mismatch.
Fix: Backported patch from upstream qemu
Testcase: See above. Verified for Trusty with provided test qemu
Bader,
We don't see this problem after the patch is applied. I think we can
close this case.
Regards,
CY.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes:
Utopic is out of support now.
** Changed in: qemu (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: qemu (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Marking as incomplete while waiting for test feedback.
** Changed in: qemu (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
Bader,
Sorry to response late.
We patch our QEMU 2.0 and running on ubuntu 12.04, and shall keep it running
for a while.
I'll let you know if this problem is gone after weeks.
Regards,
CY.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Unfortunately I seem to be unable to get this bug triggered with the
reproducer. It could be a detail of the guest setup I am missing. Since I do
not have access to RHEL I used CentOS 6.3 in a 8core guest with 2 virtio disks.
Host was 14.04. Left the script running for quite a bit but no crash
The proposed fix seems not yet part of any qemu release but applied as
commit bdf026317daa3b9dfa281f29e96fbb6fd48394c8
Author: 马文霜 kevin...@tencent.com
Date: Wed Jul 1 15:41:41 2015 +0200
Fix irq route entries exceeding KVM_MAX_IRQ_ROUTES
to v2.4.0-rc0. So this would affect all current
** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Trusty)
-Original Message-
From: Paolo Bonzini [mailto:pbonz...@redhat.com]
Sent: 2015年7月1日 21:39
To: Li, Chengyuan
Cc: kevin...@tencent.com
Subject: Re: [Qemu-devel] [PATCH] Fix irq route entries exceed
KVM_MAX_IRQ_ROUTES
On 30/06/2015 05:47, Li, Chengyuan wrote:
Here is my understanding,
** Changed in: qemu (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
From kvm_pc_setup_irq_routing() function, we can see that 15 routes from
PIC and 23 routes from IOAPIC are added into irq route table, but only
23 irq(gsi) are reserved. This leads to irq route table has been full
but there are still tens of free gsi. So the retry part of
kvm_irqchip_get_virq()
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1465935
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
Have you be able to reproduce this issue on a wily host? What about a
different guest? Or is only RHEL6.3 affected?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
It appears that the latest version of the patch is here:
http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg00822.html
However, this hasn't yet be accepted upstream. The most recent
discussion requires the submitter to respond to the maintainers
questions here:
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Ryan,
Our Hypervisors are running in the internal network which can't access to
Launchpad,
# apport-collect 1465935
ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out
We saw this qemu crash on 18 Hypervisor nodes. So far all our
hypervisors are ubuntu 12.04,
http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg00822.html
Seems that the latest version code has answered maintainers questions.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1465935
The problem can be re-produced by the script in the below in link.
http://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg03739.html
i.e.
vda_irq_num=25
vdb_irq_num=27
while [ 1 ]
do
for irq in {1,2,4,8,10,20,40,80}
do
echo $irq /proc/irq/$vda_irq_num/smp_affinity
http://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg03739.html
Seems that this patch hasn't been accpeted yet, and also no comments for
it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
From the debug log, we can see that virq is only 1008, but irq route table has
been full, i.e. 1024.
In kvm_irqchip_get_virq(), it only calls kvm_flush_dynamic_msi_routes() when
all virqs(total gsi_count, 1024 too) have been allocated, but irq route table
has two kind of entry type,
35 matches
Mail list logo
