Re: Problems booting NetBSD/Xen on Intel NUC 12 Extreme w/ i9-12900

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Manuel Bouyer <bouyer%antioche.eu.org@localhost> writes:

> On Thu, May 11, 2023 at 02:27:51PM -0400, Brad Spencer wrote:
>> Manuel Bouyer <bouyer%antioche.eu.org@localhost> writes:
>> 
>> > On Thu, May 11, 2023 at 12:27:03PM +0200, Johan Stenstam wrote:
>> >> Hi agin,
>> >> 
>> >> > On 11 May 2023, at 08:54, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
>> >> > 
>> >> > On Wed, May 10, 2023 at 10:20:49PM +0200, Johan Stenstam wrote:
>> >> >> 
>> >> >>> On Wed, May 10, 2023 at 03:04:37PM -0400, Greg Troxel wrote:
>> >> >>> 
>> >> >>> AFAIK NetBSD/xen still need separate modules (and I don't think it's going
>> >> >>> to change). But as I don't use modules I don't know how they're supposed
>> >> >>> to be built.
>> >> >> 
>> >> >> Well, I have them (copied from /stand/amd64/ to /stand/amd64-xen/), so either way this should not be the issue.
>> >> > 
>> >> > It is, because modules from /stand/amd64/ and not compatible with
>> >> > /stand/amd64-xen/ (the ABI is not the same)
>> >> 
>> >> Yes, I?ve found that out now. However, note that one of the last messages from the successful boot of XEN3_DOM0 using the serial console was:
>> >> 
>> >> kern.module.path=/stand/amd64/10.0/modules
>> >> 
>> >> So it seems that there is some confusion in the XEN3_DOM0 kernel about the correct path for locating modules.
>> >
>> > Yes, looks like something is wrong here
>> >
>> 
>> [snip]
>> 
>> My understanding, also born out by real installs, indicates that prior
>> to 10.x and -current there was separate modules directories for Xen, the
>> amd64-xen thing.  At 10.x and after, however, that was eliminated and
>> there is only one.  I have a pure PV 10.x guest that appears to work
>> just fine with modules pointing at /stand/amd64/10.0/modules.
>
> There is still lots of code and constant conditional on XENPV in
> arch/x86/include/ and arch/amd64/include/. As long as you modules don't depend
> on theses it's safe. But as these can be #included indirectly it's hard
> to tell what a module uses or doesn't use ...

<Shrug ... don't know...  my own use case appears fine>

Looks like amd64-xen has been gone for 2 years.  The commit that did it
mentions that amd64 and amd64-xen modules were identical (the same
operation was applied to the i386pae and i386pae-xen modules).  Noted
here:

http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/modules/arch/x86/amd64-xen/Attic/Makefile?only_with_tag=MAIN

The Makefile fragment in the Attic appears to only defined XEN and not
XENPV, although I didn't walk the twisted and turning Makefile path
completely, so XENPV may get defined somehow.







-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org