From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xensource.com, Ian.Jackson@eu.citrix.com,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH v3 2/6] libxl: do not add a vkb backend to hvm guests
Date: Wed, 1 Jul 2015 13:14:10 +0200 [thread overview]
Message-ID: <5593CB82.2090806@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507011156220.4360@kaball.uk.xensource.com>
El 01/07/15 a les 12.56, Stefano Stabellini ha escrit:
> On Wed, 1 Jul 2015, Roger Pau Monné wrote:
>> El 01/07/15 a les 12.29, Stefano Stabellini ha escrit:
>>> Given that xen-fbfront is likely to go away for HVM guests, I wouldn't
>>> be opposed to stop the driver initialization in Linux on x86/HVM. Unless
>>> Roger's work on HVMlite is going to need xen-fbfront again, but in that
>>> case we'll be able to distinguish a regular HVM guest from an HVMlite
>>> guest, I think.
>>
>> I haven't get to that point yet, but yes, it seems useful for HVMlite
>> guests because we won't have an emulated VGA card any more.
>>
>> HVMlite guest can be easily identified because they set the device model
>> to none:
>>
>> device_model_version == LIBXL_DEVICE_MODEL_VERSION_NONE
>
> What about the guest side? Are they going to be hvm guests from Linux
> POV? Or something else?
That's not set on stone, they could certainly be HVM guests depending on
the implementation that each OS has.
IMHO from a guest POV the interface exposed is very similar to PVH, so
in order to ease the implementation I think they should be considered
PVH guests from Linux POV, we can always move them to being HVM guests
later if needed.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-01 11:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 10:07 [PATCH v3 0/6] libxl: xs_restrict QEMU Stefano Stabellini
2015-06-10 10:09 ` [PATCH v3 1/6] libxl: allow /local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID to be written by $DOMID Stefano Stabellini
2015-06-16 14:52 ` Wei Liu
2015-06-29 17:50 ` Stefano Stabellini
2015-06-25 16:16 ` Ian Campbell
2015-06-29 17:52 ` Stefano Stabellini
2015-06-30 8:49 ` Ian Campbell
2015-06-30 13:49 ` Stefano Stabellini
2015-06-30 14:04 ` Ian Campbell
2015-06-30 15:00 ` Stefano Stabellini
2015-07-03 14:37 ` Ian Campbell
2015-07-23 17:13 ` Stefano Stabellini
2015-06-30 9:06 ` Ian Jackson
2015-06-10 10:09 ` [PATCH v3 2/6] libxl: do not add a vkb backend to hvm guests Stefano Stabellini
2015-06-16 14:57 ` Wei Liu
2015-06-16 15:39 ` Stefano Stabellini
2015-06-25 16:19 ` Ian Campbell
2015-06-29 17:59 ` Stefano Stabellini
2015-06-30 8:51 ` Ian Campbell
2015-06-30 11:21 ` Stefano Stabellini
2015-06-30 13:32 ` Ian Campbell
2015-06-30 14:02 ` Stefano Stabellini
2015-06-30 14:13 ` Ian Campbell
2015-06-30 20:38 ` Konrad Rzeszutek Wilk
2015-07-01 10:29 ` Stefano Stabellini
2015-07-01 10:55 ` Roger Pau Monné
2015-07-01 10:56 ` Stefano Stabellini
2015-07-01 11:14 ` Roger Pau Monné [this message]
2015-07-01 11:10 ` Fabio Fantoni
2015-07-01 18:41 ` Konrad Rzeszutek Wilk
2015-07-02 11:04 ` Stefano Stabellini
2015-07-02 14:31 ` Konrad Rzeszutek Wilk
2015-06-10 10:09 ` [PATCH v3 3/6] [WIP] libxl: xsrestrict QEMU Stefano Stabellini
2015-06-25 16:24 ` Ian Campbell
2015-06-29 18:07 ` Stefano Stabellini
2015-06-30 8:53 ` Ian Campbell
2015-06-30 13:53 ` Stefano Stabellini
2015-06-10 10:09 ` [PATCH v3 4/6] libxl: change xs path for QEMU Stefano Stabellini
2015-06-25 16:21 ` Ian Campbell
2015-06-29 18:26 ` Stefano Stabellini
2015-06-10 10:09 ` [PATCH v3 5/6] libxl: change qdisk-backend-pid path on xenstore Stefano Stabellini
2015-06-10 10:09 ` [PATCH v3 6/6] libxl: spawns two QEMUs for HVM guests Stefano Stabellini
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=5593CB82.2090806@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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).