If you don't mind, I have a few other questions related to this that I'd like to ask before I forget about them. 1) Is there any technical reason for not shipping the 32-bit version of the libvirt shared library for 64-bit systems?? 2) Is it possible via libvirt to get that some additional information about the guests, such as: a) uptime b) hostname c) real operating system Thanks again. John -----Original Message----- From: Daniel P. Berrange [mailto:berrange@xxxxxxxxxx] Sent: Friday, August 20, 2010 8:12 AM To: Tavares, John Cc: libvir-list@xxxxxxxxxx; Tomen Tse; Betley, Greg; Chen, Jianjiun Subject: Re: inability to open local read-only connection On Fri, Aug 20, 2010 at 07:03:05AM -0500, Tavares, John wrote: > Hi Daniel, > > Thank you for looking into this for me and providing such a detailed explanation, I really appreciate it. > > As a related question, will this work for RHEL6 for KVM as well along with the virsh CLI?? Yes, just change the URI to 'qemu:///system'. No need for the +unix bit here because QEMU always goes via libvirtd. You have KVM in RHEL5.4 or later too that this should work with... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list