Have the same proble: qemu-img: Check failed: Cannot allocate memory
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1332297
Title:
qemu-img: crash on check of an image with large value in the
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1332297
Title:
qemu-img:
QEMU nowadays seems to report "Check failed: Cannot allocate memory" ...
so I assume that is OK and we can now close this bug?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Tue, Jun 24, 2014 at 7:36 PM, Kevin Wolf kw...@redhat.com wrote:
Am 24.06.2014 um 15:19 hat M.Kustova geschrieben:
On Mon, Jun 23, 2014 at 12:02 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Jun 19, 2014 at 07:19:55PM -, Maria Kustova wrote:
The bug description missed qemu-img
Am 25.06.2014 um 11:32 hat M.Kustova geschrieben:
On Tue, Jun 24, 2014 at 7:36 PM, Kevin Wolf kw...@redhat.com wrote:
Am 24.06.2014 um 15:19 hat M.Kustova geschrieben:
On Mon, Jun 23, 2014 at 12:02 PM, Stefan Hajnoczi stefa...@gmail.com
wrote:
On Thu, Jun 19, 2014 at 07:19:55PM -,
On Wed, Jun 25, 2014 at 1:42 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2014 um 11:32 hat M.Kustova geschrieben:
On Tue, Jun 24, 2014 at 7:36 PM, Kevin Wolf kw...@redhat.com wrote:
Am 24.06.2014 um 15:19 hat M.Kustova geschrieben:
On Mon, Jun 23, 2014 at 12:02 PM, Stefan Hajnoczi
Am 25.06.2014 um 11:54 hat M.Kustova geschrieben:
On Wed, Jun 25, 2014 at 1:42 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2014 um 11:32 hat M.Kustova geschrieben:
On Tue, Jun 24, 2014 at 7:36 PM, Kevin Wolf kw...@redhat.com wrote:
Am 24.06.2014 um 15:19 hat M.Kustova geschrieben:
On Wed, Jun 25, 2014 at 2:40 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2014 um 11:54 hat M.Kustova geschrieben:
On Wed, Jun 25, 2014 at 1:42 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2014 um 11:32 hat M.Kustova geschrieben:
On Tue, Jun 24, 2014 at 7:36 PM, Kevin Wolf
The series fixed the crash, but qemu-img started to produce the
confusing output:
$ qemu-img check test_image
ERROR: I/O error in check_refcounts_l1
No errors were found on the image.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Mon, Jun 23, 2014 at 12:02 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Jun 19, 2014 at 07:19:55PM -, Maria Kustova wrote:
The bug description missed qemu-img error:
(process:12283): GLib-ERROR **: gmem.c:110: failed to allocate
18446744059294601304 bytes
Thanks, there has
Am 24.06.2014 um 15:19 hat M.Kustova geschrieben:
On Mon, Jun 23, 2014 at 12:02 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Jun 19, 2014 at 07:19:55PM -, Maria Kustova wrote:
The bug description missed qemu-img error:
(process:12283): GLib-ERROR **: gmem.c:110: failed to
On Thu, Jun 19, 2014 at 07:19:55PM -, Maria Kustova wrote:
The bug description missed qemu-img error:
(process:12283): GLib-ERROR **: gmem.c:110: failed to allocate
18446744059294601304 bytes
Thanks, there has been recent work by Kevin Wolf to handle memory
allocation failures gracefully
The bug description missed qemu-img error:
(process:12283): GLib-ERROR **: gmem.c:110: failed to allocate
18446744059294601304 bytes
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1332297
Title:
13 matches
Mail list logo