From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laszlo Ersek Subject: Re: domain pause vs. watchdog timer Date: Thu, 13 Oct 2011 19:11:18 +0200 Message-ID: <4E971BB6.5040700@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Igor Mammedov , "xen-devel@lists.xensource.com" , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 10/13/11 16:56, Keir Fraser wrote: > On 13/10/2011 15:38, "Laszlo Ersek" wrote: > >> On 10/13/11 16:21, Jan Beulich wrote: >>>>>> On 13.10.11 at 15:41, Laszlo Ersek wrote: >>>> if a domain is paused (= not scheduled), its process that keeps >>>> otherwise kicking /dev/watchdog and (thusly the hypervisor) "freezes" >>>> too. Should pausing a domain suspend (or "inactivate") its watchdog_timers? >>> >>> I would say yes it should. And you say it doesn't? >> >> I must have missed a changeset (or a hunk?) related to pausing: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=742880#c1 >> >> I backported 21529 from xen-unstable to the RHEL-5 hypervisor version, >> and Igor tested pausing a Fedora 16 HVM guest. The domU was destroyed >> while it was paused. > > You are just as likely to upset a watchdog implemented entirely internally > to the guest, and which we have no chance to disable/suspend when a domain > is paused. Domain pausing from the dom0 command line really doesn't have a > production use case afaik -- just don't do it is my helpful suggestion. Thank you both for the answers. L.