On Tue, 2007-03-06 at 21:37 +0100, Ingo Molnar wrote: > maybe i shouldnt call it 'VMI' but 'the paravirt ABI'. I dont mind if > it's the Xen ABI or the VMWare ABI or a mesh of the two - everyone can > map their own internals to that /one/ ABI. I think it's an excellent aim, but it's *HARD*. I rejected this approach earlier because I'm just not smart enough. (Yet?) The Linux side is fairly stable. The hardware side is changing, and the hypervisor side is changing. This means the ABI will churn fairly fast. The hypervisors are very different, which means the ABI will be very wide. We could start with VMI and try to support Xen, KVM and lguest. It would at least give us a better idea of the scope of the problem. But IMHO it's a *huge* job. Rusty. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/virtualization
