From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH] docs: Clarify scope of reboot= and noreboot Xen command line options
Date: Thu, 22 Dec 2016 15:02:53 +0000 [thread overview]
Message-ID: <1482418973-26941-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
CC: Jan Beulich <JBeulich@suse.com>
---
docs/misc/xen-command-line.markdown | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index 0138978..68c81e6 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -1260,6 +1260,7 @@ the **vga** option, which relies on real mode to set the video mode.
Do not automatically reboot after an error. This is useful for
catching debug output. Defaults to automatically reboot after 5
seconds.
+This is equivalent to `reboot=no`
### nosmp
> `= <boolean>`
@@ -1356,7 +1357,9 @@ The following resources are available:
> Default: `0`
-Specify the host reboot method.
+Specify the host reboot method,
+used when Xen crashes.
+(This does not affect deliberate reboots initiated by dom0.)
`warm` instructs Xen to not set the cold reboot flag.
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-22 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 15:02 Ian Jackson [this message]
2016-12-22 15:30 ` [PATCH] docs: Clarify scope of reboot= and noreboot Xen command line options Jan Beulich
2016-12-22 18:59 ` Ian Jackson
2016-12-27 15:36 ` Jan Beulich
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=1482418973-26941-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=JBeulich@suse.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).