From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: add "xl qemu-monitor-command"
Date: Mon, 5 Sep 2016 13:30:31 +0200 [thread overview]
Message-ID: <4dfea2a1-8b69-fc62-a4c9-80c2d69ec314@suse.com> (raw)
In-Reply-To: <22477.18866.27916.372639@mariner.uk.xensource.com>
On 05/09/16 12:32, Ian Jackson wrote:
> Juergen Gross writes ("[PATCH] libxl: add "xl qemu-monitor-command""):
>> Add a new xl command "qemu-monitor-command" to issue arbitrary commands
>> to a domain's device model. Syntax is:
>>
>> xl qemu-monitor-command <domain> <command>
>>
>> The command is issued via qmp human-monitor-command command. Any
>> information returned by the command is printed to stdout.
> ...
>> +=item B<qemu-monitor-command> I<domain-id> I<command>
>> +
>> +Issue a monitor command to the device model of the domain specified by
>> +I<domain-id>. I<command> can be any valid command qemu understands. This
>> +can be e.g. used to add non-standard devices or devices with non-standard
>> +parameters to a domain. The output of the command is printed to stdout.
>
> This needs some kind of health warning. Something like:
>
> Warning: This qemu monitor access is provided for convenience when
> debugging, troubleshooting, and experimenting. Its use is not
> supported by the Xen Project.
>
> Specifically, not all information printed by the qemu monitor will
> necessarily be accurate or complete, because in a Xen system qemu
> does not have a complete view of the guest.
>
> Furthermore, modifying the guest's setup via the qemu monitor may
> conflict with the Xen toolstack's assumptions. Resulting problems
> may include, but are not limited to: guest crashes; toolstack error
> messages; inability to migrate the guest; and security
> vulnerabilities which are not covered by the Xen Project security
> response policy.
Thanks for the complete text! I'll add it to the man page.
> The rest of the documentation will need adjusting. As an example of
> the incompleteness I am talking about I think the example shows only
> some of the USB devices presented to the guest.
Hmm, I think the statement:
+Obtain information of USB devices connected via the device model to a
+domain:
is absolutely correct. Which USB devices connected via the device model
won't be shown?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-05 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 9:29 [PATCH] libxl: add "xl qemu-monitor-command" Juergen Gross
2016-09-05 10:32 ` Ian Jackson
2016-09-05 11:30 ` Juergen Gross [this message]
2016-09-05 12:18 ` Ian Jackson
2016-09-05 12:29 ` Juergen Gross
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=4dfea2a1-8b69-fc62-a4c9-80c2d69ec314@suse.com \
--to=jgross@suse.com \
--cc=ian.jackson@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 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).