public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Sascha Schmidt <sascha@sakisoft.de>
Cc: PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] Watchdog hardware vor VMS
Date: Tue, 3 Oct 2023 18:40:27 +0200	[thread overview]
Message-ID: <a0eff2cc-e2ee-455c-8e11-636881ed9b68@proxmox.com> (raw)
In-Reply-To: <f8f5000438ed61efb2f4df7ae6b932711ea8c933.camel@sakisoft.de>

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




      parent reply	other threads:[~2023-10-03 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a21b36832c582c8b193fb9a5567b4d88e0578113.camel@sakisoft.de>
2023-10-03 10:35 ` Thomas Lamprecht
     [not found]   ` <f8f5000438ed61efb2f4df7ae6b932711ea8c933.camel@sakisoft.de>
2023-10-03 16:40     ` Thomas Lamprecht [this message]

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=a0eff2cc-e2ee-455c-8e11-636881ed9b68@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@pve.proxmox.com \
    --cc=sascha@sakisoft.de \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal