On 23/01/20 19:04, Ben Gardon wrote: > KVM creates internal memslots covering the region between 3G and 4G in > the guest physical address space, when the first vCPU is created. > Mapping this region before creation of the first vCPU causes vCPU > creation to fail. Prohibit tests from creating such a memslot and fail > with a helpful warning when they try to. > > Signed-off-by: Ben Gardon <bgardon@xxxxxxxxxx> > --- The internal memslots are much higher than this (0xfffbc000 and 0xfee00000). I'm changing the patch to block 0xfe0000000 and above, otherwise it breaks vmx_dirty_log_test. Paolo
