From nobody Thu Oct 13 10:00:17 2022 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mp4lG4X53z4fbZq for ; Thu, 13 Oct 2022 10:00:26 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mp4lF6DK5z41kd for ; Thu, 13 Oct 2022 10:00:25 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] by smtp.krpservers.com (8.16.1/8.15.2) with ESMTPSA id 29DA0HPB093174 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 13 Oct 2022 11:00:18 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tdx.co.uk; s=krpdkim; t=1665655218; bh=LahRxEbIi10fixKmdfCkXu8Rs/QmMPV3MMDV/p0WEbk=; h=Date:From:To:Subject; b=lXAHsbco1Q34KEGqab5xAK/8jmv2jWBOPU8UiO3DNm4s4qlXSDQxwlz6yXtKEnMCN hxePqQCe/opaa5Q3ZFPOz1oyklPJOsw65hFsIR81Yi8U0SSlwZF1nD3yW9TzCGPadD 8XjYKuq9mPf6tnlvubl7pVwA5i2Cg09+kQkLZog3BllnuA/Th1Er6lro3Liad42zbD KG2CqaMQ1r9Reab5VehVN4v4KPOVT1LafNS5+6ZWkfPihMz1+iEL4eLLIRYxgyIWsg N/wCW/QiWfbCmsjERQvuanKb9u1OOj2z4QiVZQyjWHdVF+t+gG4W9Py9VBSC5DeNMx 58bxcz90BMhVw== Date: Thu, 13 Oct 2022 11:00:17 +0100 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: Recently moved to XS 8.2 on new hardware - seen a couple of FreeBSD DomU lock ups? Message-ID: <3C47F89ECDBA642ACCC7B932@[10.12.30.106]> X-Mailer: Mulberry/4.0.8 (Win32) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Rspamd-Queue-Id: 4Mp4lF6DK5z41kd X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tdx.co.uk header.s=krpdkim header.b=lXAHsbco; dmarc=pass (policy=none) header.from=tdx.co.uk; spf=pass (mx1.freebsd.org: domain of kpielorz_lst@tdx.co.uk designates 62.13.128.145 as permitted sender) smtp.mailfrom=kpielorz_lst@tdx.co.uk X-Spamd-Result: default: False [-0.52 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(0.98)[0.981]; DMARC_POLICY_ALLOW(-0.50)[tdx.co.uk,none]; MID_RHS_IP_LITERAL(0.50)[]; R_SPF_ALLOW(-0.20)[+a:smtp.krpservers.com]; R_DKIM_ALLOW(-0.20)[tdx.co.uk:s=krpdkim]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-xen@freebsd.org]; ASN(0.00)[asn:60969, ipnet:62.13.128.0/24, country:GB]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[tdx.co.uk:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-xen@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi all, We've been running FreeBSD as a DomU under Xen Server for years now, and only really had a few now 'known' issues (e.g. with networking). We've recently setup XS 8.2 on some new Dell servers, and whilst everything appears fine - twice now in a couple of weeks we've had FreeBSD DomU's just "lock up". There's no errors logged, no kernel panic, nothing - they just "stop". Xen reckons the CPU is pegged at 100% (with brief periods of zero) - the console is still 'available' (but locked up) - and the kernel is dead (i.e. you cannot ping it). Aside from the "Has anyone else seen similar" - with nothing in the logs, no panic, nothing - I'm kind of at a loss as to how best to troubleshoot this further? The VM's are lightly loaded - haven't run out of resources (RAM /CPU etc.) - and it's only happened a couple of times now (but in a couple of weeks) - whereas our setup before never experienced this in it's lifetime. One was a legacy 11.4 system (amd64) - the other was a 12.3 system (amd64). A forced reboot brings them back (with some file system damage - as you'd expect from a crash). Just at a loss as to where to look - given the lack of any panic/errors etc. Any suggestions? Regards, -Karl