[Qemu-devel] [Bug 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu

2018-08-30 Thread Stefan Bader 
Since we no longer produce i386 images, this would be hard to reproduce.
I could imagine the issue still exists but nobody is or will care.
Essentially a difference of what features are reported via cpuid and
what actually is implemented in the cpu emulation. Will close at least
the Ubuntu side.

** Changed in: llvm-toolchain-3.6 (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1448985

Title:
  llvmpipe i386 crashes when running on qemu64 cpu

Status in QEMU:
  Incomplete
Status in llvm-toolchain-3.6 package in Ubuntu:
  Won't Fix
Status in qemu package in Ubuntu:
  Won't Fix

Bug description:
  STEPS TO REPRODUCE:
     1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all 
updates (it is a host system).
     2. Download one (or all) isos:
    * Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = 
a8a14f1f92c1ef35dae4966a2ae1a264).
    * Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM = 
4a3c4b8421af51c29c84fb6f4b3fe109)
    * Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM = 
6ea04093b767ad6778aa245d53625612)
     3. Boot one (or all) isos with as QEMU-KVM guest with the following 
commands:
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
    *  or from usb-creator-gtk via "Test disk" button
     4. Click on "Try Ubuntu"

  EXPECTED RESULTS:
  ISO is booted to Unity desktop, user can test and use it.

  ACTUAL RESULTS:
     In 14.04 and 14.10 guests can see empty purple desktop or purple desktop 
with two shortcuts ("Examples" and "Install Ubuntu ...").
     15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).

  The reason for this is that unity requires gfx acceleration which is
  done via llvmpipe on non accelerated gfx chipsets (as VMs use by
  default). The error message is hidden away but is:

  LLVM ERROR: Do not know how to split the result of this operator!

  The cause is that KVM VMs by default use the qemu64 cpu model which
  seems to be inconsistent in some way between claimed features and
  actual results when using those features. A work-around for running
  i386 isos is to use a cpu model like core2duo or kvm64.

  This bug should be confirmed and fixed.
  Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1448985/+subscriptions

[Qemu-devel] [Bug 1323758] Re: Mouse stops working when connected usb-storage-device

2015-10-21 Thread Stefan Bader 
** Changed in: qemu (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758

Title:
  Mouse stops working when connected usb-storage-device

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  I'm running a guest that has Windows 8 Pro (x64) installed. Every time
  I pass through a usb storage device from the host to the guest, the
  mouse stops working in the vnc client. When I remove the usb-device
  the mouse works again.

  The mouse only stops working when I pass through a usb storage device
  and then make the vlc viewer (client) inactive by clicking on another
  program on the local computer (where I'm running the vnc viewer
  (client)). As long as I keep the vnc viewer active, the mouse works
  without any problems. But as soon as I make the vnc viewer inactive
  and then active again, the mouse will no longer work. I have to reboot
  the guest or remove the usb storage device.

  I can't find any related problems on the internet, so it may be just
  me?

  I hope someone can help me with this.

  EDIT: I posted the extra/new information in comments. But as I know
  see it might be wrong and maybe I should've posted them in this bug
  description container (by editing)? Please tell me if I did it wrong
  and I will change it. Sorry for this misunderstanding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1323758/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-13 Thread Stefan Bader 
@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 into the cloud-archive after it landed in the Trusty/Vivid
main archive.

** Changed in: qemu (Ubuntu Precise)
   Status: New => Invalid

-- 
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 qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Precise:
  Invalid
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-13 Thread Stefan Bader 
** 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) => Stefan Bader (smb)

** Changed in: qemu (Ubuntu)
     Assignee: Stefan Bader (smb) => (unassigned)

