From: Anthony Liguori <anthony@codemonkey.ws>
To: Kai Meyer <kai.meyer@storagecraft.com>
Cc: Nate Bushman <Nate.Bushman@storagecraft.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add support for new image type
Date: Thu, 01 Mar 2012 15:02:37 -0600 [thread overview]
Message-ID: <4F4FE3ED.5070202@codemonkey.ws> (raw)
In-Reply-To: <4F4FD1C9.8050006@storagecraft.com>
On 03/01/2012 01:45 PM, Kai Meyer wrote:
> Great, this is exactly what we're after. I work for StorageCraft, and we would
> like to figure out some way to allow qemu to directly consume our image-based
> backups. It would provide us with user-space mounting (via libguestfs) as well
> as booting VMs directly from Backup images. We already have a proprietary image
> access library that provides block-wise access to our image files. I have been
> able to scratch together a proof of concept already, which I am really pleased
> with.
>
> I see only two roadblocks for which I don't have immediate answers for.
>
> 1) Licensing
> Is it possible to license our contributions in such a way that we do not need to
> open the source code of our image access library?
Hi,
Obviously, you should ask your legal department for advice on licensing, but as
a policy of the QEMU project, it's unlikely we would accept anything that's sole
purpose was to enable third party proprietary code regardless of license
compatibility. QEMU is an Open Source project and our past and future success
depends on the collaboration and innovation that comes from having an open code
base.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-03-01 21:03 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
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 [this message]
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=4F4FE3ED.5070202@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Nate.Bushman@storagecraft.com \
--cc=kai.meyer@storagecraft.com \
--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).