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 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.





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