applied, thanks. i pushed a follow up to fix not sending the server on
edit as it's a fixed value in the storage config
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Useful for retrieving flags from default CPU models.
Signed-off-by: Stefan Reiter
---
...E-Add-list-flags-command-line-option.patch | 213 ++
debian/patches/series | 1 +
2 files changed, 214 insertions(+)
create mode 100644
debian/patches/pve/0049-PVE
For supporting a GUI to easily create custom CPU models based on cluster
CPU availability.
Signed-off-by: Stefan Reiter
---
PVE/API2/Qemu/CPU.pm | 86
1 file changed, 86 insertions(+)
diff --git a/PVE/API2/Qemu/CPU.pm b/PVE/API2/Qemu/CPU.pm
index b0b
"originalValue" is set to "null" in case it's the default, but
getValue() returns an empty string. This means that when editing a VM's
CPU config when the model is "default", the form would always be marked
dirty.
Signed-off-by: Stefan Reiter
---
www/manager6/form/CPUModelSelector.js | 6 ++
For someone to pick up, please :)
This is some rather old code I had lying around, rebased and slightly fixed up
to build. Doesn't currently work as intended, but gets somewhat close.
Includes the API (mostly stable AFAICT, only some stuff broken during the time
it was lying around) and the GUI (
Standard API, loosely based on Storage config API code. Uses digests and
'delete'-parameter (parameters not given to an update call are
untouched).
Locking and writing helpers are added to CPUConfig. write_config is
fixed with adding 'type' to every section, otherwise SectionConfig
fails.
Signed-
Supports viewing, deleting, adding and editing existing custom CPU
models. All properties except CPU flags are supported in the editor.
A new control for selecting between different Phys-Bits (default, host,
custom number) is added.
This also seems to be the first use of a non-fa icon in the side
Signed-off-by: Stefan Reiter
---
I believe this one is the most outdated, it's original title in my working
branch was "tmp", dating back to more than a year ago ;)
www/manager6/dc/CPUTypeEdit.js | 8 ++
www/manager6/form/VMCPUFlagSelector.js | 125 -
2 files c
For custom models, this returns the saved configuration, for default
models it returns the cputype, vendor and a list of flags that the guest
OS will see when running with this CPU type (using the -list-flags QEMU
parameter).
For custom models it also includes the digest of the whole config, in
ca
...and typo in name.
Signed-off-by: Stefan Reiter
---
www/manager6/form/VMCPUFlagSelector.js | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/www/manager6/form/VMCPUFlagSelector.js
b/www/manager6/form/VMCPUFlagSelector.js
index ace3c531..a6d17930 100644
--- a/www
When set to false, only default CPU models will be shown.
Signed-off-by: Stefan Reiter
---
www/manager6/form/CPUModelSelector.js | 16
1 file changed, 16 insertions(+)
diff --git a/www/manager6/form/CPUModelSelector.js
b/www/manager6/form/CPUModelSelector.js
index a4d883a4..54
Functionally the same, but now with less crashbugs and memory leaks.
Also includes git tags from upstream, now that it has officially been
included in a PR.
Cleanly rebased from upstream master to v6.1.0, only change is
- "if: CONFIG_VNC"
+ "if: defined(CONFIG_VNC)"
(same for CONFIG_SPICE)
in the
12 matches
Mail list logo
