qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, qemu-block@nongnu.org
Subject: [Qemu-devel] How to specify the full block driver tree on the CLI ?
Date: Thu, 29 Oct 2015 08:58:56 +0900	[thread overview]
Message-ID: <20151028235824.GB663@redhat.com> (raw)

As previously mentioned, I'm working on support for LUKS full disk
encryption in QEMU. I have a simple driver implemented that works
on top of plain files. eg I can launch qemu-io thus:

 $ qemu-io /home/berrange/VirtualMachines/demo.luks-aes-cbc-plain-sha256

and it'll probe the luks format & instantiate my "luks" block driver impl
on top of the "file" driver. IIUC, I should be able to layer this format
driver on top of any of the QEMU block driver backends though. In particular
I want to be able to layer it on top of any of the network drivers (RBD,
iSCSI and glusterfs). I'm struggling to figure out the right syntax to
specify this to QEMU though, using either qemu-io, or the system emulators
with the -drive arg.  Are there any docs somewhere about the way to
structure the command line arguments to build up a stack of block drivers.
I'd like to figure out the following combinations, for qemu-io, qemu-img
and system emulator -drive syntax.

 - luks -> file
 - qcow2 -> luks -> file
 - luks -> rbd
 - luks -> iscsi
 - luks -> glusterfs

Currently the only required QemuOpt for the luks driver is the ID of
a secret to provide the password.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

             reply	other threads:[~2015-10-28 23:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 23:58 Daniel P. Berrange [this message]
2015-10-29  8:11 ` [Qemu-devel] How to specify the full block driver tree on the CLI ? Kevin Wolf
2015-10-29  8:15   ` Daniel P. Berrange
2015-10-29  8:31     ` Kevin Wolf

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=20151028235824.GB663@redhat.com \
    --to=berrange@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).