On Mon, Nov 5, 2012 at 8:58 PM, Hu Tao <hu...@cn.fujitsu.com> wrote: > But in the case of panic notification, more dependency means more > chances of failure of panic notification. Say, if we use a virtio device > to do panic notification, then we will fail if: virtio itself has > problems, virtio for some reason can't be deployed(neither built-in or > as a module), or guest doesn't support virtio, etc.
Add polling to your virtio device. If it didn't notify of a panic but taking more than 20 sec to answer your poll request you can assume it's dead. Actually, just use virtio-serial and something in userspace on the guest. > We choose IO because compared to virtio device, it is not that heavy and > less problematic. Less problematic? Heavy? Are there any known issues with virtio that should be fixed? You make virtio sound like an old IDE drive or something. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
