On Thu, Aug 16, 2007 at 05:01:42PM +0200, Jernej Simon?i? wrote: > On Thursday, August 16, 2007, 15:49:14, Paul Brook wrote: > > > Mainly because the kernel already has one perfectly good virtualization > > interface. > > Weren't both Xen and lguest recently merged to the (upcoming) 2.6.23 > kernel?
They're different to this scenario. Xen & lguest are Host <-> Guest ABIs, and both ultimately use the common paravirt_ops API inside the kernel. kqemu & kvm are Host Kernel <-> Host Userspace APIs, which are completely different, sharing no commonality in their APIs. kqemu stands very little chance getting merged unless it can share its userspace API model with KVM. This would have the added advantage that the QEMU binary would only need to talk one protocol to the kernel too, removing the need for the fork between plain QEMU & KVM-ified QEMU. 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 -=|
