Signed-off-by: Aaron Lauterer
---
changes since v2: none
www/manager6/node/Config.js | 1 +
1 file changed, 1 insertion(+)
diff --git a/www/manager6/node/Config.js b/www/manager6/node/Config.js
index d27592ce..7bdfb6d9 100644
--- a/www/manager6/node/Config.js
+++ b/www/manager6/node/Config.js
@
The new optional bridge_vids field allows to set that property via the
GUI. Since the backend needs to support it, the field needs to be
explicitly enabled.
For now, Proxmox VE (PVE) is the use case.
Signed-off-by: Aaron Lauterer
---
changes since v2:
* added validation code following how it is
This is one step to make it possible to define the VLAN IDs and ranges
for bridges.
It is expected to be used in combination with the `-list` magic
property. Therefore it defines and checks the validity of a single list
item that could just be a single VLAN tag ID or a range.
Signed-off-by: Aaron
In some situations we don't want a total empty list. I opted for a
dedicated function instead of integrating it as error in the
`split_list` function. It is used in many places and the potential
fallout from unintended behavior changes is too big.
Signed-off-by: Aaron Lauterer
---
changes since v
Because the API accepts multiple possible list separators we need to
make sure that we write the bridge_vids with space as separator, no
matter which separator was used when passing it to the API.
Signed-off-by: Aaron Lauterer
---
changes since v2:
* added to make sure the format works as expecte
this version reworks a few parts since v2.
* renamed format in JSONSchema to a more generic `pve-vlan-id-or-range`
* explicitly use spaces when writing interfaces file. This is one
possible approach to deal with the fact, that the generic `-list`
format will accept quite a few delimiters and w
Signed-off-by: Aaron Lauterer
---
changes since v2:
* added checks to handle empty lists
PVE/API2/Network.pm | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/PVE/API2/Network.pm b/PVE/API2/Network.pm
index f39f04f5..dd3855d1 100644
--- a/PVE/API2/Network.pm
+++
new patch series (v3) is available
https://lists.proxmox.com/pipermail/pve-devel/2024-July/064388.html
On 2023-06-14 11:30, Aaron Lauterer wrote:
For that we need to add a new format option that checks against valid
VLAN tags and ranges, for example: 2 4 100-200
The check, if the default valu
applied, thanks
Interesting how this seems to break on other architectures...
On Fri, Jun 07, 2024 at 06:33:13PM GMT, Jing Luo via pve-devel wrote:
> From: Jing Luo
> To: pve-devel@lists.proxmox.com
> Cc: Jing Luo
> Subject: [PATCH pve-common] tools: fix syscall mknod()
> Date: Fri, 7 Jun 2024
Some callers like the move disk API endpoint do not pass an explicit
completion argument. This is not an issue in general, because
qemu_drive_mirror_monitor() defaults to 'complete'. However, there was
a string comparision for the cloudinit case that can trigger a warning
about the value being unin
Am 14.06.24 um 13:00 schrieb Fiona Ebner:
> The 'status' pointer is dereferenced regardless of the NULL check,
> i.e. 'status->closed' is accessed after the branch with the check.
> Since all callers pass in the address of a struct on the stack, the
> pointer can never be NULL. Remove the superfluo
In order to make sure we are only affecting VM traffic and no host
interfaces that are bridged, move the rules into a chain that gets
executed inside the guest chain, rather than setting the rules
globally.
Since ether type matches on the respective Ethernet header, it
doesn't work for packets wit
Signed-off-by: Stefan Hanreich
---
proxmox-ve-config/Cargo.toml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/proxmox-ve-config/Cargo.toml b/proxmox-ve-config/Cargo.toml
index cc689c8..b0f3434 100644
--- a/proxmox-ve-config/Cargo.toml
+++ b/proxmox-ve-config/Cargo.toml
@
When matching via ether type, VLAN packets are not matched. This can
cause ARP packets encapsulated in VLAN frames to be dropped.
Signed-off-by: Stefan Hanreich
---
proxmox-firewall/src/firewall.rs | 2 +-
.../tests/snapshots/integration_tests__firewall.snap | 10 ---
Am 10.06.24 um 11:04 schrieb Fiona Ebner:
> The storage API version has been bumped to at least 9 since
> libpve-storage = 7.0-4. If the source node is on Proxmox VE 8, where
> this change will come in, then the target node can be assumed to be
> running either Proxmox VE 8 or, during upgrade, the
Am 03/07/2024 um 10:40 schrieb Fiona Ebner:
> Some callers like the move disk API endpoint do not pass an explicit
> completion argument. This is not an issue in general, because
> qemu_drive_mirror_monitor() defaults to 'complete'. However, there was
> a string comparision for the cloudinit case t
Am 14/06/2024 um 13:29 schrieb Fiona Ebner:
> While archives with unknown or undetermined subtype could be shown,
> this is only for autocompletion, so users can still specify those
> manually if required.
>
> Signed-off-by: Fiona Ebner
> ---
> PVE/QemuServer.pm | 2 +-
> 1 file changed, 1 inser
Adds the ability to change the owner of a guest image.
Btrfs does not need special commands to rename a subvolume and this can
be achieved the same as in Storage/plugin.pm's rename_volume taking
special care of how the directory structure used by Btrfs.
Signed-off-by: Maximiliano Sandoval
---
s
Am 12/06/2024 um 14:15 schrieb Fiona Ebner:
> ---
> PVE/API2/Qemu.pm | 3 +++
> 1 file changed, 3 insertions(+)
>
>
applied both patches, thanks!
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinf
On April 29, 2024 4:49 pm, Fiona Ebner wrote:
> Reported in the community forum:
> https://forum.proxmox.com/threads/145955/post-658380
>
> Signed-off-by: Fiona Ebner
> ---
> vzdump.adoc | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/vzdump.adoc b/vzdump.adoc
> in
On May 17, 2024 11:07 am, Fiona Ebner wrote:
> Reported in the community forum [0].
>
> Both firmware files that are in the package [1]
>
>> /lib/firmware/ath9k_htc/htc_7010-1.4.0.fw
>> /lib/firmware/ath9k_htc/htc_9271-1.4.0.fw
>
> seem to have been present since the linux-firmware submodule com
This can lead to issue when upgrading from ifupdown to ifupdown2. The
particular issue this fixes occurs in the following scenario:
* Suppose there is a legacy Debian host with ifupdown and ifenslave
installed that has a bond configured in /etc/network/interfaces.
* ifenslave installs a script /
superseded by
https://lists.proxmox.com/pipermail/pve-devel/2024-July/064404.html
On 6/27/24 17:01, Stefan Hanreich wrote:
> This can lead to issue when upgrading from ifupdown to ifupdown2. The
> particular issue this fixes occurs in the following scenario:
>
> * Suppose there is a legacy Debian
Add the ability to move a backup, ISO, container template or snippet
between storages and nodes via an API method. Moving a VMA backup to a
Proxmox Backup Server requires the proxmox-vma-to-pbs package to be
installed. Currently only VMA backups can be moved to a Proxmox Backup
Server and moving ba
On 26/06/2024 11:58, Fabian Grünbichler wrote:
@@ -1613,6 +1615,15 @@ sub volume_export {
run_command(['tar', @COMMON_TAR_FLAGS, '-cf', '-', '-C', $file,
'.'],
output => '>&'.fileno($fh));
return;
+ } elsif ($format eq 'backup+size') {
nit:
On 2024-07-03 14:32, Maximiliano Sandoval wrote:
Aaron Lauterer writes:
Works overall. I did not test edge cases like working around the BTRFS plugin to
have qcow2 files instead of the raw files in a subvol.
Thanks for testing!
[...]
I am not too familiar with how BTRFS and our plugi
On May 28, 2024 10:50 am, Fiona Ebner wrote:
> In Proxmox VE 8, the oldest supported QEMU version is 8.0, so a check
> for version 4.0.1 is not required anymore.
>
> Signed-off-by: Fiona Ebner
> ---
>
> New in v2.
>
> PVE/VZDump/QemuServer.pm | 4
> 1 file changed, 4 deletions(-)
>
> dif
On May 28, 2024 10:50 am, Fiona Ebner wrote:
> In Proxmox VE 8, the oldest supported QEMU version is 8.0, so a
> check for version 4.2 is not required anymore. The check was also
> wrong, because it checked the installed version and not the currently
> running one.
>
> Signed-off-by: Fiona Ebner
On May 28, 2024 10:50 am, Fiona Ebner wrote:
> There is a possibility that the drive-mirror job is not yet done when
> the migration wants to inactivate the source's blockdrives:
>
>> bdrv_co_write_req_prepare: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)'
>> failed.
>
> This can be prevented
On May 28, 2024 10:50 am, Fiona Ebner wrote:
> The version of the running QEMU binary is not related to the machine
> version and so it's a bit confusing to have the helper in the
> 'Machine' module. It cannot live in the 'Helpers' module, because that
> would lead to a cyclic inclusion Helpers <->
Am 03.07.24 um 15:15 schrieb Fabian Grünbichler:
> On May 28, 2024 10:50 am, Fiona Ebner wrote:
>> +eval {
>> +mon_cmd(
>> +$vmid,
>> +"block-job-change",
>> +id => $job,
>> +type => 'mirror',
>> +'copy-mode' => 'write-blocking
Am 03.07.24 um 15:44 schrieb Fiona Ebner:
> Am 03.07.24 um 15:15 schrieb Fabian Grünbichler:
>> On May 28, 2024 10:50 am, Fiona Ebner wrote:
>>> + eval {
>>> + mon_cmd(
>>> + $vmid,
>>> + "block-job-change",
>>> + id => $job,
>>> + type => 'mirror',
>
--- Begin Message ---
extended_l2 is an optimisation to reduce write amplification.
Currently,without it, when a vm write 4k, a full 64k cluster
need to be writen.
When enabled, the cluster is splitted in 32 subclusters.
We use a 128k cluster by default, to have 32 * 4k subclusters
https://blogs
33 matches
Mail list logo
