It is available via xm, so my point was if it can, why can't libvirt?? In the end, I had to switch to calling virsh until I can get all of problem resolved.
Ideally, virsh to would be able to provide most of the same data as going thru libvirt directly. It might also be nice if it provided that data in a more machine parseable format. -----Original Message----- From: Justin Clift [mailto:jcl...@redhat.com] Sent: Friday, August 20, 2010 9:15 AM To: Daniel P. Berrange Cc: Tavares, John; libvir-list@redhat.com Subject: Re: [libvirt] inability to open local read-only connection On 08/20/2010 10:58 PM, Daniel P. Berrange wrote: <snip> >> a) uptime <snip> > You can't reliably get any of that information without having > an agent running inside the guest OS. We should be able to get the uptime of the guest's qemu process itself though, and report that back "over the wire" to a requesting client, without needing a guest OS agent. Or even keep track of when libvirt launched the guest as wall clock time. Not the same thing as "how long has the guest OS been up?", but potentially useful for management tools. Regards and best wishes, Justin Clift -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
