From: Jacob Bang <julemand101@archlinux.dk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1775366] Re: [Feature request] qemu-ga - Allow unexpected parameter
Date: Wed, 06 Jun 2018 21:07:32 -0000 [thread overview]
Message-ID: <152831925237.24753.7046504788711493357.malone@gac.canonical.com> (raw)
In-Reply-To: 152827602795.25960.11192717382861692470.malonedeb@wampee.canonical.com
I see you point. Just close this issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1775366
Title:
[Feature request] qemu-ga - Allow unexpected parameter
Status in QEMU:
New
Bug description:
It whould be nice if the qemu-ga allowed received messages to contain
fields which is not part of the spec. In my example I have a host
which sends the following request:
{"execute":"guest-exec","arguments":{"path":"prl_nettool","capture-
output":true,"execute-in-shell":false,"arg":[...]}}
Right now this request is rejected with the following error:
{"error": {"class": "GenericError", "desc": "Parameter 'execute-in-
shell' is unexpected"}}
My situation is the hosting provider I use does have some customized
solution which sends some extra arguments. I have manually patched my
qemu-ga so it accepts the "execute-in-shell" parameter but I don't
think this should be necessary.
Instead of "Error" it should just be a "warning" returned to the user
of qemu-ga but the call should still be executed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1775366/+subscriptions
next prev parent reply other threads:[~2018-06-06 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 9:07 [Qemu-devel] [Bug 1775366] [NEW] [Feature request] qemu-ga - Allow unexpected parameter Jacob Bang
2018-06-06 19:40 ` [Qemu-devel] [Bug 1775366] " John Snow
2018-06-06 21:07 ` Jacob Bang [this message]
2018-06-07 10:14 ` Thomas Huth
2018-06-07 10:28 ` Daniel Berrange
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=152831925237.24753.7046504788711493357.malone@gac.canonical.com \
--to=julemand101@archlinux.dk \
--cc=1775366@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.