** Changed in: qemu (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: qemu (Ubuntu Vivid)
   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:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Precise:
  Invalid
Status in qemu source package in Trusty:
  In Progress
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  In Progress

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-12 Thread 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 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 qemu package in Ubuntu:
  Fix Committed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-12 Thread Stefan Bader 
@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 would also match the qemu version 2.0 which you mentioned.

-- 
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 qemu package in Ubuntu:
  Fix Committed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-09 Thread Stefan Bader 
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
package(s).

-- 
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 qemu package in Ubuntu:
  Fix Committed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-10-09 Thread Stefan Bader 
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.
https://bugs.launchpad.net/bugs/1465935

Title:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Fix Committed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  Won't Fix
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1336801] Re: 12.04 guest hangs on a 14.04 host server with cirrus graphics

2015-09-23 Thread Stefan Bader 
The errors about the frame buffer device happen because grub is started in 
graphical mode and then the boot wants to replace the framebuffer device/driver 
while plymouth still holds it. I thought we should have fixed this before 
release by adding cirrus to the list of graphics that should get initialized 
late. So are people still having this issue with the latest updates?
A work around if this really still happens is to change /etc/default/grub and 
uncomment the console mode. Not ultimately nice but should be working.

** Changed in: qemu (Ubuntu)
   Status: Triaged => 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/1336801

Title:
  12.04 guest hangs on a 14.04 host  server with cirrus graphics

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  A new 12.04.4 server guest installation hangs on a 14.04 server host
  machine.

  I did the following:

  Created a new Virtual Machine with the Ubuntu 12.04 template using 
virt-manager
  Ran through the installation without a hitch to install a LAMP+SSH server. 
All standard options apart from that.
  On reboot the 12.04 guest started but then hung after doing fsck step.
  Trying different options (change disk driver, etc) made it progress a couple 
more steps but still hung.

  The thing that fixed it in the end was to switch to a VGA display
  driver, away from the default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1336801/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-08-12 Thread Stefan Bader 
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:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Incomplete
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  New
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu

2015-08-12 Thread Stefan Bader 
Since a simple work-around exists I think the importance can be lowered.

** Summary changed:

- Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from 
QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
+ llvmpipe i386 crashes when running on qemu64 cpu

** Description changed:

  STEPS TO REPRODUCE:
     1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all 
updates (it is a host system).
     2. Download one (or all) isos:
    * Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = 
a8a14f1f92c1ef35dae4966a2ae1a264).
    * Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM = 
4a3c4b8421af51c29c84fb6f4b3fe109)
    * Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM = 
6ea04093b767ad6778aa245d53625612)
     3. Boot one (or all) isos with as QEMU-KVM guest with the following 
commands:
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
    *  or from usb-creator-gtk via Test disk button
     4. Click on Try Ubuntu
  
  EXPECTED RESULTS:
  ISO is booted to Unity desktop, user can test and use it.
  
  ACTUAL RESULTS:
     In 14.04 and 14.10 guests can see empty purple desktop or purple desktop 
with two shortcuts (Examples and Install Ubuntu ...).
     15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).
  
+ The reason for this is that unity requires gfx acceleration which is
+ done via llvmpipe on non accelerated gfx chipsets (as VMs use by
+ default). The error message is hidden away but is:
+ 
+ LLVM ERROR: Do not know how to split the result of this operator!
+ 
+ The cause is that KVM VMs by default use the qemu64 cpu model which
+ seems to be inconsistent in some way between claimed features and actual
+ results when using those features. A work-around for running i386 isos
+ is to use a cpu model like core2duo or kvm64.
+ 
  This bug should be confirmed and fixed.
  Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.

** Also affects: llvm-toolchain-3.6 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qemu (Ubuntu)
   Importance: High = Medium

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1448985

Title:
  llvmpipe i386 crashes when running on qemu64 cpu

Status in QEMU:
  New
Status in llvm-toolchain-3.6 package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE:
     1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all 
updates (it is a host system).
     2. Download one (or all) isos:
    * Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = 
a8a14f1f92c1ef35dae4966a2ae1a264).
    * Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM = 
