This is caused due to another missing config option in linux-kvm, CONFIG_KALLSYMS. Lttng seems to have a bug in which if this symbol is not present, it doesn't include <linux/vmalloc.h>, but...some other code portion make use of that, so voilá hehe
This is caused due to another missing config option in linux-kvm, CONFIG_KALLSYMS. Lttng seems to have a bug in which if this symbol is not present, it doesn't include <linux/vmalloc.h>, but...some other code portion make use of that, so voilá hehe