qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, libguestfs <libguestfs@redhat.com>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [qemu-img] support for XVA
Date: Wed, 15 Nov 2017 20:59:15 +0100	[thread overview]
Message-ID: <0e6cc220-814a-17fd-4fd7-7b0665d34e81@redhat.com> (raw)
In-Reply-To: <CAJH6TXhBAaBE9gBSxksWZqNywWmencRaGyeY-oN3jbKdgUettQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 538 bytes --]

On 2017-11-15 18:44, Gandalf Corvotempesta wrote:
> XVA is a tar archive.
> I don't think would be possible to directly use the image stored inside
> without extracting and merging each chunks
> 
> Any random reads would be impossible to do, only a huge sequential dump to
> build the raw image

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.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2017-11-15 19:59 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 [this message]
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
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=0e6cc220-814a-17fd-4fd7-7b0665d34e81@redhat.com \
    --to=mreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=libguestfs@redhat.com \
    --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).