4a3c4b8421af51c29c84fb6f4b3fe109)
    * Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM = 
6ea04093b767ad6778aa245d53625612)
     3. Boot one (or all) isos with as QEMU-KVM guest with the following 
commands:
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
    * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
    *  or from usb-creator-gtk via Test disk button
     4. Click on Try Ubuntu

  EXPECTED RESULTS:
  ISO is booted to Unity desktop, user can test and use it.

  ACTUAL RESULTS:
     In 14.04 and 14.10 guests can see empty purple desktop or purple desktop 
with two shortcuts (Examples and Install Ubuntu ...).
     15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).

  The reason for this is that unity requires gfx acceleration which is
  done via llvmpipe on non accelerated gfx chipsets (as VMs use by
  default). The error message is hidden away but is:

  LLVM ERROR: Do not know how to split the result of this operator!

  The cause is that KVM VMs by default use the qemu64 cpu model which
  seems to be inconsistent in some way between claimed features and
  actual results when using those features. A work-around for running
  i386 isos is to use a cpu model like core2duo or kvm64.

  This bug should be confirmed and fixed.
  Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1448985/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-07-17 Thread Stefan Bader 
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 happened.
So it would be up to you to confirm that with a current 14.04 host you still 
can trigger the bug and with the patched version of qemu from 
http://people.canonical.com/~smb/lp1465935/ it would be gone. Thanks.

-- 
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 qemu package in Ubuntu:
  Confirmed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  New
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

2015-07-16 Thread Stefan Bader 
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 releases and the current
development release (Wily/15.10). I would start there with
reproduction/verification and work backwards from there.

-- 
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 qemu package in Ubuntu:
  Confirmed
Status in qemu source package in Precise:
  New
Status in qemu source package in Trusty:
  New
Status in qemu source package in Utopic:
  New
Status in qemu source package in Vivid:
  New

Bug description:
  Several my QEMU instances crashed, and in the  qemu log, I can see
  this assertion failure,

 qemu-system-x86_64: /build/buildd/qemu-2.0.0+dfsg/kvm-all.c:984:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed.

  The QEMU version is 2.0.0, HV OS is ubuntu 12.04, kernel 3.2.0-38.
  Guest OS is RHEL 6.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+subscriptions

[Qemu-devel] [Bug 897750] Re: libvirt/kvm problem with disk attach/detach/reattach on running virt

2015-01-27 Thread Stefan Bader 
Serge, Scott, somehow I think we all left here in a confused state and I
do not think we still have the problem (at least not Trusty). From my
last comment it seems I did not even find something that I could change
for Precise. For now I would unassign myself and maybe this report
should be closed if Justin has no objections.

** Changed in: qemu-kvm (Ubuntu)
 Assignee: Stefan Bader (smb) = (unassigned)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/897750

Title:
  libvirt/kvm problem with disk attach/detach/reattach on running virt

Status in QEMU:
  New
Status in qemu-kvm package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 11.10 (Oneiric)
  libvirt-bin:  0.9.2-4ubuntu15.1
  qemu-kvm:   0.14.1+noroms-0ubuntu6

  Summary:With a running KVM virt,   performing an 'attach-disk',  then a 
'detach-disk', then another 'attach-disk' 
  in an attempt to reattach the volume at the same point on the virt, fails, 
with the qemu reporting back to
  libvirt a 'Duplicate ID' error.

  Expected behavior:   The 2nd invocation of 'attach-disk' should have succeeded
  Actual behavior: Duplicate ID error reported

  
  I believe this is most likely a qemu-kvm issue, as the DOM  kvm spits back at 
libvirt after the 'detach-disk'
  does not show the just-detached disk.   There is some kind of registry/lookup 
for devices in qemu-kvm
  and for whatever reason, the entry for the disk does not get removed when it 
is detached from the
  virt.   Specifically, the error gets reported at the 2nd attach-disk attempt 
