Date: Tue, 18 Oct 2022 12:15:28 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: Recently moved to XS 8.2 on new hardware - seen a couple of FreeBSD DomU lock ups? Message-ID: <91CF514F28FADFC45E157B96@[10.12.30.106]> In-Reply-To: <Y0l00fUaRtwIIjJS@Air-de-Roger> References: <3C47F89ECDBA642ACCC7B932@[10.12.30.106]> <Y0l00fUaRtwIIjJS@Air-de-Roger>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 14 October 2022 16:40 +0200 Roger Pau Monn=C3=A9 = <roger.pau@citrix.com>=20 wrote: > Hello, > > Sorry, been very busy this week and forgot to reply earlier. > > Could you try to setup a watchdog in FreeBSD and see if that > triggers? So that we can get an idea of where the guest locks up. Hi - no problem / thanks for the reply... I'll give the above ago - part of the problem is not knowing which VM is=20 going to die (there are quite a few) - the second part, is the waiting=20 game... > Is also the 100% load on all CPUs, or just one? >>From memory of the graphs - I think it was probably just one (I think the=20 last VM that locked was a two core VM). > If the watchdog doesn't work we can try other methods. Well, I'll get back to you when it happens again (personally - I hope it=20 doesn't happen again) - but at least I know it's not quite as much of a=20 dead end as I feared debug wise. If this does happen again - and I'm able, is there any point in doing a=20 snapshot + memory of the VM? (which is about the only thing I could think=20 of - not knowing about the watchdog stuff). -Kp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91CF514F28FADFC45E157B96>