qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "ligang (P)" <ligang6@huawei.com>
To: "kvm@veger.kernel.org" <kvm@veger.kernel.org>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "openstack-discuss@lists.openstack.org"
	<openstack-discuss@lists.openstack.org>
Subject: watchdog fed successfully event of 6300esb
Date: Mon, 7 Sep 2020 14:04:20 +0000	[thread overview]
Message-ID: <624825e298f94650a7b69f483c9de84d@huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

Hi folks,

I have an question to discuss about the 6300esb watchdog.

I think is it possible that qemu can send an event while the watchdog successfully fed by the vm at the first time.

Here is the situation:

Qemu will send an VIR_DOMAIN_EVENT_ID_WATCHDOG event while watch dog timeout, and if the action of the watchdog in xml of the vm was set to "reset", the vm will be rebooted while timeout.

I have an monitor process that register callback function of the VIR_DOMAIN_EVENT_ID_WATCHDOG event, the callback function will send an alarm to my upper layer monitor platform indicate that the vm is fault, and the cluster deployed business on the vm will isolate the vm by the alarm.

And after the vm rebooted , the monitor process will receive an reboot event and send it to the platform, the upper layer monitor platform will clear the alarm, and business continue to run on the vm.

In most cases ,the watch dog process in vm will feed the watchdog after vm rebooted and all things go back on track.

In some other cases,the guestos may failed to start (in my environment vm start failed by io error), but the reboot event will still be received and the alarm will be cleared and the vm is still fault. So the this may not a good idea to clear the alarm by the reboot event.

So, I think it will be helpful that the qemu can send an event while the watchdog successfully fed by the vm at the first time. So I can exactly know that the guest os go back on running and the watch dog initialized successfully.

Or any other opintion about this situation.

Thanks.


[-- Attachment #2: Type: text/html, Size: 5046 bytes --]

                 reply	other threads:[~2020-09-07 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=624825e298f94650a7b69f483c9de84d@huawei.com \
    --to=ligang6@huawei.com \
    --cc=kvm@veger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=openstack-discuss@lists.openstack.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).