[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH V4 0/5] Introduce Advanced Watch Dog module

From: Jason Wang
Subject: Re: [PATCH V4 0/5] Introduce Advanced Watch Dog module
Date: Wed, 12 Feb 2020 10:56:48 +0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

On 2020/2/11 下午4:58, Zhang, Chen wrote:
-----Original Message-----
From: Jason Wang<address@hidden>
Sent: Monday, January 20, 2020 10:57 AM
To: Zhang, Chen<address@hidden>; Paolo Bonzini
<address@hidden>; Philippe Mathieu-Daudé<address@hidden>;
Cc: Zhang Chen<address@hidden>
Subject: Re: [PATCH V4 0/5] Introduce Advanced Watch Dog module

On 2020/1/19 下午5:10, Zhang, Chen wrote:

Anyone have comments about this module?
Hi Chen:

I will take a look at this series.
Sorry for slow reply due to CNY and extend leave.
OK, waiting your comments~ Thanks~

Two general questions:

- if it can detect more than network stall, it should not belong to /net
This module use network connection status to detect all the issue(Host to 
Guest/Host to Host/Host to Admin...).
The target is more than network but all use network way. So it is looks a 
tricky problem.


- need to convince libvirt guys for this proposal, since usually it's the duty 
upper layer instead of qemu itself

Yes, It looks a upper layer responsibility, but In the cover latter I have 
explained the reason why we need this in Qemu.
  try to make this module as simple as possible. This module give upper layer 
software a new way to connect/monitoring Qemu.
And due to all the COLO code implement in Qemu side, Many customer want to use 
this FT solution without other dependencies,
it is very easy to integrated to real product.

Zhang Chen

I would like to hear from libvirt about such design.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]