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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, May 10, 2023 at 10:20:49PM +0200, Johan Stenstam wrote:
> Hi Manuel,
> 
> > On 10 May 2023, at 21:31, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
> > 
> > On Wed, May 10, 2023 at 03:04:37PM -0400, Greg Troxel wrote:
> >> Johan Stenstam <johani%johani.org@localhost> writes:
> >> 
> >>> 2. How important is it to keep in exact sync between xenkernelNNN and
> >>> xentoolsMMM? I.e. assuming I get past the current crash and get a
> >>> running system with xenkernel415, is it imperative that I find a
> >>> xentools415 to go with it or would xentools413 be sufficient?
> >> 
> >> I built xentools415 on March 14, as part of testing what was to become
> >> 2023Q1.  The host was netbsd-10 (so 10_BETA). I would recommend testing
> >> with 10 rather than 9 for a new system.
> >> 
> >>> 3. When trying 10_BETA + xenkernel415 I notice that the distribution
> >>> doesn?t include the kernel modules,
> >>> i.e. /stand/amd64-xen/10.0/modules/ is empty. It seems that there is
> >>> no difference in the .kmods between GENERIC and XEN_DOM0 systems, so I
> >>> just copied them over. But it surprises me as one of the things that
> >>> will be much improved with NetBSD 10 is Xen performance, so why then
> >>> isn?t the distribution kit complete?
> >> 
> >> It's a bug that you need separate  modules, and my understanding is that
> >> as of 10, you don't.
> > 
> > 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)

> boot device: ld0
> root on dk1 dumps on dk2
> root file system type: ffs
> kern.module.path=/stand/amd64/10.0/modules
> 
> I have no idea what has caused NetBSD/Xen to think that the boot device is dk0, but that?s clearly where everything goes south.
> 
> Any suggestions?

try
root=dk1 
as argument to NetBSD ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--