I've been experiencing occasional "hangs" during domU boot where the kernel gets along so just so far and then goes into a silent loop, and this is apparently before ddb can be started. The only thing I continue to observe is the domU uses CPU time about as fast as it possibly can. These are with an amd64 9.99.81 kernel on both dom0 and domU, and with Xen 4.13.2, all running on an older Dell server. Here's a typical console log from a hung domU: [ 1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.0000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.0000000] 2018, 2019, 2020, 2021 The NetBSD Foundation, Inc. All rights reserved. [ 1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.0000000] The Regents of the University of California. All rights reserved. [ 1.0000000] NetBSD 9.99.81 (XEN3_DOMU) #2: Mon Nov 29 20:07:53 PST 2021 [ 1.0000000] woods@xentastic:/build/woods/xentastic/current-amd64-amd64-obj/build/src/sys/arch/amd64/compile/XEN3_DOMU [ 1.0000000] total memory = 4000 MB [ 1.0000000] avail memory = 3855 MB [ 1.0000000] entropy: seed attached as an entropy source (collecting without estimation) [ 1.0000000] entropy: autoconf attached as an entropy source (collecting without estimation) [ 1.0000000] timecounter: Timecounters tick every 1.000 msec [ 1.0000000] entropy: system-power attached as an entropy source (collecting) [ 1.0000000] mainbus0 (root) [ 1.0000000] hypervisor0 at mainbus0: Xen version 4.13.2nb5 [ 1.0000000] hypervisor0: Xen Domain-0: xentastic [ 1.0000000] hypervisor0: features: mmu_pt_update_preserve_ad highmem_assist gnttab_map_avail_bits [ 1.0000000] VIRQ_DEBUG interrupt using event channel 3 [ 1.0000000] vcpu0 at hypervisor0 [ 1.0000000] event_set_handler: id:<NULL>, xname:vcpu0 ipi, handler:(*0xffffffff80202191)(), evtch 4, level 8 [ 1.0000000] event_set_handler: id:xenev0 chan 4, xname:vcpu0 ipi, attaching evtch 4 to VCPU vcpu0 0 [ 1.0000000] vcpu0: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu0: node 0, package 0, core 0, smt 0 [ 1.0000000] vcpu1 at hypervisor0 [ 1.0000000] vcpu1: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu1: node 0, package 0, core 0, smt 0 [ 1.0000000] vcpu2 at hypervisor0 [ 1.0000000] vcpu2: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu2: node 0, package 0, core 0, smt 0 [ 1.0000000] vcpu3 at hypervisor0 [ 1.0000000] vcpu3: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu3: node 0, package 0, core 0, smt 0 [ 1.0000000] vcpu4 at hypervisor0 [ 1.0000000] vcpu4: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu4: node 0, package 0, core 0, smt 0 [ 1.0000000] vcpu5 at hypervisor0 [ 1.0000000] vcpu5: Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, id 0x10676 [ 1.0000000] vcpu5: node 0, package 0, core 0, smt 0 [ 1.0000000] xenbus0 at hypervisor0: Xen Virtual Bus Interface [ 1.0000000] xencons0 at hypervisor0: Xen Virtual Console Driver [ 1.0000000] xencons0: console major 143, unit 0 [ 1.0000000] event_set_handler: id:xenev0 chan 2, xname:xencons0, handler:(*0xffffffff8020f56c)(), evtch 2, level 6 [ 1.0000000] event_set_handler: id:xenev0 chan 2, xname:xencons0, attaching and binding evtch 2 to current VCPU vcpu0 0 [ 1.0000000] xencons0: using event channel 2 [ 1.0000000] entropy: WARNING: extracting entropy too early [ 1.0000000] timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz quality 10000 [ 1.0000030] event_set_handler: id:<NULL>, xname:vcpu0 clock, handler:(*0xffffffff802099f4)(), evtch 5, level 7 [ 1.0000030] event_set_handler: id:xenev0 chan 5, xname:vcpu0 clock, attaching evtch 5 to VCPU vcpu0 0 -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpBvd9zg3f2d.pgp
Description: OpenPGP Digital Signature