> -----Original Message----- [snip] > > Longer term vision: > > * Have a tiny hypervisor between Guest and Xen that handles the common cases > -> this enables (almost) zero downtime for the guest > -> the tiny hypervisor will maintain the guest while the underlying xen > is kexecing into new > build >
This sounds very much more like a KVM system... The majority of Xen becomes the 'kernel and QEMU' part (i.e. it's the part that boot-straps the system, deals with IOMMU, APICs, etc. and incorporates the scheduler) and the tiny hypervisor is the 'kvm.ko' (deals with basic I/O and instruction emulation traps). Is that the general split you envisage? Paul _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
