On Tue, 2023-09-19 at 14:03 +0200, pi3.14@tuta.io wrote:

Hello,

Is it possible to use virtual hardware watchdog in Windows VMs? I am emulating the "i6300esb" with QEMU in Linux instances and  everything works as expected. But when creating Windows  instances, this device does not show up in the device manager.

so upstream does not generally provide any support for workload runing on openstakc inclduing the os. the watchdog device model is not currently expsoted as a tunable via a flavor or image property so configurign it is not currently supprot by nova. it is hardcoded to i6300esb so if your windows guest does not have the correct dirver then it wont work. https://github.com/openstack/nova/blob/master/nova/virt/libvirt/config.py#L2... it looks like libvirt does supprot other models https://libvirt.org/formatdomain.html#watchdog-devices and 'itco'is included by default with q35 machine type Since 9.1.0 but its still not clear if windows would even supprot that if we were to make this configurable you could try setting the machine type to q35 see if that works for you """ Having multiple watchdogs is usually not something very common, but be aware that this might happen, for example, when an implicit watchdog device is added as part of another device. For example the iTCO watchdog being part of the ich9 southbridge, which is used with the q35 machine type. Since 9.1.0 """ im not sure if the watchdog action would affect the implict iTCO watchdog or not the default is 'reset' - default, forcefully reset the guest

- Has anyone tried/tested this before? 

- Is this supported? offically we support exposing a watchdog device to a guest but that is where our supprot ends. upstream nova does not provide support for the integration fo a watchdong in any given os. - Are additional drivers needed?

this is not test upstream or downstream we have no windows guest testing upstream and this is not an offically supported fature in redhats downstream although it not offically unsupproted meaning you can use it if it works for your use case but we do not test it with any sepecic os. this is likely the issue you are encountering windows is proably misssing the i6300esb driver

- I found the following old bug. Has anything changed since then or are there still no suitable drivers? https://bugzilla.redhat.com/show_bug.cgi?id=610063

quickly googleing i dont see refence to one so i woudl assume tha tis still the case