On 18/01/19 14:41, Mark Mielke wrote: > It is useful to understand the risk. However, this is the same risk we > have been successfully living with for several years now, and it seems > abrupt to declare 3.1 and 3.2 as the Qemu version beyond which migration > requires a whole cluster restart whether or not a L2 guest had been, or > will ever be started on any of the guests.
Only if nested was enabled for the kvm_intel module. If you didn't enable it, you didn't see any change with 3.1. Nested was enabled for kvm_amd years ago. It was a mistake, but that's why we didn't add such a blocker for AMD. Paolo
