qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <1808928@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1808928] Re: Bitmap Extra data is not supported
Date: Tue, 20 Apr 2021 17:21:15 -0000	[thread overview]
Message-ID: <161893927567.9885.16114792454231177468.malone@wampee.canonical.com> (raw)
In-Reply-To: 154511858636.8591.3431958243733477284.malonedeb@gac.canonical.com

Sorry, that formatted *terribly*... please see the attachment for a raw
text version with arbitrarily long columns that looks nicer. :(

** Attachment added: "Raw text for comment #7 with better formatting (?)"
   https://bugs.launchpad.net/qemu/+bug/1808928/+attachment/5490362/+files/bztemp

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

Title:
  Bitmap Extra data is not supported

Status in QEMU:
  Incomplete

Bug description:
  i am using dirty bitmaps and drive-backup. It works as aspected.

  Lately, i encounter a disastrous error. There is not any information
  about that situation. I cannot reach/open/attach/info or anything with
  a qcow2 file.

  virsh version
  Compiled against library: libvirt 4.10.0
  Using library: libvirt 4.10.0
  Using API: QEMU 4.10.0
  Running hypervisor: QEMU 2.12.0

  "qemu-img: Could not open '/var/lib/libvirt/images/test.qcow2': Bitmap
  extra data is not supported"

  what is that mean? what should i do?
  i cannot remove bitmap. i cannot open image or query.

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


  parent reply	other threads:[~2021-04-20 17:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  7:36 [Qemu-devel] [Bug 1808928] [NEW] Bitmap Extra data is not supported Ali Sag
2019-02-12  1:16 ` [Qemu-devel] [Bug 1808928] " John Snow
2019-02-12 12:49 ` Ali Sag
2019-02-18 19:56 ` John Snow
2019-02-19 10:56 ` Ali Sag
2019-12-23 20:45 ` John Snow
2021-04-20  7:56 ` Thomas Huth
2021-04-20 17:17 ` John Snow
2021-04-20 17:21 ` John Snow [this message]
2021-04-30 17:02 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161893927567.9885.16114792454231177468.malone@wampee.canonical.com \
    --to=1808928@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).