Re: booting xen [was Re: serial console puzzle]

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Fri, Apr 30, 2021 at 08:50:10PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 30, 2021 at 07:28:57PM +0100, Patrick Welche wrote:
> > On Fri, Apr 30, 2021 at 07:00:38PM +0200, Manuel Bouyer wrote:
> > > On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> > > > no luck. I see loading /netbsd-XEN3_DOM0, and then it just reboots.
> > > > Nothing more appears on the console. (-current XEN, xen.gz from xenkernel415)
> > > 
> > > Try xen-debug.gz ?
> > > Do you get the Xen boot messages ?
> > 
> > I don't get the Xen boot messages. Just tried xen-debug.gz and again I just
> > see loading, and then a reboot. I don't think it gets as far xen*.gz.
> > 
> > boot.cfg contains:
> > 
> > menu=Boot Xen:rndseed /var/db/entropy-file;consdev com0,57600;load /netbsd-XEN3_
> > DOM0 console=com1 com1=57600,8n1,0x3f8;multiboot /xen-debug.gz dom0_mem=1024M
> 
> should probably be:
> menu=Boot Xen:rndseed /var/db/entropy-file;consdev com0,57600;load /netbsd-XEN3_ DOM0 console=com0;multiboot /xen-debug.gz dom0_mem=1024M console=com1 com1=57600,8n1,0x3f8
> 
> (should really be console=com0 for NetBSD, it doens't access the hardware and
> use the I/O services from the hypervisor)

Ah - I remembered that NetBSD starts at 0, but xen at 1, but clearly still
muddled the boot.cfg.

We now have some serial console output!

Some of what flew by:

(XEN) Xen version 4.15.0nb0 (prlw1@) (gcc (nb1 20210411) 10.3.0) debug=y Thu Ap1
(XEN) Latest ChangeSet:
(XEN) build-id: d2ee973db9f01886c1297a3a469888de162702c6
(XEN) Bootloader: NetBSD/x86 BIOS Boot, Revision 5.11 (Tue Apr 20 14:32:11 UTC )
(XEN) Command line: dom0_mem=1024M console=com1 com1=57600,8n1,0x3f8
(XEN) Xen image load base address: 0
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) CPU Vendor: AMD, Family 16 (0x10), Model 9 (0x9), Stepping 1 (raw 00100f9)
(XEN) Xen-e820 RAM map:
(XEN)  [0000000000000000, 000000000009dfff] (usable)
...
(XEN)   5 disabled
(XEN)   6 disabled
(XEN)   7 disabled
(XEN) TOM2: 001820000000 (WB)
(XEN) Xenoprofile: AMD IBS detected (0x1f)
(XEN) Running stub recovery selftests...
(XEN) Fixup #UD[0000]: ffff82d07fffe040 [ffff82d07fffe040] -> ffff82d04038aa07
(XEN) Fixup #GP[0000]: ffff82d07fffe041 [ffff82d07fffe041] -> ffff82d04038aa07
(XEN) Fixup #SS[0000]: ffff82d07fffe040 [ffff82d07fffe040] -> ffff82d04038aa07
(XEN) Fixup #BP[0000]: ffff82d07fffe041 [ffff82d07fffe041] -> ffff82d04038aa07
(XEN) HPET: 3 timers usable for broadcast (4 total)
(XEN) NX (Execute Disable) protection active
(XEN) Dom0 has maximum 1128 PIRQs
(XEN) *** Building a PV Dom0 ***
(XEN) ELF: not an ELF binary
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Could not construct domain 0
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

$ file /netbsd*
/netbsd:           ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for NetBSD 9.99.82, not stripped
/netbsd-XEN3_DOM0: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for NetBSD 9.99.82, with debug_info, not stripped


(Should we move this to port-xen?)


Cheers,

Patrick