From nobody Thu Mar 03 17:03: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 68DA119E05C3 for ; Thu, 3 Mar 2022 17:03:26 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nfbcal.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K8ckj11KLz4XLS for ; Thu, 3 Mar 2022 17:03:24 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (localhost [127.0.0.1]) by nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id 223H3Ij1015194 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 3 Mar 2022 09:03:18 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.2 at lothlorien.nfbcal.org Received: (from buhrow@localhost) by nfbcal.org (8.15.2/8.12.11) id 223H3Hl0004266; Thu, 3 Mar 2022 09:03:17 -0800 (PST) Message-Id: <202203031703.223H3Hl0004266@nfbcal.org> From: Brian Buhrow Date: Thu, 3 Mar 2022 09:03:17 -0800 In-Reply-To: X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Roger Pau =?utf-8?B?TW9ubsOp?= , Ze Dupsys Subject: Re: ZFS + FreeBSD XEN dom0 panic Cc: , buhrow@nfbcal.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nfbcal.org [127.0.0.1]); Thu, 03 Mar 2022 09:03:18 -0800 (PST) X-Rspamd-Queue-Id: 4K8ckj11KLz4XLS X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of buhrow@nfbcal.org designates 157.22.230.125 as permitted sender) smtp.mailfrom=buhrow@nfbcal.org X-Spamd-Result: default: False [-3.29 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:ns.nfbcal.org]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nfbcal.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.993]; MLMMJ_DEST(0.00)[freebsd-xen]; FREEMAIL_TO(0.00)[citrix.com,gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7091, ipnet:157.22.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N 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 hello Roger. I wonder if this leak is related to a bug I ran into a few weeks ago, but didn't investigate. Traditionaly, when I shutdown a domu, I use the xl destroy command because the xl shutdown hasn't been very reliable for me with the domu's I've been using. However, I thought I'd try things out with the new version of Xen plus the newer versions of NetBSD, which was the domu in question for this issue. When I ran the xl shutdown command against the domain, the domain shut down, but didn't disappear from the list of domains when subsequent xl list commands were issued. Worse, following up with an xl destroy against the zombie domain that resulted from the xl shutdown command did nothing. Because this was a production system, I immediately rebooted the dom0 and all the domu hosts in order to assure the corruption didn't spread. this is against Xen-4.14.0 and FreeBSD-12.2. Have you seen this behavior before? -thanks -Brian