From: Max Reitz <mreitz@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block/ssh: Implement .bdrv_refresh_filename()
Date: Wed, 6 Feb 2019 17:42:15 +0100 [thread overview]
Message-ID: <0d644429-0b16-bc7c-c583-d4684e47adb1@redhat.com> (raw)
In-Reply-To: <20190206163704.GV12500@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]
On 06.02.19 17:37, Richard W.M. Jones wrote:
> On Wed, Feb 06, 2019 at 04:29:17PM +0100, Max Reitz wrote:
>> This series implements .bdrv_refresh_filename() for the ssh block
>> driver, along with an appropriate .bdrv_dirname() so we don't chop off
>> query strings for backing files with relative filenames.
>>
>> This series depends on my "block: Fix some filename generation issues"
>> series.
>>
>> Based-on: 20190201192935.18394-1-mreitz@redhat.com
>
> I have verified that this doesn't appear to break the existing driver:
> ssh connections to block devices still work as well as they did before
> (which is to say, not very well, I wish we would replace this driver
> with Pino Toscano's reimplementation that uses libssh1).
>
> However I wasn't sure how I could trigger the bdrv_refresh_filename
> code path, so I don't think I tested that.
One test case goes like this:
Before this series:
$ ./qemu-img create -f qcow2 /tmp/base.qcow2 64M
$ ./qemu-img create -f qcow2 -b base.qcow2 /tmp/top.qcow2
$ ./qemu-img info ssh://localhost/tmp/top.qcow2
image: json:{"driver": "qcow2", "file": {"server.host": "localhost",
"server.port": "22", "driver": "ssh", "path": "/tmp/top.qcow2"}}
[...]
backing file: base.qcow2 (cannot determine actual path)
[...]
$ ./qemu-io ssh://localhost/tmp/top.qcow2
can't open device ssh://localhost/tmp/top.qcow2: Cannot generate a base
directory for ssh nodes
So the filename is weird and you cannot open overlays with relative
backing files.
After this series:
$ ./qemu-img info ssh://localhost/tmp/top.qcow2
image: ssh://maxx@localhost:22/tmp/top.qcow2
[...]
backing file: base.qcow2 (actual path:
ssh://maxx@localhost:22/tmp/base.qcow2)
$ ./qemu-io ssh://localhost/tmp/top.qcow2
qemu-io> quit
The filename looks better and the image is usable.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-06 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 15:29 [Qemu-devel] [PATCH v2 0/2] block/ssh: Implement .bdrv_refresh_filename() Max Reitz
2019-02-06 15:29 ` [Qemu-devel] [PATCH v2 1/2] " Max Reitz
2019-02-06 15:29 ` [Qemu-devel] [PATCH v2 2/2] block/ssh: Implement .bdrv_dirname() Max Reitz
2019-02-06 15:45 ` [Qemu-devel] [PATCH v2 0/2] block/ssh: Implement .bdrv_refresh_filename() Richard W.M. Jones
2019-02-06 15:51 ` Max Reitz
2019-02-06 16:37 ` Richard W.M. Jones
2019-02-06 16:42 ` Max Reitz [this message]
2019-02-06 17:00 ` Richard W.M. Jones
2019-02-06 17:16 ` Max Reitz
2019-02-25 13:39 ` Max Reitz
2019-02-25 14:10 ` Max Reitz
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=0d644429-0b16-bc7c-c583-d4684e47adb1@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).