At Tue, 27 May 2025 12:39:43 -0400, Chuck Zmudzinski <frchu...@gmail.com> wrote: Subject: [SOLVED] Re: Xen 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen) > > It is definitely not production ready, but I got it to work with the following > tweaks and hacks. > > boot command used: > > menu=Boot normally with Xen:dev hd2d:;load /netbsd-XEN3_DOM0.gz -c > console=xencons bootdev=wd1;multiboot /xen.gz dom0_mem=2G dom0_max_vcpus=4 > com2=9600,8n1,0x40c0,16,1:0.0 console=com2 cet=no-ibt pv-l1tf=false > > I also needed to pass -c to the NetBSD dom0 kernel so I could disable com* > interactively using userconf at boot time. Without doing this, the NetBSD dom0 > panics when using the serial console for Xen. I could not get the kernel to > invoke userconf to disable com* by any setting in boot.cfg; it was necessary > to pass -c and disable com* interactively at boot time.
That's very strange.
Perhaps it has something to do with the fact you're using what Xen calls
"com2" for the serial console.
Normally when a COM port is used by Xen for the serial console then it
won't even be seen by the probe in NetBSD.
However it doesn't look like you're using an old-fashioned "standard"
COM port. According to the "Xen Serial Console" notes you should
probably be telling Xen to use "com1", not "com2":
Xen com1= option for non-standard serial ports (IPMI SOL, Intel AMT,
PCI serial)
Note that even if your SOL device is, for example, COM3, you
still need to specify "com1=<foo> console=com1" options for Xen.
If you specify "com3=" the serial console won't work! Remember
to list the correct (actual) serial port IOport and IRQ in the
Xen "com1=" parameters!
https://wiki.xenproject.org/wiki/Xen_Serial_Console
> I also needed to interactively set the root device because no bootdev
> setting in boot.cfg allowed the NetBSD dom0 kernel to correctly detect
> the root device.
> 2. I tried passing the bootdev to the NetBSD kernel as wd1, dk12,
> and NAME=<UUID> but it never worked. However, I was able to
> interactively set it at boot time:
That's also very strange. (note "wd1" would probably never be correct
given how it appears your disks are partitioned -- you need "dk12")
What devices does it suggest if you type a "?" at the "root device"
prompt?
It seems like NetBSD/Xen almost never gets the "boot device" correct,
but I've never seen the kernel reject/ignore what seems to be a correct
"bootdev=" option, and then accept the very same name at the prompt.
--
Greg A. Woods <gwo...@acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <wo...@robohack.ca>
Planix, Inc. <wo...@planix.com> Avoncote Farms <wo...@avoncote.ca>
pgpVXrnHnMsY5.pgp
Description: OpenPGP Digital Signature
