From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fw3hZ-0006oD-Kg for qemu-devel@nongnu.org; Thu, 29 Jun 2006 17:05:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fw3hX-0006mH-Qx for qemu-devel@nongnu.org; Thu, 29 Jun 2006 17:05:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fw3hX-0006m9-Kj for qemu-devel@nongnu.org; Thu, 29 Jun 2006 17:05:27 -0400 Received: from [64.233.184.235] (helo=wr-out-0506.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fw3uA-0005zm-FX for qemu-devel@nongnu.org; Thu, 29 Jun 2006 17:18:30 -0400 Received: by wr-out-0506.google.com with SMTP id i23so163579wra for ; Thu, 29 Jun 2006 14:05:26 -0700 (PDT) Message-ID: <44A44095.8080508@gmail.com> Date: Thu, 29 Jun 2006 17:05:25 -0400 From: Joe Lee MIME-Version: 1.0 Subject: Re: [Qemu-devel] QEMU GUI References: <44998BB7.2060402@bellard.org> <3B232C36-6014-4472-BA4C-452ABAB526C9@kberg.ch> <48969.203.185.161.115.1151004763.squirrel@imaps.mandriva.com> <44A30AC3.5060104@gmail.com> <20060629131917.GA29611@redhat.com> In-Reply-To: <20060629131917.GA29611@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: joelee724@gmail.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: qemu-devel@nongnu.org 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? In what OS platform will virt-manager run under (Windows, Linux, OS-X) - Essentially, how cross-platform is it? -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. >