[GH-ISSUE #31] Minor issues and feature suggestions after lab testing (2 nodes + iSCSI storage)

kerem commented

2026-03-02 15:47:18 +03:00

Owner

Originally created by @ThibautBascoulergue on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/31

Originally assigned to: @mkellermann97 on GitHub.

Hi,

First of all, congratulations on PegaProx — I’ve set up a small lab to test it (2 nodes with iSCSI-backed storage), and overall the tool is really impressive.
Compared to the current Proxmox Datacenter experience, the UI, usability, and global approach are excellent. Great job.

During my tests, I noticed a few minor issues and potential improvements that I wanted to share.

1 - VM Console issue when moving the window

When opening a VM console and moving the console window (for example, dragging it to a second screen on my local workstation), the SSH/WebSocket connection sometimes goes into an error state and disconnects.

It doesn’t seem like a major issue, but it’s reproducible in my lab and might be related to window focus, resolution change, or WebSocket handling on the client side.

2 - iSCSI storage rescan / LUN resize functionality

My storage setup is:

iSCSI target

LUNs presented to the nodes

LVM on top of iSCSI (classic Proxmox-style setup)

Currently, I have:

LUN_0: 4 TB

LUN_1: 2 TB → later extended to 4 TB on the storage array side

It would be really useful to have a storage rescan / resize button, similar to what exists in VMware environments, to:

Rescan iSCSI LUNs

Detect size changes

Optionally assist with extending the underlying LVM

I don’t know if this is already planned or technically feasible in PegaProx, but from a Proxmox/LVM perspective it should be possible:

rescan SCSI devices

resize PV

extend VG/LV if applicable

This would greatly improve day-2 operations when storage capacity is increased on the array side.

Another issue, the content of the LUN is not displaying.

3 - Storage High Availability behavior

I noticed there is a Storage Balancing feature, but I’m not sure how storage failures are handled in HA scenarios.

Example question:

If one node temporarily loses access to the shared storage (iSCSI path down, network issue, etc.), does the HA system:

detect the storage failure?

restart affected VMs on another node that still sees the storage?

In other words, is there HA logic tied to storage availability, or is it mainly focused on compute node failures?

A bit more clarification on this point would be very helpful.

4 - Global CPU Compatibility policy for VM creation

It would be very useful to have the ability to define a global CPU Compatibility policy for VM creation.

Example:

A checkbox or setting like “force this CPU compatibility recommendation”

Once enabled, this CPU model / compatibility level would be applied by default to all future VM creations

This would be particularly helpful in multi-node clusters with heterogeneous CPUs, to avoid configuration drift and ensure VM mobility and compatibility without relying on manual selection for each VM.

5 - Automation tasks edition

In the Automation section, it currently doesn’t seem possible to edit an existing task (for example, a snapshot task).
To modify a task, it must be deleted and recreated entirely.

Being able to edit existing automation tasks would significantly improve usability, especially when fine-tuning schedules or parameters in production environments.

To give some context, I work in the healthcare sector, where infrastructure stability and availability are critical. We currently operate three Proxmox clusters in production, and based on the first results, we plan to test PegaProx more intensively in the coming weeks.

Again, great work on the project — PegaProx looks extremely promising, and I’m looking forward to evaluating it further.

Best regards,
— A very motivated tester 😄

Originally created by @ThibautBascoulergue on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/31 Originally assigned to: @mkellermann97 on GitHub. Hi, First of all, congratulations on PegaProx — I’ve set up a small lab to test it (2 nodes with iSCSI-backed storage), and overall the tool is really impressive. Compared to the current Proxmox Datacenter experience, the UI, usability, and global approach are excellent. Great job. During my tests, I noticed a few minor issues and potential improvements that I wanted to share. **1 - VM Console issue when moving the window** When opening a VM console and moving the console window (for example, dragging it to a second screen on my local workstation), the SSH/WebSocket connection sometimes goes into an error state and disconnects. It doesn’t seem like a major issue, but it’s reproducible in my lab and might be related to window focus, resolution change, or WebSocket handling on the client side. **2 - iSCSI storage rescan / LUN resize functionality** My storage setup is: iSCSI target LUNs presented to the nodes LVM on top of iSCSI (classic Proxmox-style setup) Currently, I have: LUN_0: 4 TB LUN_1: 2 TB → later extended to 4 TB on the storage array side <img width="398" height="392" alt="Image" src="https://github.com/user-attachments/assets/c86dee39-e672-4024-9a32-be802b34a241" /> It would be really useful to have a storage rescan / resize button, similar to what exists in VMware environments, to: Rescan iSCSI LUNs Detect size changes Optionally assist with extending the underlying LVM I don’t know if this is already planned or technically feasible in PegaProx, but from a Proxmox/LVM perspective it should be possible: rescan SCSI devices resize PV extend VG/LV if applicable This would greatly improve day-2 operations when storage capacity is increased on the array side. Another issue, the content of the LUN is not displaying. **3 - Storage High Availability behavior** I noticed there is a Storage Balancing feature, but I’m not sure how storage failures are handled in HA scenarios. Example question: If one node temporarily loses access to the shared storage (iSCSI path down, network issue, etc.), does the HA system: detect the storage failure? restart affected VMs on another node that still sees the storage? In other words, is there HA logic tied to storage availability, or is it mainly focused on compute node failures? A bit more clarification on this point would be very helpful. **4 - Global CPU Compatibility policy for VM creation** It would be very useful to have the ability to define a global CPU Compatibility policy for VM creation. Example: A checkbox or setting like “force this CPU compatibility recommendation” Once enabled, this CPU model / compatibility level would be applied by default to all future VM creations This would be particularly helpful in multi-node clusters with heterogeneous CPUs, to avoid configuration drift and ensure VM mobility and compatibility without relying on manual selection for each VM. **5 - Automation tasks edition** In the Automation section, it currently doesn’t seem possible to edit an existing task (for example, a snapshot task). To modify a task, it must be deleted and recreated entirely. Being able to edit existing automation tasks would significantly improve usability, especially when fine-tuning schedules or parameters in production environments. To give some context, I work in the healthcare sector, where infrastructure stability and availability are critical. We currently operate three Proxmox clusters in production, and based on the first results, we plan to test PegaProx more intensively in the coming weeks. Again, great work on the project — PegaProx looks extremely promising, and I’m looking forward to evaluating it further. Best regards, — A very motivated tester 😄

kerem

2026-03-02 15:47:18 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 1, 2026):

