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 something else today, why are calls like a) virConnectListAllNetworks(...) b) virConnectListAllStoragePools(...) return "not supported by connection driver". I am running ESX with libvirt-1.2.1. But I can use a) virConnectListStoragePools(...) b) virConnectListNetworks(...) without any problems. Do you guys think I have libvirt configured incorrectly at my end? Thanks, Vik. On Mon, Feb 24, 2014 at 6:03 PM, Eric Blake <eblake@redhat.com> wrote:
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 can get to list VMs, their config etc. from node but not able to list the operating system running on the VM (ubuntu, win7, etc.). I can get the os_type though (hvm in my case) but that does not tell me whether it is running a windows or a linux distro.
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.
-- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org