From: Paolo Bonzini <pbonzini@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Building QMP in qemu-nbd
Date: Thu, 13 Mar 2014 16:21:03 +0100 [thread overview]
Message-ID: <5321CCDF.8000908@redhat.com> (raw)
In-Reply-To: <20140313144017.GA4798@irqsave.net>
Il 13/03/2014 15:40, Benoît Canet ha scritto:
> Hi,
>
> I want to make qemu-nbd QMP aware so the cloud stack my customer work on could
> start lxc containers with qcow2 KVM images and still benefit from the quorum
> and snapshot goodness.
Yes, blockdev can help for this. In the meanwhile, could you start a
dummy guest ("-M none -m 1 -machine accel=qtest -display none
-nodefaults" consumes ~16M here) and use the embedded NBD server?
> Stefan mentioned the nice idea of splitting qapi-schema.json in small files
> in a subdirectory so qemu-nbd could use only the block related commands.
>
> Eric: What do you think of this idea ?
> Do you have variants of this idea ?
Weren't there patches to add "include" directives to qapi-schema.json?
Paolo
prev parent reply other threads:[~2014-03-13 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:40 [Qemu-devel] Building QMP in qemu-nbd Benoît Canet
2014-03-13 14:56 ` Eric Blake
2014-03-13 15:21 ` Paolo Bonzini [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=5321CCDF.8000908@redhat.com \
--to=pbonzini@redhat.com \
--cc=benoit.canet@irqsave.net \
--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 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.