Re: [Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

You might ask on #virt for the opinion there, but I don't believe migrating backward is supported in any case. t->x->t doesn't change the fact that there is x->t. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

Re: [Qemu-devel] [Bug 1536487] Re: Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1

Migrating a VM from xenial -> trusty (or anything moving backward) is not supported. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1536487 Title: Unable to migrate pc-i440fx-2.4 KVM guest from

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Awesome- thanks for verifying ** Tags removed: verification-needed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump Status in QEMU:

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

No, I'm afraid not. But if you can test when this package is accepted into trusty-proposed that'll be great. ** Description changed: + = + SRU Justification: + 1. Impact: guests hang after live migration with 100% cpu + 2. Upstream fix: a set of four patches

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Conflicting experimental packages in that ppa, trying ubuntu-virt/ppa instead. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump Status

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Thank you. I'm doing a test build in ppa:serge-hallyn/virt, and will run a full regression test from there. I'll push for SRU if that passes. Would you mind putting in the bug Description (at top) a concise summary of the test case, for the SRU process? -- You received this bug notification

[Qemu-devel] [Bug 1490611] Re: Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to the result file, which Microsoft Azure rejects as invalid

** 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/1490611 Title: Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra

[Qemu-devel] [Bug 1490611] Re: Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to the result file, which Microsoft Azure rejects as invalid

** Also affects: qemu (Ubuntu Xenial) 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/1490611 Title: Using qemu >=2.2.1 to convert raw->VHD (fixed) adds

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

See https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1297218/+attachment/4301780/+files/backport.patch referenced in comment #29 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title:

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

@Steve, it seems to me those are the same as the 'backport.patch' from an earlier comment? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc

[Qemu-devel] [Bug 1585008] Re: Windows 7 guests hang on bootup when qxl video is used

*** This bug is a duplicate of bug 1591724 *** https://bugs.launchpad.net/bugs/1591724 Thanks - so it's fixed upstream and in ubuntu yakkety. I'll mark it as a dup of bug 1591724. ** Changed in: qemu (Ubuntu) Status: Confirmed => Fix Released ** This bug has been marked a duplicate

[Qemu-devel] [Bug 1585008] Re: Windows 7 guests hang on bootup when qxl video is used

Thanks. ** Also affects: qemu 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/1585008 Title: Windows 7 guests hang on bootup when qxl video is used

[Qemu-devel] [Bug 1589923] Re: https websockets not working in 2.5 or 2.6

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

Re: [Qemu-devel] [Bug 1583775] [NEW] Feature Request: qemu 2.6.0

I'm testing a merge of it right now. On Thu, May 19, 2016 at 9:13 PM, Launchpad Bug Tracker <1583...@bugs.launchpad.net> wrote: > You have been subscribed to a public bug: > > Qemu 2.6.0 just got released, and according to changelogs it has quite > some enhancements... > > would it be possible to

Re: [Qemu-devel] [Bug 1581334] [NEW] qemu + librbd takes high %sy cpu under high random io workload

affects ceph ** Also affects: ceph 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/1581334 Title: qemu + librbd takes high %sy cpu under high random io

Re: [Qemu-devel] [Bug 1581334] [NEW] qemu + librbd takes high %sy cpu under high random io workload

affects linux ** Also affects: linux 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/1581334 Title: qemu + librbd takes high %sy cpu under high random

[Qemu-devel] [Bug 1525676] Re: qemu runas and sandbox option incompatible, process will hang in futex after setgid

** Also affects: qemu Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Triaged ** Changed in: qemu (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

Re: [Qemu-devel] [PATCH] Whitelist sysinfo call

Quoting mreza...@redhat.com (mreza...@redhat.com): > From: Miroslav Rezanina > > Newer version of nss-softokn libraries (> 3.16.2.3) use sysinfo call > so qemu using rbd image hang after start when run in sandbox mode. > > To allow using rbd images in sandbox mode we have

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

@leftyfb - what exactly is IBM asking to verify? Whether kvm works under powervm? Did smoser's info help? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Ok so if I'm following this right there are two issues: 1. the bug reporter is using a powervm partition. KVM cannot be used there. This is not a KVM bug. 2. the xenial cloud images have an outdated 4.2 kernel which doesn't boot in kvm on powernv. A workaround is to use the isos which do

[Qemu-devel] [Bug 1563152] Re: general protection fault running VirtualBox in KVM guest

** Changed in: qemu (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563152 Title: general protection fault running VirtualBox in KVM guest Status in QEMU:

Re: [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

If you can reproduce this with the ppc64 xenial iso or a rootfs installed from that, using 4.4 kernel, please let us know. Otherwise, I think the fix will be for cloud images to be updated with a 4.4 kernel. -- You received this bug notification because you are a member of qemu- devel-ml, which

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

4.4.0-16 also works. ** Also affects: livecd-rootfs (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/1563887 Title: qemu-system-ppc64 freezes on

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Actually the clou dimages have a 4.2 kernel. When I use a xenial beta2 iso which has 4.4.0-15-generic #31, it boots fine. I can install, and I can boot the installed image (with same kernel) just fine. -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Result of doing qemu-system-ppc64 -m 1024 -vnc :1 -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=my-seed.img,if=virtio ** Attachment added: "crash.png"

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Hm - I can boot a wily cloud image, just not a xenial one. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

** Changed in: qemu (Ubuntu) Status: New => 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/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU:

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Hi, I've redeployed my test box with 14.04 with kilo-staging archive, but i get a core dump when i try to run kvm the same way you did. Can you show your /etc/apt/sources.list and /etc/apt/sources.list.d, as well as output for uname -a dpkg -l | egrep -e '(qemu|linux|bios)' -- You received

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Indeed building the kilo package from source gives me the same hang. So something else (seabios maybe) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

I'll try building the package source from kilo on the xenial host and see if that succeeds. I'm having doubts. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Hm, building 2.2.0 (close to what is in the kilo cloud archive) doesn't help. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le

Re: [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Thanks very much for testing. I think I have a system I can use to try and bisect tonight/tomorrow. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on

[Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

Failing any brighter ideas, this should be pretty bisectable to figure out what happened. Hardware availability is the main problem. Would you be able to use your system to bisect to the commit introducing the bug? Actually before we get to that, could you try installing the 14.04 slof package

[Qemu-devel] [Bug 1006655] Re: Can't convert to vmdk with the streamOptimized subformat

I'm confused- this is marked as affecting qemu-kvm in precise, but the preceding patch (c6ac36e) which introduced the bug is not there either. So I'm going to mark this as not affecting precise unless someone speaks up to say that we in fact need the whole dependent series. ** Changed in:

[Qemu-devel] [Bug 1562653] Re: Ubuntu 15.10: QEMU VM hang if memory >= 1T

Hi, just to be sure, if you run kvm -vnc :1 -m 1.5G kvm -vnc :1 -m 1.5G --no-hpet do those also crash? Can you please show the contents of /var/log/libvirt/qemu/u1510-1.log ** Package changed: kvm (Ubuntu) => qemu (Ubuntu) ** Also affects: qemu Importance: Undecided Status: New

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

But unfortunately we do not know which patch fixed it, making an SRU much more problematic. Someone who is able to reproduce the bug would need to try to either bisect, or make educated guesses and test patch cherrypicks. -- You received this bug notification because you are a member of qemu-

[Qemu-devel] [Bug 1546445] Re: support vhost user without specifying vhostforce

** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Changed in: qemu Status: In Progress => 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/1546445 Title: support

[Qemu-devel] [Bug 1308341] Re: Multiple CPUs causes blue screen on Windows guest (14.04 regression)

*** This bug is a duplicate of bug 1346917 *** https://bugs.launchpad.net/bugs/1346917 Hi, could you please file a new bug with debugging information as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/comments/11 ? -- You received this bug notification because you are a

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Thanks - marked fixed released for development release. We can SRU this into trusty if we know exactly which patch actualy fixed it. ** Changed in: qemu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1465935] Re: 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

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

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

[Qemu-devel] [Bug 1516203] Re: qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()

Do other iso's, like http://archive.ubuntu.com/ubuntu/dists/wily/main /installer-amd64/current/images/netboot/mini.iso also cause this for you? (I ran with upstream qemu GIT HEAD using that iso and was unable to reproduce) -- You received this bug notification because you are a member of qemu-

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

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.

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

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 --

[Qemu-devel] [Bug 1516203] Re: qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()

Could you please give the full command you used so that I can reproduce this? ** Also affects: qemu 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/1516203

[Qemu-devel] [Bug 1516203] Re: qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()

Thanks. (I thought I had upgraded my test system to xenial, but I hadn't, so virtio-vga was not supported) How far into the boot do you see this happening? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1516203] Re: qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy()

(Note I cannot reproduce this here) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1516203 Title: qemu-system-x86_64 crashed with SIGSEGV in SDL_BlitCopy() Status in QEMU: New Status in qemu

[Qemu-devel] [Bug 1350435] Re: tcg.c:1693: tcg fatal error

Ah, thanks for setting me straight. ** Changed in: qemu (Ubuntu) Status: Invalid => 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/1350435 Title: tcg.c:1693: tcg fatal error

[Qemu-devel] [Bug 1350435] Re: tcg.c:1693: tcg fatal error

This patch is still not applied upstream. As there has been no discussion in over a year, I assume it is no longer a problem and I'm going to mark it invalid. Please rep;ly if that is not the case. If it *is* still a problem, then we should go discuss on oftc#qemu. ** Changed in: qemu

[Qemu-devel] [Bug 1463172] Re: destination arm board hangs after migration from x86 source

Hi, would it be possible to run the emulator on arm under gdb (with debugging symbols intalled), do the incoming migration, and then when it hangs, show a backtrace from gdb? ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a

[Qemu-devel] [Bug 1042388] Re: qemu: Unsupported syscall: 257 (timer_create)

@erikd, can you check whether this has been fixed in wily? ** Changed in: qemu (Ubuntu) Status: Triaged => 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/1042388 Title: qemu:

[Qemu-devel] [Bug 1486278] Re: 'info vnc' monitor command does not show websocket information

** Changed in: qemu (Ubuntu) Status: New => Confirmed ** Also affects: qemu 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/1486278 Title: 'info

[Qemu-devel] [Bug 1497479] Re: memory corruption with migrate/savevm in TCG mode

Hi, is this a duplicate of 1493049? (Should they be merged?) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1497479 Title: memory corruption with migrate/savevm in TCG mode Status in QEMU: New

Re: [Qemu-devel] [Bug 1497479] Re: memory corruption with migrate/savevm in TCG mode

Generally combining them is still better - but if it helps you to keep things straight then no problem, sorry for the noise - 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/1497479 Title:

[Qemu-devel] [PATCH 1/1] vl.c: don't try to insert malloc tracepoints on newer glib

/+source/qemu-kvm/+bug/1491972 (thanks danpb for the suggestion) Signed-off-by: Serge Hallyn <serge.hal...@ubuntu.com> --- vl.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/vl.c b/vl.c index 584ca88..cab9425 100644 --- a/vl.c +++ b/vl.c @@ -2719,6 +2719,7 @@ static const QEMU

[Qemu-devel] [PATCH] vl.c: don't try to insert malloc tracepoints on newer glib (v2)

-by: Serge Hallyn <serge.hal...@ubuntu.com> --- vl.c | 27 +-- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/vl.c b/vl.c index 584ca88..6a69027 100644 --- a/vl.c +++ b/vl.c @@ -2719,6 +2719,7 @@ static const QEMUOption *lookup_opt(int argc, char

[Qemu-devel] [Bug 1422307] Re: qemu-nbd corrupts files

** Changed in: qemu (Ubuntu Trusty) Importance: Medium = High ** Changed in: qemu (Ubuntu Trusty) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https

[Qemu-devel] [Bug 1422307] Re: qemu-nbd corrupts files

** Changed in: qemu (Ubuntu Trusty) Assignee: Serge Hallyn (serge-hallyn) = (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/1422307 Title: qemu-nbd corrupts files Status in QEMU

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Could someone confirm whether this is fixed in 15.04 and/or 15.10? ** 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/1297218 Title:

[Qemu-devel] [Bug 1163034] Re: linux-user mode can't handle guest setting RLIMIT_AS (hangs running gnutls28 configure check code)

This will come in when implemented upstream. ** Changed in: qemu (Ubuntu) Importance: High = Wishlist -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1163034 Title: linux-user mode can't handle

[Qemu-devel] [Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean

*** This bug is a duplicate of bug 1317603 *** https://bugs.launchpad.net/bugs/1317603 ** This bug has been marked a duplicate of bug 1317603 qemu-system-ppc does not terminate on VM exit -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1463172] Re: destination arm board hangs after migration from x86 source

I'm going to mark this invalid as I don't believe this is a supported case. If someone can vouch for the fact that this is supposed to work, please leave a comment. ** Changed in: qemu (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of qemu-

[Qemu-devel] [Bug 1321028] Re: qemu-system-ppc : file systems are not shutting down clean

** Changed in: qemu (Ubuntu) Status: Incomplete = 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/1321028 Title: qemu-system-ppc : file systems are not shutting down clean Status in

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

** Changed in: qemu (Ubuntu) Importance: Medium = Low -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/685096 Title: USB Passthrough not working for Windows 7 guest Status in QEMU: Confirmed

[Qemu-devel] [Bug 1463172] Re: destination arm board hangs after migration from x86 source

Hm, ok, thanks - sadly i don't have any board I can test this on with me. Wonder whether a rpi2 (which I have but not with me) would work. ** Changed in: qemu (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of qemu- devel-ml, which is

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

** 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:

[Qemu-devel] [Bug 1463172] Re: destination arm board hangs after migration from x86 source

Thanks for the information. I'm suspect that this sort of migration is not expected to work, but I've marked the bug as affecting upstream in case someone there can comment. ** Changed in: qemu (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a

[Qemu-devel] [Bug 1463172] Re: destination arm board hangs after migration from x86 source

To be sure I'm understanding right, are you migrating from qemu-system- arm on x86 to a native arm board? What are the exact parameters you are passing the emulator, and what exactly is the physical board? ** Changed in: qemu (Ubuntu) Status: New = Incomplete ** Also affects: qemu

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

I'm sorry, but I'm not clear at this point on the status of this bug. I never received an answer to comments #32 and comment #35, and don't know what, if anything, to apply in an SRU. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1450881] Re: qemu-system-sparc MUTEX_HELD assert and libC lock errors

** No longer affects: qemu (Ubuntu) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1450881 Title: qemu-system-sparc MUTEX_HELD assert and libC lock errors Status in QEMU: New Bug description:

[Qemu-devel] [Bug 1450881] Re: qemu-system-sparc MUTEX_HELD assert and libC lock errors

** Also affects: qemu 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/1450881 Title: qemu-system-sparc MUTEX_HELD assert and libC lock errors Status in

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

I believe this should be fixed in 15.04, as the cited patches are present. Could someone confirm? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due

[Qemu-devel] [Bug 1392504] Re: libvirt not relabeling devices on USB Passthrough

Actually I was talking about just libvirt. cmment #23 (and 24) suggests that the problem is libvirt not re-labeling the devices, so i'm wondering whether 1.2.12 fixes it. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1392504] Re: USB Passthrough is not working anymore

Has anyone tested whether this is still broken in 15.04? ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** No longer affects: libvirt (Ubuntu) ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu)

[Qemu-devel] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@ullix could you please give the precise full qemu command line which is failing, and a url to a boot cd I can use for the guest? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/918791 Title:

Re: [Qemu-devel] [Bug 1392504] Re: USB Passthrough is not working anymore

You also should be able to do aa-audit /usr/sbin/libvirtd which should put informative messages into /var/log/syslog or /var/log/audit/audit.log as well. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1392504] Re: USB Passthrough is not working anymore

I haven't seen an error like that, and cannot reproduce it here. Another way to test that apparmor is causing the problem would be to add /dev/** rw, at the bottom of the file /etc/apparmor.d/abstractions/libvirt-qemu. When you next start the vm apparmor should allow it full access to all

[Qemu-devel] [Bug 1006655] Re: Can't convert to vmdk with the streamOptimized subformat

** Also affects: qemu Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu (Ubuntu) Status: New = Confirmed -- You received this bug

[Qemu-devel] [Bug 1424237] Re: missing manpage for bridge.conf

** Also affects: qemu Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New = Confirmed ** Changed in: qemu (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

[Qemu-devel] [Bug 1392504] Re: USB Passthrough is not working anymore

@lj-keus if you turn off apparmor sudo /etc/init.d/apparmor stop sudo /etc/init.d/apparmor teardown does that fix the issue for you? (Please re-enable apparmor immediately after the test using sudo /etc/init.d/apparmor start sudo stop libvirt-bin sudo start libvirt-bin ) -- You received

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

** Changed in: qemu-kvm (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/897750 Title: libvirt/kvm problem with disk attach/detach/reattach on running

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

Hi, just to be clear, the backport.patch which you uploaded actually increased jitter for you, making the situation worse, right? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1297218 Title:

[Qemu-devel] [Bug 1318830] Re: High CPU usage on windows virtual machine

** Changed in: qemu (Ubuntu) Status: New = Invalid ** Changed in: qemu 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/1318830 Title: High CPU usage on windows

[Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling avoids using mono

** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1319100 Title:

[Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest

The file seems to be in qemu-system-common (at least in Ubuntu 14.10). The next question is how to best help the user to run the right command. Should it go into the manpage? ** Package changed: qemu-kvm (Ubuntu) = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Importance: Undecided = Medium **

[Qemu-devel] [Bug 1387881] Re: qemu fails to recognize full virtualization

** Changed in: qemu (Ubuntu) Status: New = Invalid ** Changed in: qemu Status: New = Invalid ** Changed in: virtinst (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1318830] Re: High CPU usage on windows virtual machine

** Changed in: qemu (Ubuntu) Status: Incomplete = 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/1318830 Title: High CPU usage on windows virtual machine Status in QEMU: New Status in

[Qemu-devel] [Bug 1396497] Re: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot

** Changed in: qemu (Ubuntu) Importance: Undecided = Low ** Changed in: qemu (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1396497 Title: 'qemu-img

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

It looks as though the relevant commits were re-committed to upstream git HEAD (9a48bcd1b82494671c09b0eefdb882581499 and 317b0a6d8ba44e9bf8f9c3dbd776c4536843d82c). So this may be fixed in vivid, and we might be able to cherrypick the final patches to trusty. ** Package changed: libvirt

[Qemu-devel] [Bug 1297218] Re: guest hangs after live migration due to tsc jump

@Paul, could you confirm whether qemu 1:2.2+dfsg-3exp~ubuntu1 from https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream fixes this issue? If it does then I'll go ahead and backport the patch. -- You received this bug notification because you are a member of qemu- devel-ml,

[Qemu-devel] [Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

Went ahead and tested - it is in fact fixed in the v2.2 version. ** Changed in: qemu (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

Re: [Qemu-devel] [Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

Does it also fail with the qemu from https://launchpad.net/~ubuntu-virt/+archive/ubuntu/virt-daily-upstream ? (This isn't quite git head, but it is qemu v2.2) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

Re: [Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

@Mario, the external snapshots have apparently been around a long time. The ability to create external snapshots from running vms is newer, but it appears to exist evn in qemu-kvm 1.0. So all versions in Debian and Ubuntu should support them.

[Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

Changing priority given workarounds. ** Changed in: qemu-kvm (Ubuntu) Importance: High = Low -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1025244 Title: qcow2 image increasing disk size above

Re: [Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

For the record, the workaround is deleting old snapshots in shutdown mode as per comment #14. Upstream has moved toward external snapshots as the way forward, so while I don't argue that this is a bug, it seems unlikely to receive a fix from upstream. -- You received this bug notification

[Qemu-devel] [Bug 1392504] Re: USB Passthrough is not working anymore

** Changed in: qemu (Ubuntu) Status: Incomplete = Confirmed ** Changed in: qemu (Ubuntu) Importance: Undecided = High ** Changed in: qemu (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

[Qemu-devel] [Bug 1368815] Re: qemu-img convert intermittently corrupts output images

@Michael, by any chance would you be albe to test on utopic? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1368815 Title: qemu-img convert intermittently corrupts output images Status in

[Qemu-devel] [Bug 1368815] Re: qemu-img convert intermittently corrupts output images

I couldn't reproduce the bug on the old qemu myself, however Michael has verified the (same) fix on trusty, and the full qa-regression-test passed for me on utopic-proposed. So I would request that we call this verification-done. -- You received this bug notification because you are a member of

Re: [Qemu-devel] [Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)

Excellent! Any chance you can start bisecting with http://people.canonical.com/~serge/binaries.{0..68}/{qemu-img,qemu- system-x86_64} ? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1292234 Title:

[Qemu-devel] [Bug 1396497] Re: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot

I'd agree that at least the last part - removing the oldest snapshot first - seems like a bug. ** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

  1   2   3   4   5   >