On 04/ 1/15 09:16 PM, Alexey Eromenko wrote:
Basically VirtualBox is going to implement ABI compatible with Hyper V and with KVM on the host side.
Correct. At present, this is providing paravirtualized clock support and a little bit more like spinlocks for KVM guests.
With Hyper-V provider, this should also result in relaxing timer checks within Windows guests, so BSODs like "A clock interrupt was not received on a secondary processor within the allocated time interval" would be avoided.
This also results in slightly less overhead by not having to intercept any guest RDTSC instructions by the hypervisor once the guest has started using the paravirtualized clocks. However, these are difficult to benchmark; you would need very specific workloads triggering a huge amount of TSC reads on SMP VMs.
Regards, Ram.
_______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev
_______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev
