** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Also affects: cloud-archive/liberty
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Fix Released
** Changed in: cloud-archive/liberty
Status: New => Fix Releas
** Changed in: qemu (Ubuntu Vivid)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion hangs on large core s
** No longer affects: qemu (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion hangs on large core systems
To manage notifications
On 28/10/15 08:42, dann frazier wrote:
> Sorry for the additional post - I just noticed that @Haw was asking
> about trusty.
>
> As I recall, the issue fixed by the patch I provided was introduced in
> vivid, and was fixed before wily. In other words, only vivid should be
> impacted. I'm surprised
** Patch added: "patch from my vivid git branch"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+attachment/4507008/+files/aio-strengthen-memory-barriers-for-bottom-half-sched.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
Sorry for the additional post - I just noticed that @Haw was asking
about trusty.
As I recall, the issue fixed by the patch I provided was introduced in
vivid, and was fixed before wily. In other words, only vivid should be
impacted. I'm surprised to hear that it impacts trusty.
--
You received
@Serge: I identified the patch that fixes this - see comment #2.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion hangs on large core systems
To
I don't see where anyone has identified what patches actually fixed
this, and no obvious message in git log , so offhand I'd say chances are
slim. Could you use the cloud archive, which should have the newer
versions?
--
You received this bug notification because you are a member of Ubuntu
Serve
Any chance of having the fixes (or fixed version) backported to trusty?
We need this for the HP Moonshot hardware we're using in ScalingStack
and am currently working around it with a backport of the version in
Vivid[1]
[1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra-
workaro
** Changed in: qemu (Ubuntu Vivid)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion ha
** Changed in: qemu (Ubuntu Vivid)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion hangs on large core s
** Changed in: qemu (Ubuntu Vivid)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion ha
We can reproduce this naturally within a few hours on ppc64el with a
backport of vivid's qemu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qemu-img qcow2 conversion h
This should be fixed in 1:2.3+dfsg-4ubuntu1
** Changed in: qemu (Ubuntu Wily)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1457639
Title:
qe
Debian has been updated to 2.3 which includes the upstream fix, so
ignore my last comment. I assume wily will get a 2.3 upload soon, and
that will fix the issue there.
I have pushed a branch for vivid to git://git.launchpad.net/~dannf/qemu
(lp1457639-vivid)
--
You received this bug notification
I pushed a fix based on the debian-unstable branch to:
git://git.launchpad.net/~dannf/qemu
I haven't been able to reproduce this issue on Debian unstable so I
didn't file a Debian bug. However, as the upstream commit log describes,
easy reproduction is pretty sensitive to the environment and doe
16 matches
Mail list logo