from:

qemu-option.c:qemu_opts_create:697

  684 QemuOpts *qemu_opts_create(QemuOptsList *list, const char *id, int 
fail_if_exists)  
  685 { 
  
  686 QemuOpts *opts = NULL;
  
  687   
  
  688 if (id) { 
  
  689 if (!id_wellformed(id)) { 
  
  690 qerror_report(QERR_INVALID_PARAMETER_VALUE, id, an 
identifier); 
  691 error_printf_unless_qmp(Identifiers consist of letters, 
digits, '-', '.', '_', starting with a letter.\n);
  692 return NULL;  
  
  693 } 
  
  694 opts = qemu_opts_find(list, id);  
  
  695 if (opts != NULL) {   
  
  696 if (fail_if_exists) { 
  
  697 qerror_report(QERR_DUPLICATE_ID, id, list-name); 
   == HERE ===  

  698 return NULL;  
  
  699 } else {  
  
  700 return opts;  
  
  701 } 
  
  702 } 
  
  703 } 
  
  704 opts = qemu_mallocz(sizeof(*opts));   
  
  705 if (id) { 
  
  706 opts-id = qemu_strdup(id);   
  
  707

[Qemu-devel] [Bug 897750] Re: libvirt/kvm problem with disk attach/detach/reattach on running virt

2012-07-30 Thread Stefan Bader 
I am quite confused. Looking at my Precise system, pci-hotplug is built-
in, and the configs for Oneiric and Quantal are the same. Could you tell
me the exact kernel version for which you see this as a module?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/897750

Title:
  libvirt/kvm problem with disk attach/detach/reattach on running virt

Status in QEMU:
  New
Status in “qemu-kvm” package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 11.10 (Oneiric)
  libvirt-bin:  0.9.2-4ubuntu15.1
  qemu-kvm:   0.14.1+noroms-0ubuntu6

  Summary:With a running KVM virt,   performing an 'attach-disk',  then a 
'detach-disk', then another 'attach-disk' 
  in an attempt to reattach the volume at the same point on the virt, fails, 
with the qemu reporting back to
  libvirt a 'Duplicate ID' error.

  Expected behavior:   The 2nd invocation of 'attach-disk' should have succeeded
  Actual behavior: Duplicate ID error reported

  
  I believe this is most likely a qemu-kvm issue, as the DOM  kvm spits back at 
libvirt after the 'detach-disk'
  does not show the just-detached disk.   There is some kind of registry/lookup 
for devices in qemu-kvm
  and for whatever reason, the entry for the disk does not get removed when it 
is detached from the
  virt.   Specifically, the error gets reported at the 2nd attach-disk attempt 
from:

qemu-option.c:qemu_opts_create:697

  684 QemuOpts *qemu_opts_create(QemuOptsList *list, const char *id, int 
fail_if_exists)  
  685 { 
  
  686 QemuOpts *opts = NULL;
  
  687   
  
  688 if (id) { 
  
  689 if (!id_wellformed(id)) { 
  
  690 qerror_report(QERR_INVALID_PARAMETER_VALUE, id, an 
identifier); 
  691 error_printf_unless_qmp(Identifiers consist of letters, 
digits, '-', '.', '_', starting with a letter.\n);
  692 return NULL;  
  
  693 } 
  
  694 opts = qemu_opts_find(list, id);  
  
  695 if (opts != NULL) {   
  
  696 if (fail_if_exists) { 
  
  697 qerror_report(QERR_DUPLICATE_ID, id, list-name); 
   == HERE ===  

  698 return NULL;  
  
  699 } else {  
  
  700 return opts;  
  
  701 } 
  
  702 } 
  
  703 } 
  
  704 opts = qemu_mallocz(sizeof(*opts));   
  
  705 if (id) { 
  
  706 opts-id = qemu_strdup(id);   
  
  707 } 
  
  708 opts-list = list;