Most importantly the first one "Revert "monitor: use
aio_co_reschedule_self()"", fixing a crash when doing hotplug+resize
with a disk using io_uring.
Other fixes (likely not too important) for TCG emulation of x86(_64)
and ARM.
Signed-off-by: Fiona Ebner
---
...t-monitor-use-aio_co_reschedule_s
When disabling the nftables firewall again, there is a race condition
where the nftables ruleset never gets flushed and persists after
disabling. In practice this almost never happens due to pve-firewall
running every 10 seconds, and proxmox-firewall running every 5
seconds, so the proxmox-firewall
ping.
Its not possible to build proxmox-perl-rs at the moment without this
patch series.
Lukas Wagner writes:
> These changes adapts the PVE notification stack to the changes introduced
> in proxmox-notify 0.4.
>
> The notification system uses handlebar templates to render the subject
> and t
add documentation for the "[PATCH qemu-server] config: QEMU AMD SEV
enable" patch.
Signed-off-by: Markus Frank
---
qm.adoc | 103
1 file changed, 103 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 42c26db..2001bd4 100644
--- a/qm.adoc
Patch series to enable AMD Secure Encrypted Virtualization (SEV)
https://www.amd.com/en/developer/sev.html
changes v11:
* removed systemd service and added run_command in qemu-server instead
* moved SEV related code to CPUConfig
* instead of the no-debug and no-key-sharing checkboxes there are no
This patch is for enabling AMD SEV (Secure Encrypted Virtualization)
support in QEMU.
VM-Config-Examples:
amd_sev: type=std,no-debug=1,no-key-sharing=1
amd_sev: es,no-debug=1,kernel-hashes=1
kernel-hashes, reduced-phys-bits & cbitpos correspond to the variables
with the same name in QEMU.
kernel
By adding a new input panel with an AMD SEV technology selection combo
box and checkboxes for the optional parameters in an advanced section,
the user can configure the amd_sev option via the WebUI's Options tab.
Signed-off-by: Markus Frank
---
changes v11:
* instead of the no-debug and no-key-sh
The function checks for resources that cannot be migrated, snapshoted,
or suspended.
Signed-off-by: Markus Frank
---
changes v11:
* this patch is new to v11
PVE/API2/Qemu.pm | 5 -
PVE/QemuMigrate.pm | 2 +-
PVE/QemuServer.pm | 23 ++-
3 files changed, 27 insertions
Implement a C program that extracts AMD SEV hardware information such
as reduced-phys-bios and cbitpos from CPUID at boot time, looks if
SEV, SEV-ES & SEV-SNP are enabled, and outputs these details as JSON
to /run/qemu-server/host-hw-capabilities.json
This programm can also be used to read and sav
Superseded by version 2, which correctly prefixes the repositories the patches
must be applied to:
https://lists.proxmox.com/pipermail/pve-devel/2024-May/064024.html
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-b
This patch series defines the vzdump configuration description as well
as backup job configuration option in the WebUI to set the
experimental `change-detection-mode` parameter to the
proxmox-backup-client invocation for container backups having a Proxmox
Backup Server storage target.
This allows
Allows to switch the backup clients change detection mode based on
the option set in the backup jobs configuration for backup jobs with
Proxmox Backup Server target.
Signed-off-by: Christian Ebner
---
changes since version 1:
- no changes
src/PVE/VZDump/LXC.pm | 2 ++
1 file changed, 2 insertio
The proxmox backup client allows to switch the method used to encode
data based on a change-detection-mode parameter. Expose this setting
as experimental feature in the advanced panel for a backup job.
Signed-off-by: Christian Ebner
---
changes since version 1:
- prefix subject with correct repo
Include the additional parameter to set the `change-detection-mode`
for backup jobs with Proxmox Backup Server target as node wide
configuration, including possible variants to be set.
Signed-off-by: Christian Ebner
---
changes since version 1:
- prefix subject with correct repo
configs/vzdump.
Define the possible modes to be configured in a PBS file change
detection mode to the vzdump confdesc.
Signed-off-by: Christian Ebner
---
changes since version 1:
- no changes
src/PVE/VZDump/Common.pm | 8
1 file changed, 8 insertions(+)
diff --git a/src/PVE/VZDump/Common.pm b/src/PVE
this increases verbosity of the actions, especially when including the
snapshot name, since that will appear in the task logs wereas before
there was no mention of any action, just the storage specific output for
creating/rollback/removal.
Logs are printed at all main actions that can fail or take
The proxmox backup client allows to switch the method used to encode
data based on a change-detection-mode parameter. Expose this setting
as experimental feature in the advanced panel for a backup job.
Signed-off-by: Christian Ebner
---
www/manager6/panel/BackupAdvancedOptions.js | 20 +
Define the possible modes to be configured in a PBS file change
detection mode to the vzdump confdesc.
Signed-off-by: Christian Ebner
---
src/PVE/VZDump/Common.pm | 8
1 file changed, 8 insertions(+)
diff --git a/src/PVE/VZDump/Common.pm b/src/PVE/VZDump/Common.pm
index 1539444..76e5f8
Allows to switch the backup clients change detection mode based on
the option set in the backup jobs configuration for backup jobs with
Proxmox Backup Server target.
Signed-off-by: Christian Ebner
---
src/PVE/VZDump/LXC.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/PVE/VZDump/LXC.
Include the additional parameter to set the `change-detection-mode`
for backup jobs with Proxmox Backup Server target as node wide
configuration, including possible variants to be set.
Signed-off-by: Christian Ebner
---
configs/vzdump.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/conf
This patch series defines the vzdump configuration description as well
as backup job configuration option in the WebUI to set the
experimental `change-detection-mode` parameter to the
proxmox-backup-client invocation for container backups having a Proxmox
Backup Server storage target.
This allows
On May 29, 2024 1:07 pm, Dominik Csapak wrote:
> On 5/29/24 12:09, Fabian Grünbichler wrote:
>> On May 29, 2024 11:20 am, Dominik Csapak wrote:
>>> so that an admin can see from the task logs which snapshot was rolled
>>> back/created/removed without the need to look into the journal (to which
>>>
On 5/29/24 12:09, Fabian Grünbichler wrote:
On May 29, 2024 11:20 am, Dominik Csapak wrote:
so that an admin can see from the task logs which snapshot was rolled
back/created/removed without the need to look into the journal (to which
the admin might not have access to).
good idea in general,
On May 29, 2024 11:20 am, Dominik Csapak wrote:
> so that an admin can see from the task logs which snapshot was rolled
> back/created/removed without the need to look into the journal (to which
> the admin might not have access to).
good idea in general, but wouldn't it be better to log it before
so that an admin can see from the task logs which snapshot was rolled
back/created/removed without the need to look into the journal (to which
the admin might not have access to).
Signed-off-by: Dominik Csapak
---
noticed while trying to find out, to which snapshot a vm was rolled back
to on a ho
25 matches
Mail list logo
