Libvirt can't tell you what the guest is running. For that, you need
higher-level software, such as libguestfs. virt-manager is an example
of a program that uses libguestfs to probe which OS is running in the
guest.
Awesome! you guys are of so much help. And sorry for top posting.
Ran into
On 02/25/2014 02:41 PM, vikhyath reddy wrote:
a) virConnectListAllNetworks(...)
b) virConnectListAllStoragePools(...)
return not supported by connection driver. I am running ESX with
libvirt-1.2.1. But I can use
That merely means no one has written the patches for ESX to support
those
Hey,
On Fri, Feb 21, 2014 at 07:30:08AM -0800, Vikhyath Reddy wrote:
Thanks for the reply Cedric,
wrappers is a dir that I made similar to examples which wraps the libvirt
c code. The reason why I am doing this is to simplify the usage of
virConnectOpenAuth - it's arguments and callbacks
Thanks for the replies guys, libvirt-glib sure sounds interesting. On the
other hand I was able to leave libvirt.so alone and write my own wrapper
(based on libvirt/examples) for easy calls from NodeJS. I can get to list
VMs, their config etc. from node but not able to list the operating system
On 02/24/2014 05:09 PM, vikhyath reddy wrote:
[Please don't top-post on technical lists]
Thanks for the replies guys, libvirt-glib sure sounds interesting. On the
other hand I was able to leave libvirt.so alone and write my own wrapper
(based on libvirt/examples) for easy calls from NodeJS. I
Hello Vik,
On Thu, 2014-02-20 at 15:14 -0800, vikhyath reddy wrote:
Thanks for libvirt. It is a life saver. I am in the process of writing
some custom wrappers for libvirt so that it can be easily accessed
from nodejs using the nodejs-ffi interfacing (basically describes a
way to convert
Hi,
Thanks for libvirt. It is a life saver. I am in the process of writing some
custom wrappers for libvirt so that it can be easily accessed from nodejs
using the nodejs-ffi interfacing (basically describes a way to convert
nodejs to c calls). I did write the wrapper on the lines of the examples