From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: [ANNOUNCE] Native Linux KVM tool Date: Sun, 03 Apr 2011 13:01:38 +0300 Message-ID: <1301824898.7875.5.camel@jaguar> References: <1301592656.586.15.camel@jaguar> <20110403090149.GI4047@playa.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org To: Alon Levy Return-path: In-Reply-To: <20110403090149.GI4047@playa.redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, 2011-04-03 at 12:01 +0300, Alon Levy wrote: > On Thu, Mar 31, 2011 at 08:30:56PM +0300, Pekka Enberg wrote: > > Hi all, > >=20 > > We=E2=80=99re proud to announce the native Linux KVM tool! > >=20 > > The goal of this tool is to provide a clean, from-scratch, lightwei= ght > > KVM host tool implementation that can boot Linux guest images (just= a > > hobby, won't be big and professional like QEMU) with no BIOS > > dependencies and with only the minimal amount of legacy device > > emulation. > >=20 > > Note that this is a development prototype for the time being: there= 's no > > networking support and no graphics support, amongst other missing > > essentials. >=20 > I've looked at how to add spice to this, the qxl device should be rel= atively > easy to add as it's just another pci device and you already support t= he virtio > block pci device. But to add the spice server library there needs to = be some > simple fd and timer (i.e. select/epoll) event loop, which I see is mi= ssing. Are > you planning on adding something like that? We have kvm__start_timer() in tools/kvm/kvm.c. Can you use that as a base for qxl? Pekka