qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Hanna Reitz <hreitz@redhat.com>,
	qemu-block@nongnu.org
Cc: Eric Blake <eblake@redhat.com>,
	Philippe Mathieu-Daude <philmd@linaro.org>
Subject: Re: [PATCH v4 0/2] vpc: Read images exported from Azure correctly
Date: Wed, 08 Jan 2025 17:03:28 +0100	[thread overview]
Message-ID: <87cygxb8dr.fsf@redhat.com> (raw)
In-Reply-To: <20241212134504.1983757-1-vkuznets@redhat.com>

Vitaly Kuznetsov <vkuznets@redhat.com> writes:

> Changes since v3:
> - Split the change into two patches [Philippe Mathieu-Daude].
>
> It was found that 'qemu-nbd' is not able to work with some disk images
> exported from Azure as it uses a currently unknown 'wa\0\0' 'creator app'
> signature. QEMU currently supports two methods for determining the image
> size: CHS and 'current_size' and the list of known 'creator app's is used
> to decide between the two. Invert the logic in QEMU and make 'current_size'
> the default as it seems that VPC and old QEMU are the only two legacy apps
> where preferring CHS makes sense.
>
> Vitaly Kuznetsov (2):
>   vpc: Split off vpc_ignore_current_size() helper
>   vpc: Read images exported from Azure correctly

Ping?

-- 
Vitaly



  parent reply	other threads:[~2025-01-08 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 13:45 [PATCH v4 0/2] vpc: Read images exported from Azure correctly Vitaly Kuznetsov
2024-12-12 13:45 ` [PATCH v4 1/2] vpc: Split off vpc_ignore_current_size() helper Vitaly Kuznetsov
2024-12-12 14:13   ` Philippe Mathieu-Daudé
2024-12-12 13:45 ` [PATCH v4 2/2] vpc: Read images exported from Azure correctly Vitaly Kuznetsov
2025-01-08 16:03 ` Vitaly Kuznetsov [this message]
2025-01-16 14:03 ` [PATCH v4 0/2] " Kevin Wolf

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=87cygxb8dr.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --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).