On Fri, Oct 10, 2008 at 02:32:09PM -0700, Adhyas Avasthi wrote: > I could not really understand this ToDo Item clearly. Does this mean that > libvert can be installed on Windows and then support Windows Hypervisor ? > Please pardon my lack of understanding, but from what I understand libvert > is supposed to be installed on the hypervisor itself (either in DOM0 or in > the kernel that is managing the hardware underneath, etc.) and then > communicated to from the virtual machine manager utility running on another > machine and trying to control VM behavior by communicating to the > hypervisor. And libvert does not support Windows hypervisor yet. So does > this ToDo mean that there is an expected support for Windows Hypervisor? No, the Windows support we are targetting is client-mode only. ie, allow use of libvirt clients to connect to remote Linux hosts running libvirtd. If someone wants to implement a libvirt driver for Hyper-V patches are of course welcome, but its not a high priority for any of the developers I know. > What about VMware hypervisor, then ? Can I install (after some development) > libvert on vmkernel (VMware's hardware managing OS) and then control it from > a virtual machine manager? I am just trying to understand the ToDo item and > possibilities of using libvert. Again we'd like to have someone contribute patches to support VMWare management. Quite a few people have expressed interest in this, but no one yet wrote much if any code. 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