From: Max Reitz <mreitz@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
Qemu-block <qemu-block@nongnu.org>,
qemu-devel@nongnu.org, libguestfs <libguestfs@redhat.com>
Subject: Re: [Qemu-devel] [Libguestfs] [qemu-img] support for XVA
Date: Wed, 15 Nov 2017 21:27:14 +0100 [thread overview]
Message-ID: <7b11bb2b-b93d-e8ff-f396-703c93549d0d@redhat.com> (raw)
In-Reply-To: <20171115202440.GJ19514@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On 2017-11-15 21:24, Richard W.M. Jones wrote:
> On Wed, Nov 15, 2017 at 09:07:12PM +0100, Max Reitz wrote:
>> On 2017-11-15 21:06, Gandalf Corvotempesta wrote:
>>> 2017-11-15 20:59 GMT+01:00 Max Reitz <mreitz@redhat.com>:
>>>> Well, you can't just add support to qemu-img alone either. Every image
>>>> format supported by qemu-img is one supported by qemu as a whole and
>>>> thus needs a proper block driver that needs to support random accesses
>>>> as well.
>>>
>>> I was talking about qemu-img convert, just to convert an XVA image to
>>> something different, in a single pass, without having to extract the
>>> tar.
>>
>> I know, but that doesn't work. qemu-img convert uses the normal
>> general-purpose block drivers for that.
>
> In any case there's no need as qemu/qemu-img can already access files
> inside an uncompressed tarball using the offset/size support added to
> the raw driver exactly for this purpose:
>
> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg03945.html
If that works, yes. To me it doesn't look like XVA is just a single raw
image inside of a tarball, but I may very well be wrong, of course.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-11-15 20:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 15:52 [Qemu-devel] [qemu-img] support for XVA Gandalf Corvotempesta
2017-11-15 17:33 ` Eric Blake
2017-11-15 17:44 ` Gandalf Corvotempesta
2017-11-15 19:59 ` Max Reitz
2017-11-15 20:06 ` Gandalf Corvotempesta
2017-11-15 20:07 ` Max Reitz
2017-11-15 20:24 ` [Qemu-devel] [Libguestfs] " Richard W.M. Jones
2017-11-15 20:27 ` Max Reitz [this message]
2017-11-15 20:29 ` Richard W.M. Jones
2017-11-15 20:41 ` Gandalf Corvotempesta
2017-11-15 21:05 ` Richard W.M. Jones
2017-11-15 21:15 ` Richard W.M. Jones
2017-11-15 21:30 ` Max Reitz
2017-11-15 21:42 ` Gandalf Corvotempesta
2017-11-15 21:49 ` Richard W.M. Jones
2017-11-15 21:50 ` Gandalf Corvotempesta
2017-11-15 21:50 ` Max Reitz
2017-11-15 22:28 ` Max Reitz
2017-11-15 22:47 ` Gandalf Corvotempesta
2017-11-15 22:55 ` Max Reitz
2017-11-15 22:57 ` Max Reitz
2017-11-16 10:08 ` Gandalf Corvotempesta
2017-11-16 14:02 ` Max Reitz
2017-11-20 21:48 ` Gandalf Corvotempesta
2017-11-15 21:51 ` Richard W.M. Jones
2017-11-16 10:01 ` Richard W.M. Jones
2017-11-16 10:07 ` Gandalf Corvotempesta
2017-11-16 10:11 ` Richard W.M. Jones
2017-11-16 12:56 ` Tomáš Golembiovský
2017-11-16 13:07 ` Tomáš Golembiovský
2017-11-16 13:08 ` Richard W.M. Jones
2017-11-15 19:43 ` [Qemu-devel] " Richard W.M. Jones
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=7b11bb2b-b93d-e8ff-f396-703c93549d0d@redhat.com \
--to=mreitz@redhat.com \
--cc=gandalf.corvotempesta@gmail.com \
--cc=libguestfs@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).