From: Peter Lieven <pl@kamp.de>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] kvm/hyper-v: obtaining client machine id
Date: Tue, 29 Oct 2013 10:40:30 +0100 [thread overview]
Message-ID: <526F828E.9010109@kamp.de> (raw)
In-Reply-To: <1974798180.15665305.1383037421877.JavaMail.root@redhat.com>
On 29.10.2013 10:03, Vadim Rozenfeld wrote:
>
> ----- Original Message -----
> From: "Peter Lieven" <pl@kamp.de>
> To: "Gleb Natapov" <gleb@redhat.com>, "Vadim Rozenfeld" <vrozenfe@redhat.com>, qemu-devel@nongnu.org
> Sent: Monday, October 28, 2013 6:50:31 PM
> Subject: [Qemu-devel] kvm/hyper-v: obtaining client machine id
>
> Hi,
>
> do you know if it is possible to obtain the client machine id of a Windows vServer via
> a Hyper-V hypercall? I would need an information to check vServer activations against
> our KMS.
>
> Hi Peter,
>
> WMI SoftwareLicensingService should be able to do it
> http://msdn.microsoft.com/en-us/library/cc534597%28v=vs.85%29.aspx
> Vadim.
Sorry, I don't see how to get this information via a Hyper-V MSR?!
Peter
>
>
> Thanks,
> Peter
>
--
Mit freundlichen Grüßen
Peter Lieven
...........................................................
KAMP Netzwerkdienste GmbH
Vestische Str. 89-91 | 46117 Oberhausen
Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
pl@kamp.de | http://www.kamp.de
Geschäftsführer: Heiner Lante | Michael Lante
Amtsgericht Duisburg | HRB Nr. 12154
USt-Id-Nr.: DE 120607556
...........................................................
next prev parent reply other threads:[~2013-10-29 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 7:50 [Qemu-devel] kvm/hyper-v: obtaining client machine id Peter Lieven
2013-10-29 9:03 ` Vadim Rozenfeld
2013-10-29 9:40 ` Peter Lieven [this message]
2013-10-29 12:11 ` Vadim Rozenfeld
2013-10-29 11:03 ` Gleb Natapov
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=526F828E.9010109@kamp.de \
--to=pl@kamp.de \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@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 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.