From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve_flutter_frontend 1/1] fix: qemu: `unknown` status shown when VM is in `prelaunch` status
Date: Tue, 3 Jun 2025 16:56:42 +0200 [thread overview]
Message-ID: <20250603145643.243019-2-s.shaji@proxmox.com> (raw)
In-Reply-To: <20250603145643.243019-1-s.shaji@proxmox.com>
When the VM starts up, if the `Freeze CPU at startup` option value is
set to `true` the VM status is shown as `unknown`. However when testing
the same on web UI, the UI shows the `prelaunch` status when
hovering over the VM.
Additionally the resume option is missing in the app UI, which should
have been found under the power settings. To create feature parity a
new `prelaunch` value has been added in the `PveResourceStatusType`
enum. The new value is used to fix the unknown status and resume
option not being shown.
Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
lib/widgets/pve_qemu_power_settings_widget.dart | 3 ++-
lib/widgets/pve_resource_status_chip_widget.dart | 3 +++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/lib/widgets/pve_qemu_power_settings_widget.dart b/lib/widgets/pve_qemu_power_settings_widget.dart
index e402b83..b4c3c0a 100644
--- a/lib/widgets/pve_qemu_power_settings_widget.dart
+++ b/lib/widgets/pve_qemu_power_settings_widget.dart
@@ -40,7 +40,8 @@ class PveQemuPowerSettings extends StatelessWidget {
),
if ([
PveResourceStatusType.paused,
- PveResourceStatusType.suspended
+ PveResourceStatusType.suspended,
+ PveResourceStatusType.prelaunch,
].contains(qemuStatus) &&
!(state.currentStatus!.template ?? false))
ListTile(
diff --git a/lib/widgets/pve_resource_status_chip_widget.dart b/lib/widgets/pve_resource_status_chip_widget.dart
index c3d3f69..1b0038d 100644
--- a/lib/widgets/pve_resource_status_chip_widget.dart
+++ b/lib/widgets/pve_resource_status_chip_widget.dart
@@ -44,6 +44,9 @@ class StatusChip extends StatelessWidget {
statusColor = intermediateColor;
statusText = 'suspending';
break;
+ case PveResourceStatusType.prelaunch:
+ statusColor = offlineColor;
+ statusText = 'prelaunch';
default:
statusColor = offlineColor;
statusText = 'unknown';
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-03 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:56 [pve-devel] [PATCH proxmox_dart_api_client/pve_flutter_frontend 0/2] fix: ui: `unknown` status shown when the QEMU state is `prelaunch` Shan Shaji
2025-06-03 14:56 ` Shan Shaji [this message]
2025-06-03 14:56 ` [pve-devel] [PATCH proxmox_dart_api_client 1/1] fix: add missing `prelaunch` value to `PveResourceStatusType` Shan Shaji
2025-06-04 11:11 ` [pve-devel] applied: [PATCH proxmox_dart_api_client/pve_flutter_frontend 0/2] fix: ui: `unknown` status shown when the QEMU state is `prelaunch` Dominik Csapak
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=20250603145643.243019-2-s.shaji@proxmox.com \
--to=s.shaji@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.