Hi @ThibautBascoulergue ,

First of all, thank you so much for the kind words and the detailed feedback – it's really appreciated! Great to hear that PegaProx is making a good impression in your lab environment.

Let me go through your points:

1 – VM Console issue when moving the window
Unfortunately, this is a limitation on the Proxmox side – they don't provide a resize function for the console, so we're unable to address this from our end.

2 – iSCSI storage rescan / LUN resize functionality
We've looked into this, but there's no native Proxmox API for this functionality. We'd have to handle it via SSH, which gets tricky across different environments and setups. It's not something we can reliably implement at this point as everyone has here diffrent setups, but we'll keep it in mind.

3 – Storage High Availability behavior
To clarify: Storage High Availability is not currently part of PegaProx. Our HA feature focuses on node failures (auto-restart VMs on node failure). Similar to the iSCSI point above, implementing reliable storage-based HA is difficult due to the variety of different setups out there. Also worth noting – our Storage Balancing feature is still marked as experimental.

4 – Global CPU Compatibility policy
We will evaluate this.

5 – Automation tasks edition
You're right – currently tasks need to be deleted and recreated. We agree this isn't ideal, and editing existing tasks is something we're planning to improve.

Thanks again for taking the time to test PegaProx so thoroughly. Feedback like this really helps us improve.

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 1, 2026): Hi @ThibautBascoulergue , First of all, thank you so much for the kind words and the detailed feedback – it's really appreciated! Great to hear that PegaProx is making a good impression in your lab environment. Let me go through your points: 1 – VM Console issue when moving the window Unfortunately, this is a limitation on the Proxmox side – they don't provide a resize function for the console, so we're unable to address this from our end. 2 – iSCSI storage rescan / LUN resize functionality We've looked into this, but there's no native Proxmox API for this functionality. We'd have to handle it via SSH, which gets tricky across different environments and setups. It's not something we can reliably implement at this point as everyone has here diffrent setups, but we'll keep it in mind. 3 – Storage High Availability behavior To clarify: Storage High Availability is not currently part of PegaProx. Our HA feature focuses on node failures (auto-restart VMs on node failure). Similar to the iSCSI point above, implementing reliable storage-based HA is difficult due to the variety of different setups out there. Also worth noting – our Storage Balancing feature is still marked as experimental. 4 – Global CPU Compatibility policy We will evaluate this. 5 – Automation tasks edition You're right – currently tasks need to be deleted and recreated. We agree this isn't ideal, and editing existing tasks is something we're planning to improve. Thanks again for taking the time to test PegaProx so thoroughly. Feedback like this really helps us improve. Regards, Marcus

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@ThibautBascoulergue commented on GitHub (Feb 1, 2026):

I think there is also a small bug when adding a node to a cluster.

@ThibautBascoulergue commented on GitHub (Feb 1, 2026): I think there is also a small bug when adding a node to a cluster. <img width="513" height="550" alt="Image" src="https://github.com/user-attachments/assets/04e13c1d-bfd8-4063-9f52-3fcb2c43fadc" />

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 4, 2026):

Hi @ThibautBascoulergue ,

Thanks for reporting this – it's now fixed in the latest version that is upcoming.

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 4, 2026): Hi @ThibautBascoulergue , Thanks for reporting this – it's now fixed in the latest version that is upcoming. Regards, Marcus

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@ThibautBascoulergue commented on GitHub (Feb 4, 2026):

Nice, thanks !

@ThibautBascoulergue commented on GitHub (Feb 4, 2026): Nice, thanks !

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 9, 2026):

Hi @ThibautBascoulergue ,

please update PegaProx to the newest version.

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 9, 2026): Hi @ThibautBascoulergue , please update PegaProx to the newest version. Regards, Marcus

kerem commented

2026-03-02 15:47:19 +03:00

Author

Owner

@DannyD25 commented on GitHub (Feb 25, 2026):

my pegaprox install is not restarting my vm's are lxc containers.

@DannyD25 commented on GitHub (Feb 25, 2026): my pegaprox install is not restarting my vm's are lxc containers.

Rows
Columns

[GH-ISSUE #31] Minor issues and feature suggestions after lab testing (2 nodes + iSCSI storage) #24