From: Paolo Bonzini <pbonzini@redhat.com>
To: Kai Meyer <kai.meyer@storagecraft.com>
Cc: Stefan Weil <weil@mail.berlios.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Nate Bushman <Nate.Bushman@storagecraft.com>
Subject: Re: [Qemu-devel] Add support for new image type
Date: Mon, 05 Mar 2012 10:14:35 +0100 [thread overview]
Message-ID: <4F5483FB.3030904@redhat.com> (raw)
In-Reply-To: <D7BD40FC27827E4D8E53A46A71FDCCF902C303F6@STC-EXCH.stc.local>
Il 02/03/2012 19:38, Kai Meyer ha scritto:
> Well, yes. I was assuming that there was potential for us to be able
> to distribute qemu modifications that would not require us opening up
> our library. The more we look at it, and some past precedence we've
> experienced, it looks like it's not going to happen.
>
> I think I agree that iSCSI is really our only option (legally). Too
> bad. The code was so simple to integrate directly into qemu. I have
> to give you guys kudos again for already having such a simple
> integration point.
Adding a small, open source version of the image access code would be
another possibility; you probably have a public spec of the format, and
including support for your format in a QEMU block driver doesn't change
much. Who knows, it may even bring cheap advertising. :)
QEMU has several entry points for the block driver, and the once with
lower performance are extremely easy to implement (see block/bochs.c).
In theory it could even be read-only, though we would have problems
testing it and this may mean bitrot.
Paolo
next prev parent reply other threads:[~2012-03-05 9:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:52 [Qemu-devel] Add support for new image type Kai Meyer
2012-03-01 0:16 ` Brian Jackson
2012-03-01 15:03 ` Kevin Wolf
2012-03-01 19:45 ` Kai Meyer
2012-03-01 20:10 ` Stefan Weil
2012-03-01 20:18 ` Stefan Weil
2012-03-01 20:31 ` Kai Meyer
2012-03-01 21:05 ` Anthony Liguori
2012-03-01 21:14 ` Kai Meyer
2012-03-02 6:54 ` Paolo Bonzini
2012-03-02 18:38 ` Kai Meyer
2012-03-05 9:14 ` Paolo Bonzini [this message]
2012-03-05 12:14 ` Stefan Hajnoczi
2012-05-16 17:06 ` Kai Meyer
2012-05-16 17:48 ` Paolo Bonzini
2012-05-16 18:21 ` Anthony Liguori
2012-05-16 18:56 ` Kai Meyer
2012-05-16 19:20 ` Kai Meyer
2012-05-17 9:10 ` Artyom Tarasenko
2012-05-17 9:41 ` Paolo Bonzini
2012-05-17 11:03 ` Artyom Tarasenko
2012-05-17 17:53 ` Kai Meyer
2012-05-17 19:43 ` Paolo Bonzini
2012-05-17 20:18 ` Kai Meyer
2012-03-01 20:26 ` Kai Meyer
2012-03-01 20:38 ` Paolo Bonzini
2012-03-01 20:53 ` Stefan Weil
2012-03-01 21:02 ` Anthony Liguori
2012-03-08 15:17 ` Kevin Wolf
2012-03-08 17:16 ` Nate Bushman
2012-03-09 9:23 ` Kevin Wolf
2012-03-09 10:28 ` Paolo Bonzini
2012-03-09 11:26 ` Kevin Wolf
2012-03-10 16:54 ` Nate Bushman
2012-03-10 16:53 ` Nate Bushman
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=4F5483FB.3030904@redhat.com \
--to=pbonzini@redhat.com \
--cc=Nate.Bushman@storagecraft.com \
--cc=anthony@codemonkey.ws \
--cc=kai.meyer@storagecraft.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).