From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: No emulated disk driver for xvdX disk
Date: Mon, 26 Oct 2015 17:53:51 -0400 [thread overview]
Message-ID: <562EA0EF.8050808@oracle.com> (raw)
In-Reply-To: <22049.834.580885.592862@mariner.uk.xensource.com>
On 10/16/2015 10:01 AM, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH] libxl: No emulated disk driver for xvdX disk"):
>> When a guest configuration list xvdX for its disks, there is no need to
>> provide an emulated driver for the same target.
>>
>> Such configuration can work with the OVMF firmware, as it supports PV
>> disk.
> Acked-by: Ian Jackson<ian.jackson@eu.citrix.com>
>
> I have checked this with the docs, and this change makes the libxl
> behave as documented and as I intended when I wrote the doc.
>
This commit prevents a guest from seeing disks that specify xvdX ("disk
= [ '/root/virt/fedora.img,raw,xvda,rw' ]", for example).
TBH, I am not sure I understand how this is supposed to work --- how is
the guest expected to discover the disk?
-boris
next prev parent reply other threads:[~2015-10-26 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 11:05 [PATCH] libxl: No emulated disk driver for xvdX disk Anthony PERARD
2015-10-16 14:01 ` Ian Jackson
2015-10-22 15:54 ` Ian Campbell
2015-10-26 21:53 ` Boris Ostrovsky
2015-10-26 21:53 ` Boris Ostrovsky [this message]
2015-10-27 11:11 ` Stefano Stabellini
2015-10-27 11:31 ` George Dunlap
2015-10-27 13:19 ` Ian Jackson
2015-10-27 13:25 ` Boris Ostrovsky
2015-10-27 14:26 ` Ian Jackson
2015-10-27 14:35 ` Boris Ostrovsky
2015-10-27 14:43 ` Ian Jackson
2015-10-27 14:52 ` George Dunlap
2015-10-27 14:34 ` George Dunlap
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=562EA0EF.8050808@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 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.