all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Nicolas Frey <n.frey@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager v2 1/4] ui: iso selector: add option to warn about virtio versions with issues
Date: Wed, 26 Aug 2026 13:44:47 +0200	[thread overview]
Message-ID: <3cec4b70-3e06-434d-aa8f-0c9b07252de0@proxmox.com> (raw)
In-Reply-To: <20260826074935.78437-2-n.frey@proxmox.com>

Am 26.08.26 um 9:49 AM schrieb Nicolas Frey:
> based on the known issues as seen on the wiki. If warnVirtio is true,
> the filename is matched against "virtio-win-x.x.x.iso" and checks
> whether the version number in the filename is in any "from - to" version
> range in `virtioIssues`.
> 
> Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
> ---
> changes since v1:
> * use single gettext call for warning message
> * remove the detailed hints about which version to switch to,
>   instead rely on the link to the wiki
> 
>  www/manager6/form/IsoSelector.js | 70 +++++++++++++++++++++++++++++++-
>  1 file changed, 68 insertions(+), 2 deletions(-)
> 
> diff --git a/www/manager6/form/IsoSelector.js b/www/manager6/form/IsoSelector.js
> index b2d94ed3..ba7b6953 100644
> --- a/www/manager6/form/IsoSelector.js
> +++ b/www/manager6/form/IsoSelector.js
> @@ -10,6 +10,7 @@ Ext.define('PVE.form.IsoSelector', {
> 
>      nodename: undefined,
>      insideWizard: false,
> +    warnVirtio: false,

Nit: I'd use a slightly more explicit name "warnVirtioWin" and similarly
for other names below

>      labelWidth: undefined,
>      labelAlign: 'right',
> 
> @@ -63,6 +64,63 @@ Ext.define('PVE.form.IsoSelector', {
>          return me.callParent([disabled]);
>      },
> 
> +    virtioIssues: [
> +        {
> +            from: '0.1.215',
> +            to: '0.1.262',
> +        },
> +        {
> +            from: '0.1.285',
> +            to: '0.1.285',
> +        },
> +    ],
> +
> +    checkVirtioVersion: function (filename) {
> +        let me = this;
> +        let warningBox = me.lookup('virtioWarning');
> +
> +        const compareVersions = (a, b) => {
> +            let pa = a.split('.').map(Number);
> +            let pb = b.split('.').map(Number);
> +            let max = Math.max(pa.length, pb.length);
> +            for (let i = 0; i < max; i++) {
> +                let cmp = (pa[i] || 0) - (pb[i] || 0);
> +                if (cmp !== 0) {
> +                    return cmp;
> +                }
> +            }
> +            return 0;
> +        };
> +
> +        let match = (filename || '').match(/virtio-win[_-](\d+\.\d+\.\d+)/i);
> +        let version = match && match[1];
> +        let issue =
> +            version &&
> +            me.virtioIssues.some(
> +                (i) => compareVersions(version, i.from) >= 0 && compareVersions(version, i.to) <= 0,
> +            );
> +
> +        if (!issue) {
> +            warningBox.setHtml('');

Nit: I think it would be nice to hide the displayfield if there is no
warning.

> +            return;
> +        }
> +
> +        let atag = `<a
> +            href="https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Known_issues"

Typo: the i should be capitalized, i.e. "#Known_Issues"

> +            target="_blank">${gettext('known issues')}</a>`;
> +
> +        warningBox.setHtml(
> +            '<i class="fa fa-exclamation-triangle warning"></i> ' +
> +                Ext.String.format(
> +                    gettext(
> +                        'Version {0} of the VirtIO drivers is known to cause issues. See {1} for more details.',
> +                    ),
> +                    version,
> +                    atag,
> +                ),
> +        );
> +    },
> +
>      referenceHolder: true,
> 
>      items: [
> @@ -105,10 +163,18 @@ Ext.define('PVE.form.IsoSelector', {
>              },
>              allowBlank: false,
>              listeners: {
> -                change: function () {
> -                    this.up('pveIsoSelector').checkChange();
> +                change: function (_field, value) {
> +                    let selector = this.up('pveIsoSelector');
> +                    if (selector.warnVirtio) {
> +                        selector.checkVirtioVersion(value);
> +                    }
> +                    selector.checkChange();
>                  },
>              },
>          },
> +        {
> +            xtype: 'displayfield',

Please use
userCls: 'pmx-hint',
like we do for other warnings. And it should start out as hidden,
otherwise there is suddenly new spacing below all ISO selectors.

> +            reference: 'virtioWarning',
> +        },
>      ],
>  });
> --
> 2.47.3
> 
> 
> 





  reply	other threads:[~2026-08-26 11:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  7:49 [PATCH manager v2 0/4] fix #7801: ui: warn about problematic virtio versions on iso select Nicolas Frey
2026-08-26  7:49 ` [PATCH pve-manager v2 1/4] ui: iso selector: add option to warn about virtio versions with issues Nicolas Frey
2026-08-26 11:44   ` Fiona Ebner [this message]
2026-08-26 13:28     ` Nicolas Frey
2026-08-26  7:49 ` [PATCH pve-manager v2 2/4] ui: cd edit: add `warnVirtio` option to pass to iso selector Nicolas Frey
2026-08-26  7:49 ` [PATCH pve-manager v2 3/4] partially fix #7801: ui: ospanel: warn about problematic virtio versions Nicolas Frey
2026-08-26  7:49 ` [PATCH pve-manager v2 4/4] partially fix #7801: ui: hardware view: " Nicolas Frey
2026-08-26 11:44   ` Fiona Ebner
2026-08-26 13:38     ` Nicolas Frey
2026-08-26 14:09       ` Fiona Ebner
2026-08-27  6:14 ` [PATCH manager v2 0/4] fix #7801: ui: warn about problematic virtio versions on iso select Dominik Csapak
2026-08-27  6:57   ` Nicolas Frey

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=3cec4b70-3e06-434d-aa8f-0c9b07252de0@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=n.frey@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal