On Mon, Mar 22, 2010 at 02:44:57PM +0200, Avi Kivity wrote: > On 03/22/2010 01:39 PM, Ingo Molnar wrote: > >Reality is, the server space never was and never will be self-sustaining in > >the long run (as Novell has found it out with Netware), it is the desktop > >that > >dictates future markets. This is why i find your views about this naive and > >shortsighted. > > > > Yet Linux is gaining ground in the server and embedded space while > struggling on the desktop. Apple is gaining ground on the desktop but > is invisible on the server side (despite having a nice product - Xserve). > > It's true Windows achieved server dominance through it's desktop power, > but I don't think that's what keeping them there now. > > In any case, I'm not going to write a kvm GUI. It doesn't match my > skills, interest, or my employer's interest. If you wish to see a kvm > GUI you have to write one yourself or convince someone to write it > (perhaps convince Red Hat to fund such an effort beyond virt-manager). It is planned to add support for SPICE remote desktop to virt-manager once that matures & is accepted into upstream KVM/QEMU. That will improve the guest/desktop interaction in many ways compared to VNC or SDL, with improved display resolution changing, copy+paste between host & guest, much better graphics performance, etc. Development efforts aren't totally ignoring the desktop, more that they are focusing on remoting guest desktops, rather than interaction host desktop since that's where alot of demand is. This benefits single host desktops scenarios too, since there's alot of overlap in the problems faced there. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
