All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Marcotte <marcotte@panix.com>
To: "Durrant, Paul" <pdurrant@amazon.co.uk>
Cc: Jules <jules@ispire.me>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"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: Wed, 15 Jul 2020 15:17:05 -0400	[thread overview]
Message-ID: <20200715191705.GA20643@panix.com> (raw)
In-Reply-To: <763e69df40604c51bb72477c706ec24b@EX13D32EUC003.ant.amazon.com>

This issue with Xen 4.13 and Ceph/RBD was last discussed back in February.

> Remote network Ceph image works fine with Xen 4.12.x ...
> 
> 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?

I'm also encountering the problem:

    failed to create drive: Could not open 'rbd:rbd/machine.disk0': No such file or directory

Xenstore has "params" like this:

    aio:rbd:rbd/machine.disk0

If I set it to "rbd:rbd/machine.disk0", I get a different message:

  failed to create drive: Parameter 'pool' is missing

Using upstream QEMU versions 2 or 3 works fine.

The interesting thing is that access by the virtual BIOS works fine. So,
for a PVHVM domain, GRUB loads which loads a kernel, but the kernel can't
access the disks.

--
- Brian


  reply	other threads:[~2020-07-15 19:17 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
2020-07-15 19:17   ` Brian Marcotte [this message]
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=20200715191705.GA20643@panix.com \
    --to=marcotte@panix.com \
    --cc=jules@ispire.me \
    --cc=oleksandr_grytsov@epam.com \
    --cc=pdurrant@amazon.co.uk \
    --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.