* Andi Kleen <ak at suse.de> wrote: > > VDSO is only a problem if (1) the hypervisor wants to reserve the > > top virtual address space (CONFIG_PARAVIRT=y), and (2) the glibc is > > old and > > It broke the boot even with native hardware, no hypervisor yeah - i just sent the fix for that regression - by making CONFIG_COMPAT_VDSO usable again. basically, we want to avoid all the compatibility mess that exists on the hypervisor side to enter the Linux kernel. Ingo
