From: Eric Blake <eblake@redhat.com>
To: Alexandre DERUMIER <aderumier@odiso.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] drive_mirror to nbd with tls ?
Date: Wed, 4 Jan 2017 14:20:49 -0600 [thread overview]
Message-ID: <7c44e2bb-f7b5-36a9-eed0-ba9a3bd7ed21@redhat.com> (raw)
In-Reply-To: <356610769.5581597.1483558443751.JavaMail.zimbra@oxygem.tv>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On 01/04/2017 01:34 PM, Alexandre DERUMIER wrote:
> Hi,
>
> I'm currently trying to implemented drive_mirror to nbd with tls.
>
> It's working fine without tls, but with tls enabled on target,
>
> I don't known how to pass tls-creds to drive_mirror nbd uri ?
Unfortunately, drive-mirror is not set up for structured specifications
(it can only take a URI), and at the same time, NBD requires the use of
structured specification (along the lines of 'blockdev-add' in qemu 2.8)
to specify TLS parameters. In other words, it's intentional that there
is no NBD URI that you can write that allows TLS. So for any earlier
versions of qemu, you're stuck.
But for qemu 2.8, we have the new blockdev-mirror (well, that command
was added in qemu 2.6, but you couldn't use NBD through blockdev-add
back then); so the correct way is to create a BDS that targets the NBD
server using 'blockdev-add' to specify the NBD parameters, then use
blockdev-mirror to mirror to that BDS.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-01-04 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 19:34 [Qemu-devel] drive_mirror to nbd with tls ? Alexandre DERUMIER
2017-01-04 20:20 ` Eric Blake [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=7c44e2bb-f7b5-36a9-eed0-ba9a3bd7ed21@redhat.com \
--to=eblake@redhat.com \
--cc=aderumier@odiso.com \
--cc=berrange@redhat.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).