1. Is the maximum no. of vcpus in a particular guest limited to the no. of host cpus ? (I guess not)
2. Is there any attempt made to co-schedule all of a guest's vcpus, in order to avoid any spinlock holding problem ? 3. Are there any means to do content-based page sharing between guests as VMware does ? 4. Does kvm makes any attempt to avoid TLB flushes while vm-exits and vm-entries ? like Xen makes a memory hole ? (my guess is that it doesn't needs to as kvm is mapped into a guest's address-space and the pages are protected with the help of linux vm. Am i right ? ) Slightly different ones, 5. How much useful is a balloon driver for kvm, which doesn't makes any hard partitions of available physical memory between the guests ? Shouldn't the linux VM's knowledge be superior in this case than the guest-vm's ? 6. What is coalesced mmio ? -- Regards, Sukanto Ghosh -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
