[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] questions about libvirtd and virsh


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 running user.

> 2. It seems that virsh use remote driver to comunicate to libvirtd (the
> hypervisor is qemu), why doesn't it call libvirt directly?

libvirtd often runs as root to keep the required privileges to configure the 
network, start domains, mount storage pools, etc.

> 4. libvirtd has 7 threads, what are these threads doing?

I thinks they wait for work to arrive: 1 is accepting new connections, 1 runs 
the event loop and 5 (configurable) wait for work to be pushed to the 
internal work queue.

Philipp Hahn           Open Source Software Engineer      hahn univention de
Univention GmbH        Linux for Your Business        fon: +49 421 22 232- 0
Mary-Somerville-Str.1  28359 Bremen                   fax: +49 421 22 232-99
** Besuchen Sie uns auf der CeBIT in Hannover **
** Auf dem Univention Stand D36 in Halle 2    **
** Vom 01. bis 05. März 2011                  **

Attachment: signature.asc
Description: This is a digitally signed message part.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]