Re: [Xen-devel] xpti=dom0=false doesn't seem to work on 4.8.4

[Karl Johnson <karljohnson.it@xxxxxxxxx>]

On Mon, Jul 16, 2018 at 5:39 AM Jan Beulich <JBeulich@xxxxxxxx> wrote:

>>> On 13.07.18 at 20:54, <karljohnson.it@xxxxxxxxx> wrote:
> Hello,
>
> I'm currently testing last Xen 4.8.4 build for CentOS
> (http://cbs.centos.org/koji/buildinfo?buildID=23169) and disabling
> XPTI for dom0 doesn't seem to work:
>
> (XEN) Command line: dom0_mem=1792M,max:2048M dom0_max_vcpus=4 cpuinfo
> com1=115200,8n1 console=com1,vga xpti=dom0=false loglvl=all
> guest_loglvl=all crashkernel=512M@64M
>
> (XEN)   XPTI (64-bit PV only): Dom0 enabled, DomU enabled
>
> Bug or wrong syntax?

Bug - see https://lists.xenproject.org/archives/html/xen-devel/2018-07/msg01305.html.

Alternatively you could use "xpti=no-dom0" or (I think) "xpti=dom0=false,".

Jan

Is xpti command line broken again on 4.8? I've upgraded to package xen-4.8.4.43.ge52ec4b787-1 which is based on latest staging snapshot and xpti=no-dom0 now seems to disable XPTI for domU:

[root@node-tmp1 ~]# xl dmesg|grep -i xpti
(XEN) Command line: dom0_mem=1792M,max:2048M dom0_max_vcpus=4 cpuinfo com1=115200,8n1 console=com1,vga xpti=no-dom0 crashkernel=512M@64M loglvl=all guest_loglvl=all
(XEN)   XPTI (64-bit PV only): Dom0 disabled, DomU disabled

Karl

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel