Reverting the following commits seems to avoid the problem:
47755dae5ca9 UBUNTU: SAUCE: tracing/hyper-v: trace hyperv_mmu_flush_tlb_others() 0aa1395238f7 UBUNTU: SAUCE: x86/hyper-v: support extended CPU ranges for TLB flush hypercalls 5e61aa7ca654 UBUNTU: SAUCE: x86/hyper-v: use hypercall for remote TLB flush
Josh, can you confirm if that works? I built the latest linux-azure with those patches reverted and placed the deb packages at:
http://kernel.ubuntu.com/~mhcerri/azure/golang/002/
The upstream versions of those commits are significantly different. I will backport them and check if the problem still happens.
Reverting the following commits seems to avoid the problem:
47755dae5ca9 UBUNTU: SAUCE: tracing/hyper-v: trace hyperv_ mmu_flush_ tlb_others( )
0aa1395238f7 UBUNTU: SAUCE: x86/hyper-v: support extended CPU ranges for TLB flush hypercalls
5e61aa7ca654 UBUNTU: SAUCE: x86/hyper-v: use hypercall for remote TLB flush
Josh, can you confirm if that works? I built the latest linux-azure with those patches reverted and placed the deb packages at:
http:// kernel. ubuntu. com/~mhcerri/ azure/golang/ 002/
The upstream versions of those commits are significantly different. I will backport them and check if the problem still happens.