From: "Tomáš Golembiovský" <tgolembi@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Eric Blake <eblake@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Vinzenz 'evilissimo' Feenstra <vfeenstr@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 0/1] qemu-ga: add guest-get-osinfo command
Date: Tue, 27 Jun 2017 01:41:22 +0200 [thread overview]
Message-ID: <20170627014122.579f4a2e@fiorina> (raw)
In-Reply-To: <CAJ+F1C+2QiQMxzMQvaMDV8gmU95+Q46-QbA1gPOZ-NCJSLTX5Q@mail.gmail.com>
Hi,
On Mon, 26 Jun 2017 12:27:57 +0000
Marc-André Lureau <marcandre.lureau@gmail.com> wrote:
> Hi
>
> On Wed, Jun 7, 2017 at 2:02 PM Tomáš Golembiovský <tgolembi@redhat.com>
> wrote:
>
> > v5:
> > - fixed build failure with older glib
> > - fixed coding style issues
> > - fixed one log string
> >
> > This is a continuation of the work started by Vinzenz Feenstra in the
> > threads:
> >
> > https://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg04154.html
> > https://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg04302.html
> > https://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg06262.html
> >
> > The idea is to report some basic information from uname and from
> > os-release file, if it is present. On MS Windows, where neither uname
> > nor os-release exist we fill the values based on the information we can
> > get from the OS.
> >
> > The example output on Fedora is:
> >
> > {
> > "return": {
> > "kernel-version": "#1 SMP Mon May 8 18:46:06 UTC 2017",
> > "kernel-release": "4.10.15-200.fc25.x86_64",
> > "machine-hardware": "x86_64",
> > "id": "fedora",
> > "name": "Fedora",
> > "pretty-name": "Fedora 25 (Server Edition)",
> > "version": "25 (Server Edition)",
> > "variant": "Server Edition",
> > "version-id": "25",
> > "variant-id": "server"
> > }
> > }
> >
> > The example output on MS Windows 10 is:
> >
> > {
> > "return": {
> > "kernel-version": "10.0",
> > "kernel-release": "10240",
> > "machine-hardware": "x86_64",
> > "id": "mswindows",
> > "name": "Microsoft Windows",
> > "pretty-name": "Windows 10 Enterprise",
> > "version": "Microsoft Windows 10",
> > "version-id": "10",
> > "variant": "client",
> > "variant-id": "client"
> > }
> > }
> >
> > One issue I see with the current implementation is that one is not able
> > to distinguish between various (non-linux) POSIX systems from the
> > returned values. That's because without os-release file (which I assume
> > is not common on non-linux platforms) only kernel-version,
> > kernel-release and machine-hardware are returned and telling what OS is
> > running there is a guessing game. Is this a problem?
> >
> >
> I don't know, but I would rather solve this problem at OS & os-release
> level. Raise your concerns on the XDG/osrelease mailing list?
>
>
> > Also the qapi documentiaton probably need some polishing. Unfortunately,
> > so far I was unable to get qapi parser satisfied and still include all
> > the important information.
> >
>
> You mean the doc parser? What's the issue?
>
In the end no issue at all. It turned out my problems were caused by
stray quotes.
Tomas
> >
> > Tomas Golembiovsky
> >
> > Tomáš Golembiovský (1):
> > qemu-ga: add guest-get-osinfo command
> >
> > configure | 2 +-
> > qga/commands-posix.c | 160
> > ++++++++++++++++++++++++++++++++++++++++++++++++
> > qga/commands-win32.c | 170
> > +++++++++++++++++++++++++++++++++++++++++++++++++++
> > qga/qapi-schema.json | 57 +++++++++++++++++
> > 4 files changed, 388 insertions(+), 1 deletion(-)
> >
> > --
> > 2.13.0
> >
> > --
> Marc-André Lureau
--
Tomáš Golembiovský <tgolembi@redhat.com>
prev parent reply other threads:[~2017-06-26 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 12:02 [Qemu-devel] [PATCH v5 0/1] qemu-ga: add guest-get-osinfo command Tomáš Golembiovský
2017-06-07 12:02 ` [Qemu-devel] [PATCH v5 1/1] " Tomáš Golembiovský
2017-06-26 12:27 ` Marc-André Lureau
2017-06-13 6:33 ` [Qemu-devel] [PATCH v5 0/1] " Tomáš Golembiovský
2017-06-26 12:27 ` Marc-André Lureau
2017-06-26 23:41 ` Tomáš Golembiovský [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=20170627014122.579f4a2e@fiorina \
--to=tgolembi@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=vfeenstr@redhat.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).