From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v4] block: Add support for Secure Shell (ssh) block device.
Date: Wed, 27 Mar 2013 15:57:28 +0000 [thread overview]
Message-ID: <1364399849-5518-1-git-send-email-rjones@redhat.com> (raw)
This is version 4 of the Secure Shell (ssh) block device.
Links to earlier versions:
v1: http://www.mail-archive.com/qemu-devel@nongnu.org/msg162605.html
v2: http://www.mail-archive.com/qemu-devel@nongnu.org/msg162730.html
v3: http://www.mail-archive.com/qemu-devel@nongnu.org/msg162805.html
The version supports:
- image creation, so eg. 'qemu-img create' can be used
- extending the file, so qcow2 works
- file.host, file.port, file.path, file.user properties (or ssh:// URLs)
- asynch read/write using coroutines
- ssh-agent authentication
- checks the remote host key against known_hosts
This version is robust and works for me reliably. Performance of
linear reading (eg. qemu-img convert ssh://...) is very fast indeed.
Random access performance is fairly poor (about the same as sshfs).
However it's usable remotely for booting and running guests, even over
relatively slow wifi links.
Rich.
next reply other threads:[~2013-03-27 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:57 Richard W.M. Jones [this message]
2013-03-27 15:57 ` [Qemu-devel] [PATCH v4] block: Add support for Secure Shell (ssh) block device Richard W.M. Jones
2013-03-28 10:47 ` Stefan Hajnoczi
2013-03-28 11:16 ` Richard W.M. Jones
2013-03-28 13:29 ` Stefan Hajnoczi
2013-04-03 22:14 ` Richard W.M. Jones
2013-04-08 11:37 ` Stefan Hajnoczi
2013-04-08 13:01 ` Richard W.M. Jones
2013-04-08 13:05 ` Richard W.M. Jones
2013-04-08 14:58 ` Stefan Hajnoczi
2013-04-08 20:21 ` Stefan Hajnoczi
2013-04-09 7:30 ` Richard W.M. Jones
2013-04-09 12:56 ` Stefan Hajnoczi
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=1364399849-5518-1-git-send-email-rjones@redhat.com \
--to=rjones@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).