All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: janine.schneider@fau.de
Cc: 'Stefan Hajnoczi' <stefanha@gmail.com>,
	'qemu-devel' <qemu-devel@nongnu.org>,
	'qemu block' <qemu-block@nongnu.org>
Subject: Re: Integration of qemu-img
Date: Thu, 23 Apr 2020 12:03:21 +0100	[thread overview]
Message-ID: <20200423110321.GB1077680@redhat.com> (raw)
In-Reply-To: <008a01d6195d$78280570$68781050$@fau.de>

On Thu, Apr 23, 2020 at 12:53:48PM +0200, janine.schneider@fau.de wrote:
> Hy again,
> 
> okay so now we have an easy way out just in case.
> But I still want to build an DLL and/or a shared library for integration
> into the tool. I want the tool to be platform independent and I was
> already able to build qemu-img as cross build with mingw64. Does anybody
> have experience in building a qemu library or tried it already?

It has been discussed in the past, but general wasn't considered a
viable, because any apps using it would have to be strictly licensed
as GPLv2-only. This would prevent the library being used by anything
that includes GPLv3 code, or obviously from closed source apps. This
would seriously restrict how useful any library was.

I would also note that QEMU disk code is not robust against malicously
created disk images. It is possible to create images that inflict
a denial of service in terms of memory and CPU usage. Thus if an
application is handling disk images obtained from untrusted users,
it is desirable for qemu-img to be a separate process, such that
you can put strict resource limits on it as protection against DoS.

> The tool I want to integrate qemu in is published under GPL itself. And
> if I am able to build qemu as library I will share it with the community
> and everybody interested in having it.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2020-04-23 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00fc01d61256$35f849c0$a1e8dd40$@fau.de>
2020-04-16  7:50 ` Integration of qemu-img Markus Armbruster
2020-04-22 16:18   ` Stefan Hajnoczi
     [not found]     ` <006e01d61958$de787120$9b695360$@fau.de>
2020-04-23 10:40       ` Stefan Hajnoczi
2020-04-23 10:53         ` AW: " janine.schneider
2020-04-23 11:03           ` Daniel P. Berrangé [this message]

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=20200423110321.GB1077680@redhat.com \
    --to=berrange@redhat.com \
    --cc=janine.schneider@fau.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.