Re: port-xen/53965: XEN DomU fails to poweroff in new HEAD kernels

[Cherry G.Mathew <cherry%zyx.in@localhost>]

Greg Oster <oster%netbsd.org@localhost> writes:

> On Sat, 9 Feb 2019 11:47:41 -0600
> Greg Oster <oster%netbsd.org@localhost> wrote:
>
>> On Sat,  9 Feb 2019 17:35:01 +0000 (UTC)
>> Robert Elz <kre%munnari.OZ.AU@localhost> wrote:
>> 
>> > The following reply was made to PR port-xen/53965; it has been noted
>> > by GNATS.
>> > 
>> > From: Robert Elz <kre%munnari.OZ.AU@localhost>
>> > To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>> > Cc: gnats-bugs%NetBSD.org@localhost, port-xen-maintainer%netbsd.org@localhost,
>> >         gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
>> > Subject: Re: port-xen/53965: XEN DomU fails to poweroff in new HEAD
>> > kernels Date: Sun, 10 Feb 2019 00:29:48 +0700
>> > 
>> >      Date:        Sat, 9 Feb 2019 17:36:37 +0100
>> >      From:        Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>> >      Message-ID:  <20190209163637.GA3729%antioche.eu.org@localhost>
>> >  
>> >  Thanks for the reply.
>> >  
>> >    | I wonder if it could be related to the recent Xen API version
>> > bump in our | source tree
>> >  
>> >  If you could point me to an approximate time that happened, I could
>> >  try before and after kernels and see.  
>> 
>> Just tried a kernel from Jan 11, 2019, and it rebooted without
>> incident....  Going to test a Jan 19 kernel next...
>>
>
> A kernel from Jan 31 works, but a kernel from Feb 3 doesn't.  The 
>
>  Switch NetBSD/xen to use XEN api tag RELEASE-4.11.1
>
> happened on Feb 2....  Next question is: how to fix..
>

The problem is that we use the sched_op hypercall with what is now
sched_op_compat arguments.

I'm working on a fix, will commit it later today.

Thanks for the alert.

-- 
~cherry