From: "Alex Braunegg" <alex.braunegg@gmail.com>
To: 'Ian Campbell' <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [BUG] libxl: error: libxl_device.c:301:libxl__device_disk_set_backend: no suitable backend for disk
Date: Fri, 5 Feb 2016 06:19:15 +1100 [thread overview]
Message-ID: <56b3a437.65a3420a.7c73.7ed0@mx.google.com> (raw)
In-Reply-To: <1454585158.25207.177.camel@citrix.com>
Hi Ian,
As per http://xenbits.xen.org/docs/4.6-testing/misc/xl-disk-configuration.txt the disk specification conforms to:
disk = [ '/dev/vg/guest-volume,,hda', '/root/image.iso,,hdc,cdrom' ]
Is there any additional information you need to replicate this issue?
Best regards,
Alex
-----Original Message-----
From: Ian Campbell [mailto:ian.campbell@citrix.com]
Sent: Thursday, 4 February 2016 10:26 PM
To: Alex Braunegg; xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [BUG] libxl: error: libxl_device.c:301:libxl__device_disk_set_backend: no suitable backend for disk
On Thu, 2016-02-04 at 10:53 +1100, Alex Braunegg wrote:
>
> There was a thread on this in 2013
> (http://lists.xen.org/archives/html/xen-devel/2013-03/msg00806.html) however
> I have looked at the disk configuration, and there is no phy: / raw: / file:
> prefix to the disk specification.
Not sure what is going on but I just wanted to mention that phy: etc
prefixes are considered legacy. See http://xenbits.xen.org/docs/4.6-testing
/misc/xl-disk-configuration.txt for the actual syntax and how phy: is
mapped.
Ian.
next prev parent reply other threads:[~2016-02-04 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 23:53 [BUG] libxl: error: libxl_device.c:301:libxl__device_disk_set_backend: no suitable backend for disk Alex Braunegg
2016-02-04 11:25 ` Ian Campbell
2016-02-04 19:19 ` Alex Braunegg [this message]
2016-02-08 21:48 ` Alex Braunegg
2016-02-09 12:00 ` Roger Pau Monné
2016-02-10 1:03 ` Alex Braunegg
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=56b3a437.65a3420a.7c73.7ed0@mx.google.com \
--to=alex.braunegg@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.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).