Date: Thu, 3 Mar 2022 09:03:17 -0800 From: Brian Buhrow <buhrow@nfbcal.org> To: Roger Pau =?utf-8?B?TW9ubsOp?= <roger.pau@citrix.com>, Ze Dupsys <zedupsys@gmail.com> Cc: <freebsd-xen@freebsd.org>, buhrow@nfbcal.org Subject: Re: ZFS + FreeBSD XEN dom0 panic Message-ID: <202203031703.223H3Hl0004266@nfbcal.org> In-Reply-To: <YiCa70%2BHQScsoaKX@Air-de-Roger>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202203031703.223H3Hl0004266>