Re: -current doesn't boot on xen

[coypu%sdf.org@localhost]

On Sat, Jan 30, 2021 at 07:07:28PM +0100, Jaromír Doleček wrote:
> In 2017 it might have been relevant to keep v1, but nowadays I'd
> expect all the infra to be new enough to support v2.
> 
> Under what do you actually run this, what is the Dom0?

Here's what a normal boot looks like on NetBSD 9.1:

[     1.000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
[     1.000000]     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
[     1.000000]     2018, 2019, 2020 The NetBSD Foundation, Inc.  All rights reserved.
[     1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[     1.000000]     The Regents of the University of California.  All rights reserved.

[     1.000000] NetBSD 9.1 (XEN3_DOMU) #0: Sun Oct 18 19:24:30 UTC 2020
[     1.000000]         mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/xen/compile/XEN3_DOMU
[     1.000000] total memory = 10071 MB
[     1.000000] avail memory = 9741 MB
[     1.000000] cpu_rng: RDSEED
[     1.000000] timecounter: Timecounters tick every 10.000 msec
[     1.000000] Kernelized RAIDframe activated
[     1.000000] running cgd selftest aes-xts-256 aes-xts-512 done
[     1.000000] mainbus0 (root)
[     1.000000] hypervisor0 at mainbus0: Xen version 4.14.0.88.g1d1d1f53
[     1.000000] hypervisor0: features:  mmu_pt_update_preserve_ad highmem_assist gnttab_map_avail_bits
[     1.000000] VIRQ_DEBUG interrupt using event channel 9
[     1.000000] vcpu0 at hypervisor0
[     1.000000] vcpu0: AMD EPYC 7402P 24-Core Processor               , id 0x830f10
[     1.000000] vcpu0: package 0, core 0, smt 0
[     1.000000] vcpu1 at hypervisor0
[     1.000000] vcpu1: AMD EPYC 7402P 24-Core Processor               , id 0x830f10
[     1.000000] vcpu1: package 0, core 2, smt 0
[     1.000000] vcpu2 at hypervisor0
[     1.000000] vcpu2: AMD EPYC 7402P 24-Core Processor               , id 0x830f10
[     1.000000] vcpu2: package 0, core 4, smt 0
[     1.000000] vcpu3 at hypervisor0
[     1.000000] vcpu3: AMD EPYC 7402P 24-Core Processor               , id 0x830f10
[     1.000000] vcpu3: package 0, core 6, smt 0
[     1.000000] xenbus0 at hypervisor0: Xen Virtual Bus Interface
[     1.000000] xencons0 at hypervisor0: Xen Virtual Console Driver
[     1.000000] xencons0: console major 143, unit 0
[     1.000000] xencons0: using event channel 8
[     1.000000] timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
[     1.000003] timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz quality 10000
[     1.000003] Xen vcpu0 clock: using event channel 11
[     1.000003] Xen vcpu1 clock: using event channel 13
[     1.000003] Xen vcpu2 clock: using event channel 15
[     1.000003] Xen vcpu3 clock: using event channel 17
[     1.910058] xenbus0: using event channel 1
[     1.910058] xenbus: can't get state for device/suspend/event-channel (2)
[     1.910058] xbd0 at xenbus0 id 51712: Xen Virtual Block Device Interface
[     1.922270] xbd0: using event channel 18
[     1.922270] IPsec: Initialized Security Association Processing.
[     1.922270] xbd1 at xenbus0 id 51760: Xen Virtual Block Device Interface
[     1.930573] xbd1: using event channel 19
[     1.930573] unknown type vkbd at xenbus0 id 0 not configured
[     1.940520] xennet0 at xenbus0 id 0: Xen Virtual Network Interface
[     1.940520] xennet0: MAC address aa:00:00:35:c1:72
[     1.954957] xennet0: using event channel 20
[     1.954957] balloon0 at xenbus0 id 0: Xen Balloon driver
[     1.954957] balloon0: current reservation: 10312960 KiB
[     1.960918] xbd0: 120 GB, 512 bytes/sect x 251658240 sectors
[     1.960918] xbd1: 9396 KB, 512 bytes/sect x 18792 sectors
[     1.970077] xennet0: using RX copy mode
[     1.970077] boot device: xbd0
[     1.982501] xenbus: can't get state for device/suspend/event-channel (2)
[     1.990540] root on xbd0a dumps on xbd0b
[     1.990540] Your machine does not initialize mem_clusters; sparse_dumps disabled
[     2.002804] unknown type vkbd at xenbus0 id 0 not configured
[     2.002804] balloon0: new target 10567680 is above max 10312960
[     2.011753] root file system type: ffs
[     2.020091] kern.module.path=/stand/amd64-xen/9.1/modules
[     2.026120] ignore shutdown request: 
[     2.030057] xenbus: can't get state for device/suspend/event-channel (2)
[     2.030057] unknown type vkbd at xenbus0 id 0 not configured

If I ask their interface for more information:

Command result: 
	Virtualization mode: Paravirtualized
	Memory: 10240 MiB
	VCPUs: 4
	Total disk: 120.0 GiB
	Last installed OS: NetBSD 8.2 - 64 bit
	Boot option: PV-GRUB - 64 bit
	Boot arguments: (hd0,0)/boot/grub/menu.lst
	Live migration: enabled


I can give console access to the domU if you'd like to experiment.