From: Hans van Kranenburg <hans@knorrie.org>
To: xen-devel@lists.xenproject.org
Cc: Andy Smith <andy@strugglers.net>, Lars Kurth <lars.kurth.xen@gmail.com>
Subject: What about dom0? (was: Re: Clarification regarding Meltdown and 64-bit PV guests)
Date: Sun, 14 Jan 2018 15:41:32 +0100 [thread overview]
Message-ID: <5A5B6C1C.1010809@knorrie.org> (raw)
In-Reply-To: <20180113064223.GT29360@bitfolk.com>
On 13/01/2018 07:42, Andy Smith wrote:
> [...]
Related...
Dom0 is a PV guest with more privileges than a domU, right?
Currently all documentation and FAQ do not contain a section about this.
It's all about the hypervisor and guests.
Probable reason for this is that most people on this list implicitly
think about dom0 as a thing that has as only purpose to manage starting
and stopping domUs, forwarding some network traffic using bridges or
openvswitch, and with its own network connection probably on a separate
management network...
But what about small-deployment-users who use the dom0 for more things,
and have a bunch of Xen domUs running inside. Who knows what they do,
maybe they even have their graphical desktop environment running in dom0
with web browser and everything?
Just throwing some dust in the air... :)
Hans
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-01-14 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 6:42 Clarification regarding Meltdown and 64-bit PV guests Andy Smith
2018-01-13 9:43 ` Hans van Kranenburg
2018-01-13 10:08 ` Andy Smith
2018-01-13 11:12 ` Hans van Kranenburg
2018-01-14 14:00 ` Dongli Zhang
2018-01-14 14:15 ` Hans van Kranenburg
2018-01-15 17:48 ` Stefano Stabellini
2018-01-14 14:05 ` Dongli Zhang
2018-01-14 14:41 ` Hans van Kranenburg [this message]
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=5A5B6C1C.1010809@knorrie.org \
--to=hans@knorrie.org \
--cc=andy@strugglers.net \
--cc=lars.kurth.xen@gmail.com \
--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.