On Sat, Apr 04, 2009 at 02:52:49PM +0200, Brecht Sanders wrote: Honnestly I don't think anybody ever tried. The only drivers usually compiled on Win32 are remote and possibly test. Basically so far we expected libvirt on Windows to be only a way to access libvirtd remotely. But patches to improve/extend this are as usual welcome ! Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/

On Sat, Apr 04, 2009 at 02:52:49PM +0200, Brecht Sanders wrote: Why do you want to build the Xen driver on Windows ? Windows isn't a Xen host, so it seems rather pointless. For a Windows client all you need to build is the 'remote' driver. Our recommended configure options for a Windows build are: ./configure \ --without-sasl \ --without-avahi \ --without-polkit \ --without-python \ --without-xen \ --without-qemu \ --without-lxc \ --without-uml \ --without-openvz \ --without-libvirtd This gives you a libvirt.so containing the remote client that can talk to libvirtd on any UNIX host. 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 :|