From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Peter Lieven <pl@kamp.de>
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 23:11:47 +1100 [thread overview]
Message-ID: <1383048707.2494.6.camel@localhost> (raw)
In-Reply-To: <526F828E.9010109@kamp.de>
On Tue, 2013-10-29 at 10:40 +0100, Peter Lieven wrote:
> 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?!
Yes, there is no such MSR. But you probably don't need it in any case.
If you need to collect CMIDs you can access WMI data on remote
computers. Alternatively, you can write a small application to obtain
CMID locally and pass it to host via virtio-serial port.
Vadim.
>
> Peter
> >
> >
> > Thanks,
> > Peter
> >
>
>
next prev parent reply other threads:[~2013-10-29 12:12 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
2013-10-29 12:11 ` Vadim Rozenfeld [this message]
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=1383048707.2494.6.camel@localhost \
--to=vrozenfe@redhat.com \
--cc=gleb@redhat.com \
--cc=pl@kamp.de \
--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 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).