thanks a lot for your reply, Philipp and Daniel
I think I almost figure it out.
When libvirtd get control message(is it should called "a event"?) in
event loop thread
from virsh(for example), in the event loop thread it push the message
to a message queue,
then let worker threads to do the real
On Fri, Feb 25, 2011 at 03:24:06PM +0100, Philipp Hahn wrote:
> Hello,
>
> Am Freitag 25 Februar 2011 14:33:31 schrieb fengzi.gg:
> > 1. Is libvirtd necessary when I use some tools(based on libvirt)
> > to control domains?
>
> Yes, libvirt ist designed to (almost) always require a running lib
Hello,
Am Freitag 25 Februar 2011 14:33:31 schrieb fengzi.gg:
> 1. Is libvirtd necessary when I use some tools(based on libvirt)
> to control domains?
Yes, libvirt ist designed to (almost) always require a running libvirtd. Even
when using session Qemu domains, one daemon gets forked for the
hello, everyone
I am now reading the souce code of libvirtd and virsh, and got some
questions:
1. Is libvirtd necessary when I use some tools(based on libvirt)
to control domains?
2. It seems that virsh use remote driver to comunicate to libvirtd (the
hypervisor is qemu),
why doesn't it
