On Mon, Sep 08, 2008 at 09:42:32AM -0700, Yushu Yao wrote: > > > > On 9/8/08 12:17 AM, "Daniel Veillard" <veillard@xxxxxxxxxx> wrote: > > > On Fri, Sep 05, 2008 at 11:43:41AM -0700, Yushu Yao wrote: > >> Thanks Daniel, > >> > >>> Now support for local virtualization (QEmu for example) would be a more > >>> complex issue but probably not much more complex than existing linux > >>> hypervisor support. > >> Why is this more complex? Could you please explain a bit more? > > > > Because that's code which would have to be designed/ported, instead of > > just recompiling completely generic code which has already been ported > > to Windows. > > > >> By the way, with libvirt, can I control a hypervisor without the libvirtd > >> running with root privilege (or even without libvirtd running at all?)? > > > > You should not assume this is possible. > > Just curious, why there is an option "--without-libvirtd" in configure? > (Which actually works and make will not produce libvirtd.exe) The primary use is for people building on Windows, who want to get the libvirt client APIs, but not the server daemon. It lets them managed Linux hosts from Windows. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.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