Re: NetBSD DomU (PV) hangs on Xen 4.13.1 / NetBSD 9.1

[Matthias Petermann <mp%petermann-it.de@localhost>]

Hi Manuel,

Am 22.12.2020 um 12:04 schrieb Manuel Bouyer:
> Remove the :cdrom, and boot = 'cd'
>
> cdrom type devices are ignored by PV guests (this matches the linux
> behavior) and the dom0 endlessly wait for it to be ready.

Thanks for this explanation. The domain configuration is getting smaller 
now, and my documentation of the details to consider is getting longer 
;-) Was this changed between Xen 4.11 -> 4.13 and/or NetBSD 9.0 -> 
NetBSD 9.1?

I have that now:

name = "builder91"
type="pv"
kernel = "/netbsd-XEN3_DOMU.gz"
memory = 16384
vcpus = 8
vif = [ 'mac=00:16:3E:74:32:42,bridge=bridge0' ]
disk = [
   'phy:/dev/zvol/rdsk/tank0/volumes/builder91,hda,rw',
]

Which results in:

...
[   1.0000000] NetBSD 9.1 (XEN3_DOMU) #0: Sun Oct 18 19:24:30 UTC 2020
[   1.0000000] 
mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/xen/compile/XEN3_DOMU
[   1.0000000] total memory = 16384 MB
[   1.0000000] avail memory = 15854 MB
[   1.0000000] running cgd selftest aes-xts-256 aes-xts-512 done
[   1.0000000] mainbus0 (root)
[   1.0000000] hypervisor0 at mainbus0: Xen version 4.13.1nb1
[   1.0000000] vcpu0 at hypervisor0
[   1.0000000] vcpu0: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu0: package 0, core 3, smt 0
[   1.0000000] vcpu1 at hypervisor0
[   1.0000000] vcpu1: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu1: package 0, core 6, smt 0
[   1.0000000] vcpu2 at hypervisor0
[   1.0000000] vcpu2: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu2: package 0, core 5, smt 0
[   1.0000000] vcpu3 at hypervisor0
[   1.0000000] vcpu3: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu3: package 0, core 1, smt 0
[   1.0000000] vcpu4 at hypervisor0
[   1.0000000] vcpu4: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu4: package 0, core 4, smt 0
[   1.0000000] vcpu5 at hypervisor0
[   1.0000000] vcpu5: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu5: package 0, core 2, smt 0
[   1.0000000] vcpu6 at hypervisor0
[   1.0000000] vcpu6: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu6: package 0, core 0, smt 0
[   1.0000000] vcpu7 at hypervisor0
[   1.0000000] vcpu7: AMD FX(tm)-8350 Eight-Core Processor           , 
id 0x600f20
[   1.0000000] vcpu7: package 0, core 7, smt 0
[   1.0000000] xenbus0 at hypervisor0: Xen Virtual Bus Interface
[   1.0000000] xencons0 at hypervisor0: Xen Virtual Console Driver
[   1.9900269] xenbus: can't get state for device/suspend/event-channel (2)
[   1.9900269] xbd0 at xenbus0 id 768: Xen Virtual Block Device Interface
[   1.9900269] xennet0 at xenbus0 id 0: Xen Virtual Network Interface
[   1.9900269] xennet0: MAC address 00:16:3e:74:32:42
[   1.9900269] balloon0 at xenbus0 id 0: Xen Balloon driver
[   1.9900269] balloon0: current reservation: 16777216 KiB
[   1.9900269] xennet0: using RX copy mode
[   1.9900269] xenbus: can't get state for device/suspend/event-channel (2)
[   1.9900269] balloon0: current reservation: 4194304 pages => target: 
4194304 pages
[   1.9900269] ignore shutdown request:
[   1.9900269] xenbus: can't get state for device/suspend/event-channel (2)

Unfortunately, I can't see a big change.

Kind regards
Matthias