Hi Michael, Sorry for my mistake.
Indeed, whith extra = 'elevator=noop pti=off' All xen guests boot without a problem. Thanks a lot for your help. Benoît Le mar. 17 juil. 2018 à 01:20, Michael J. Redd <micr...@gmail.com> a écrit : > I've tested the workaround successfully. Added `pti=off` to my kernel's > boot arguments, updated GRUB, and it started as intended. > > Benoît, > > Just to be sure, since you're loading your guests' kernels directly > like that, you're passing pti=off via the `extra` config line in your > domU config files, right? I.e. > > extra = 'elevator=noop pti=off' > > > > On Tue, 2018-07-17 at 00:39 +0200, Benoît Tonnerre wrote: > > Hi, > > > > I tested this workaround : I confirm that it works on Xen host, but > > not on Xen guest. > > If you try to start a vm with latest kernel i.e. theses parameters in > > cfg file : > > > > # > > # Kernel + memory size > > # > > kernel = '/boot/vmlinuz-4.9.0-7-amd64' > > extra = 'elevator=noop' > > ramdisk = '/boot/initrd.img-4.9.0-7-amd64' > > > >