On Fri, Dec 21, 2012 at 04:55:09PM +0000, Matthew Garrett wrote:
On Fri, Dec 21, 2012 at 04:37:59PM +0000, Richard W.M. Jones wrote:
> On Fri, Dec 21, 2012 at 04:22:47PM +0000, Matthew Garrett wrote:
> > On Fri, Dec 21, 2012 at 10:49:19AM -0500, Don Dutile wrote:
> > > fyi: libexec has been critical to virtualization for quite some time...
>
> I think Don is referring to the helper binaries that go into
> /usr/libexec:
>
> $ rpm -ql qemu-common | grep libexec
> /usr/libexec/qemu-bridge-helper
> $ rpm -ql libvirt-daemon | grep libexec
> /usr/libexec/libvirt_iohelper
> /usr/libexec/libvirt_lxc
> /usr/libexec/libvirt_parthelper
Is the path user visible in any way?
If used, /usr/libexec/qemu-bridge-helper is encoded directly in the
libvirt XML. So is libvirt_lxc. (So is /usr/libexec/qemu-kvm, on
RHEL).
Not sure about the other two libvirt_* files. It appears that
libvirtd simply runs those.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top