From: "Durrant, Paul" <pdurrant@amazon.co.uk>
To: Jules <jules@ispire.me>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "oleksandr_grytsov@epam.com" <oleksandr_grytsov@epam.com>,
"wl@xen.org" <wl@xen.org>
Subject: Re: [Xen-devel] XEN Qdisk Ceph rbd support broken?
Date: Tue, 4 Feb 2020 08:53:16 +0000 [thread overview]
Message-ID: <763e69df40604c51bb72477c706ec24b@EX13D32EUC003.ant.amazon.com> (raw)
In-Reply-To: <AC8105C4-6DAD-4AB0-AC3F-B4CDD151CDEB@ispire.me>
De-htmling...
---
From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Jules
Sent: 03 February 2020 17:35
To: xen-devel@lists.xenproject.org
Cc: oleksandr_grytsov@epam.com; wl@xen.org
Subject: [Xen-devel] XEN Qdisk Ceph rbd support broken?
Hey,
I don’t know if it was this or a previous change in qdisk driver, but can it be that remote Ceph RBD support is broken?
https://github.com/xen-project/xen/commit/8f486344a00652ed202ade43c02c96771812bf8c
Remote network Ceph image works fine with Xen 4.12.x with a config syntax like this:
disk = [ 'format=raw, vdev=xvda1, access=rw,backendtype=qdisk, target=rbd:<pool-Name>/<Image-Name>:id=<cephx-Id>‘ ]
In Xen 4.13.0 which I have tested recently it blames with the error message „no such file or directory“ as it would try accessing the image over filesystem instead of remote network image.
---
I doubt the issue is in xl/libxl; sounds more likely to be in QEMU. The PV block backend infrastructure in QEMU was changed between the 4.12 and 4.13 releases. Have you tried using an older QEMU with 4.13?
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-04 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 17:34 [Xen-devel] XEN Qdisk Ceph rbd support broken? Jules
2020-02-04 8:53 ` Durrant, Paul [this message]
2020-07-15 19:17 ` Brian Marcotte
2020-07-16 7:13 ` [EXTERNAL] " Paul Durrant
2020-07-16 20:23 ` Brian Marcotte
2020-07-17 7:48 ` Paul Durrant
2020-09-28 14:27 ` Anthony PERARD
2020-09-29 9:17 ` Brian Marcotte
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=763e69df40604c51bb72477c706ec24b@EX13D32EUC003.ant.amazon.com \
--to=pdurrant@amazon.co.uk \
--cc=jules@ispire.me \
--cc=oleksandr_grytsov@epam.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.