On Thu, Jun 11, 2015 at 3:51 AM, Daniel P. Berrange
<berrange(a)redhat.com>
wrote:
> On Thu, Jun 11, 2015 at 09:17:30AM +0100, Daniel P. Berrange wrote:
> > On Thu, Jun 11, 2015 at 01:51:33PM +0800, zhang bo wrote:
> > > Different OSes have different capabilities and behaviors sometimes. We
> have to distinguish them then.
> > >
> > > For example, our clients want to send NMI interrupts to certain
> guests(eg.Linux distributions), but not others(eg.Windows guests).
> > > They want to acquire the list below:
> > > guest1: RHEL 7
> > > guest2: RHEL 7
> > > guest3: Ubuntu 12
> > > guest4: Ubuntu 13
> > > guest5: Windows 7
> > > ......
> > >
> > > AFAIK, neither libvirt nor openstack, nor qemu, have such capbility of
> showing these guest OS infos.
> > > Libvirt now supports to show host capabilities and driver capability,
> but not an individual guest OS's capibility. We may refer to
> > >
http://libvirt.org/formatdomaincaps.html for more information.
> > >
>
Hello. I wrote a utility a few years ago to detect which OS is running in
each qemu VM under libvirt via memory probing. I have not touched the code
in a few years. YMMV.
http://pastebin.com/m0mfcK8G
FWIW, you can also use libguestfs to analyse the disk of a libvirt guest
while it is running, if you libguestfs' use readonly mode
Regards,
Daniel
--
|: