From: Laszlo Ersek <lersek@redhat.com>
To: Keir Fraser <keir@xen.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: domain pause vs. watchdog timer
Date: Thu, 13 Oct 2011 19:11:18 +0200 [thread overview]
Message-ID: <4E971BB6.5040700@redhat.com> (raw)
In-Reply-To: <CABCBAB1.32A07%keir@xen.org>
On 10/13/11 16:56, Keir Fraser wrote:
> On 13/10/2011 15:38, "Laszlo Ersek"<lersek@redhat.com> wrote:
>
>> On 10/13/11 16:21, Jan Beulich wrote:
>>>>>> On 13.10.11 at 15:41, Laszlo Ersek<lersek@redhat.com> 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.
next prev parent reply other threads:[~2011-10-13 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:41 domain pause vs. watchdog timer Laszlo Ersek
2011-10-13 14:21 ` Jan Beulich
2011-10-13 14:38 ` Laszlo Ersek
2011-10-13 14:56 ` Keir Fraser
2011-10-13 17:11 ` Laszlo Ersek [this message]
2011-10-13 14:39 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E971BB6.5040700@redhat.com \
--to=lersek@redhat.com \
--cc=JBeulich@suse.com \
--cc=imammedo@redhat.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.