On Thu, Jun 29, 2006 at 05:05:25PM -0400, Joe Lee wrote: > Daniel, thanks for your info and comments below. I really like the > concept and work being done with virt-manager using the libvirt API. > Question: > Is the virt-manager project run by Redhat or yourself?
At the moment its just me working on it - I only put up those web pages a couple of days ago so there isn't anyone else involved. The project was initiated by Red Hat, but as with all our projects we welcome involvement / contribution / feedback from any community members. > In what OS platform will virt-manager run under (Windows, Linux, OS-X) - > Essentially, how cross-platform is it? My primary target at this time is Linux. The application is written in Python with libvirt and GTK / PyGTK being primary dependancies. All the GTK stuff is portable to Windows, and libvirt should be portable too. I'm not sure what GTK OS-X support is like though. So although I'm not testing it on anything other than Linux, it should be possible to make it portable if there were demand. I honestly couldn't estimate the work to port it though, not having any experiance developing for Windows / OS-X Regards, Dan. > -joe > > Daniel P. Berrange wrote: > >On Wed, Jun 28, 2006 at 07:03:31PM -0400, Joe Lee wrote: > > > >>>I would be interested in a GUI that is not specific to QEMU. e.g. Xen/VT, > >>>Basilisk II, SheepShaver, etc. ;-) > >>> > >>Gwenole, can you elaborate more on your comments above. Are your > >>comments referring to having a GUI that can both run and manage several > >>virtualization product (QEMU, XEN, etc) from one central GUI interface? > >>If so, I had a similar thought on this BUT was not sure how possible > >>this was. Would like to hear more on what your thoughts are on this. > >>Anyone else thought and comments to this would be appreciated! > >> > > > >Its entirely feasible if you have a management API to use which supports > >the different virtualization backends. That would allow the GUI to be > >written to a single API, and yet control multiple systems like QEMU, Xen, > >etc. The libvirt project aims to provide such a backend API, currently > >supporting Xen, and a 'mock hypervisor' backend for testing purposes, and > >it would be very desirable to have backends to drive QEMU & VMWare systems. > >While the GUI would no doubt still have some differences in the area of > >hardware /device configuration the bulk of it could be shared by using > >the generic libvirt backend. I've got an early prototype of a Python/GTK > >based GUI for managing VMs via libvirt: > > > > http://people.redhat.com/berrange/virt-manager/ > > > >So if anyone's interested in trying to put together a QEMU backend for > >libvirt the project site is http://libvirt.org/ > > > >Regards, > >Dan. > > -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
