public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* Re: [pve-devel] Watchdog hardware vor VMS
       [not found] <a21b36832c582c8b193fb9a5567b4d88e0578113.camel@sakisoft.de>
@ 2023-10-03 10:35 ` Thomas Lamprecht
       [not found]   ` <f8f5000438ed61efb2f4df7ae6b932711ea8c933.camel@sakisoft.de>
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Lamprecht @ 2023-10-03 10:35 UTC (permalink / raw)
  To: Sascha Schmidt, pve-devel

Hello!

Am 01/10/2023 um 08:59 schrieb Sascha Schmidt:
> i have the whish to use watchdog inside of VMs.
> I also want to develop this feature for Proxmox.
> Can i go with this or is there a pro / con for?

Proxmox VE already supports setting up a watchdog for virtual machines
emulated by QEMU, it's just not exposed on the web UI as it's a bit of
a niche feature. But you can use the API or CLI to configure one just
fine, for example:

Default model triggering a reset if watchdog isn't updated anymore:

qm set 1010 --watchdog action=reset

A different model doing a power off if guest OS doesn't update the
watchdog anymore:

qm set 1010 --watchdog model=ib700,action=poweroff

cheers,
 Thomas




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [pve-devel] Watchdog hardware vor VMS
       [not found]   ` <f8f5000438ed61efb2f4df7ae6b932711ea8c933.camel@sakisoft.de>
@ 2023-10-03 16:40     ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2023-10-03 16:40 UTC (permalink / raw)
  To: Sascha Schmidt; +Cc: PVE development discussion

Am 03/10/2023 um 12:51 schrieb Sascha Schmidt:
> Am Dienstag, dem 03.10.2023 um 12:35 +0200 schrieb Thomas Lamprecht:
>> Am 01/10/2023 um 08:59 schrieb Sascha Schmidt:
>>> i have the whish to use watchdog inside of VMs.
>>> I also want to develop this feature for Proxmox.
>>> Can i go with this or is there a pro / con for?
>>
>> Proxmox VE already supports setting up a watchdog for virtual machines
>> emulated by QEMU, it's just not exposed on the web UI as it's a bit of
>> a niche feature. But you can use the API or CLI to configure one just
>> fine, for example:
>
> Ive succeed by adding it manually to the conf. It shows not up in the
> Webui. Thats specially the point i want to resolve :) 
> So i can go on with my development ?
> 

Why is a web UI integration required? I'm not outright rejecting doing
so, but I see rather limited value of having this HW exposed in the UI,
as the UI is already rather crowded and that's why I'd like to keep niche
features to API/CLI only, so I'd like to manage your expectations – not
that you do lots of work that then won't get accepted.

Maybe you could open an enhancement request for this over at our
Bugzilla: https://bugzilla.proxmox.com/
I'd then mark it as postponed and comment that others interested in this
should show so by commenting too. If we get a few requests with somewhat
good use cases I'd be easier for me to argue reevaluating this.

Out of interest: What's actually your use case for an emulated QEMU
watchdog? Personally I only use the Linux softdog in VMs.

Oh, and btw. if you decide to develop something please check out our
developer docs, especially the CLA part:
https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright

Thanks!
 Thomas




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-10-03 16:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <a21b36832c582c8b193fb9a5567b4d88e0578113.camel@sakisoft.de>
2023-10-03 10:35 ` [pve-devel] Watchdog hardware vor VMS Thomas Lamprecht
     [not found]   ` <f8f5000438ed61efb2f4df7ae6b932711ea8c933.camel@sakisoft.de>
2023-10-03 16:40     ` Thomas Lamprecht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal