On 17.02.20 06:31, kkabe@xxxxxxxxxxx wrote: > bhe@xxxxxxxxxx sed in <20200217044850.GD4816@MiWiFi-R3L-srv> > >>> Sorry, I roughly went through code, didn't get clue. Not sure if David >>> have idea about it. >>> >>> By the way, may I know why you would like to run i386 guest on Hyper-V? >>> >>> Found people are talking about the 32bit kernel supporting in upstream, >>> below is Linus's point of view. >>> https://lore.kernel.org/linux-fsdevel/CAHk-=wiGbz3oRvAVFtN-whW-d2F-STKsP1MZT4m_VeycAr1_VQ@xxxxxxxxxxxxxx/ >>> > > <offtopic> > Using Hyper-V for testing out a new kernel is convenient and faster > before testing it out on a real i386 machine. > And I do want bugs squashed; meanwhile "hv_balloon.hot_add=0" will be > a workaround. > > I agree HIGHMEM64G (PAE) is going to be a deprecated feature, but I do miss > HIGHMEM4G (needed for 1GB memory support). > </offtopic> > Could it be that we are hotplugging highmem, but when onlining memory, it will be onlined to ZONE_NORMAL and not ZONE_HIGHMEM? That could explain why we fail at random points in time, when somebody stumbles over such a page. -- Thanks, David / dhildenb
