From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: "Ian Jackson" <Ian.Jackson@eu.citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 2/2] xl: dm_restrict: Document that it does not work with PV
Date: Thu, 12 Oct 2017 12:21:07 +0100 [thread overview]
Message-ID: <1507807267-13709-2-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1507807267-13709-1-git-send-email-ian.jackson@eu.citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Reported-by: Roger Pau Monné <roger.pau@citrix.com>
---
docs/man/xl.cfg.pod.5.in | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/docs/man/xl.cfg.pod.5.in b/docs/man/xl.cfg.pod.5.in
index 8125dfb..d0e3520 100644
--- a/docs/man/xl.cfg.pod.5.in
+++ b/docs/man/xl.cfg.pod.5.in
@@ -1272,7 +1272,7 @@ connectors=id0:1920x1080;id1:800x600;id2:640x480
=item B<dm_restrict=BOOLEAN>
-Restrict the HVM device model after startup,
+Restrict the device model after startup,
to limit the consequencese of security vulnerabilities in qemu.
With this feature enabled,
@@ -1287,6 +1287,11 @@ There are some significant limitations:
=item
+This is not likely to work at all for PV guests
+nor guests using qdisk backends for their block devices.
+
+=item
+
You must have a new enough qemu.
In particular,
if your qemu does not have the commit
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-12 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 11:21 [PATCH 1/2] libxl: dm_restrict: Move to domain_build_info Ian Jackson
2017-10-12 11:21 ` Ian Jackson [this message]
2017-10-12 11:23 ` [PATCH 2/2] xl: dm_restrict: Document that it does not work with PV Wei Liu
2017-10-12 11:45 ` Roger Pau Monné
2017-10-12 11:23 ` [PATCH 1/2] libxl: dm_restrict: Move to domain_build_info Wei Liu
2017-10-12 11:44 ` Roger Pau Monné
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=1507807267-13709-2-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=roger.pau@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 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.