This custom serializer will serialize all the FRR types into a string,
which is the FRR config.
Signed-off-by: Gabriel Goller
---
proxmox-frr/src/lib.rs| 2 +
proxmox-frr/src/serializer.rs | 192 ++
2 files changed, 194 insertions(+)
create mode 100644
Am 02.04.25 um 10:30 schrieb Wolfgang Bumiller:
On Tue, Apr 01, 2025 at 08:21:30PM +0200, Thomas Lamprecht wrote:
This sounds pretty inefficient - especially when
comparing with qmrestore's ability to just read read from stdin.
The reading from stdin is quite limited, does not support sparse f
Archive names start with the guest type and ID and then the same
timestamp format as PBS.
Container archives have the following structure:
guest.config
firewall.config
filesystem/ # containing the whole filesystem structure
VM archives have the following structure
guest.config
firewall.config
vol
On 3/31/25 06:45, Andrew wrote:
> Just noticed I didn’t reply to this before - the patch set in ifupdown2 does
> not actually address IPv6 local tunnel IPs at all.
3.9 itself doesn't, but 3.10 should contain the respective patches
___
pve-devel mailin
--- Begin Message ---
Basically, the backup/restore tasks will be managed through our backup
solution. So, all we needed is VM config which can be fetched through PVE REST
API and a API to get access to consistent disk image which can be then
transferred to backup storage that we support. But it
On 4/1/25 12:46, Thomas Lamprecht wrote:
Am 01.04.25 um 12:19 schrieb Dominik Csapak:
while i also agree to all said here, I have one counter point to offer:
In the case that such an operation is necessary (e.g. HA is not
wanted/needed/possible
for what ever reason), the user will fall back to
--- Begin Message ---
Ok, will give plugins a try and see if we can achieve backup/restore management
from our backup solution.
1. Can we just implement backup provider plugin and not storage plugin? We
can build storage plugin in subsequent releases.
2. What are the steps to configure/d
> DERUMIER, Alexandre hat am 04.04.2025
> 13:31 CEST geschrieben:
> Hi Fabian,
>
> >>the first one is the renaming of a blockdev while it is used, which
> >>is currently done like this:
> >>-- "link" snapshot path to make it available under old and new name
> >>-- handle blockdev additions/reo
Am 05.03.25 um 11:49 schrieb Fiona Ebner:
> v1:
> https://lore.proxmox.com/pve-devel/20250207125514.42668-1-f.eb...@proxmox.com/
>
> Changes in v2:
> * different approach, use existing format
> * introduce standard option
> * add patches to drop mythological 'cow' format
>
> Allow using 'vmdk' f
With [#6143] on the horizon, notification templates, template variables
and template helpers become part of our public API and as such
we should provide some stability guarantees for them.
As a result, we use this opportunity to do a 'final' cleanup.
This series:
- adds some common template vars
Signed-off-by: Lukas Wagner
---
proxmox-notify/Cargo.toml | 2 +-
proxmox-notify/src/endpoints/gotify.rs | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/proxmox-notify/Cargo.toml b/proxmox-notify/Cargo.toml
index ddbaacd7..5a54c4a1 100644
--- a/proxmox-notify/C
Read the rules configuration in each round and update the canonicalized
rules configuration if there were any changes since the last round to
reduce the amount of times of verifying the rule set.
Signed-off-by: Daniel Kral
---
As noted inline already, there's a missing check whether the service
c
Am 04.11.24 um 11:42 schrieb Fabian Grünbichler:
> remote migration requires elevated privileges already and can thus only be
> triggered by trusted sources, but an additional safeguard of checking the
> image
> for external references doesn't hurt.
>
> Signed-off-by: Fabian Grünbichler
> ---
>
Reviewed-by: Fiona Ebner
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
Signed-off-by: Markus Frank
---
no changes in v15
PVE/QemuServer.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuSer
On March 4, 2025 12:57 pm, Markus Frank wrote:
> Adds a config file for directories by using a 'map' property string for
> each node mapping.
>
> Next to node & path, there is the optional announce-submounts parameter
> which forces virtiofsd to report a different device number for each
> submount
A non-1KiB aligned source image could cause issues when used with
qcow2 fleecing images, e.g. for an image with size 4.5 KiB:
> Size mismatch for 'drive-tpmstate0-backup-fleecing' - sector count 10 != 9
Raw images are attached to QEMU with an explicit 'size' argument, so
rounding up before allocat
v5:
https://lore.proxmox.com/pve-devel/20250321134852.103871-1-f.eb...@proxmox.com/
v4:
https://lore.proxmox.com/pve-devel/20241114150754.374376-1-f.eb...@proxmox.com/
v3:
https://lore.proxmox.com/pve-devel/20241107165146.125935-1-f.eb...@proxmox.com/
Changes in v6:
* Factor out some helpers in
This commit moves some IP address and MAC address types from
proxmox-ve-config to proxmox, so they can be used re-used across our
code base.
The code in this commit is mostly the same as in proxmox-ve-config
('bc9253d8'), but I have made a few changes:
* Added additional documentation to some of
Am 11.03.25 um 14:27 schrieb Christoph Heiss:
> Comes with a reduction of 52 -> 40 in terms of crate dependencies for
> proxmox-chroot, 198 -> 192 for a full workspace build.
>
> Currently, this is done inconsistently anyway, i.e. there are calls to
> the external mount(8) as well as mount(2) and
On Fri, Apr 04, 2025 at 09:51:05AM +0200, Stefan Hanreich wrote:
> Thanks for your review - comments inline
>
> On 4/4/25 09:31, Wolfgang Bumiller wrote:
> > On Tue, Apr 01, 2025 at 04:52:44PM +0200, Stefan Hanreich wrote:
> >> Add a type for representing Linux hostnames. These are the same
> >> c
On 04/04/2025 10:55, Thomas Lamprecht wrote:
> Am 04.04.25 um 10:14 schrieb Maximiliano Sandoval:
>> Friedrich Weber writes:
>
> ...
>
>> An option that might require lower maintenance would be to ship a
>> service file override, e.g. at
>> /lib/systemd/system/corosync.service.d/set-log-rate-li
Currently, only one bitmap name per target is planned to be used.
Simply use the target ID itself as the bitmap name. This allows to
simplify the logic quite a bit and there also is no need for the
backup_access_bitmaps hash table anymore.
For the return value, the bitmap names are still passed al
Am 04.04.25 um 11:18 schrieb Friedrich Weber:
> On 04/04/2025 10:55, Thomas Lamprecht wrote:
>> Would be more fitting if we did not package corosync our self, as is
>> this integrated way would be fine to me. That sasid yours could be too.
>
> Hmm, is this cut off?
no, just a few typos that might
--- Begin Message ---
Given the delays in ifupdown2 development (the patches for vxlan IPv6 have been
sitting un-reviewed for 5 months now, and this is the 3rd patch set in * 5
years * that has tried to fix this issue without being merged), can we continue
waiting years for them to fix?
The mos
Am 07.03.25 um 15:44 schrieb Dominik Csapak:
> and retroactively add descriptions for previous bumps.
>
> Signed-off-by: Dominik Csapak
> ---
> new in v2
> PVE/API2/Qemu/Machine.pm | 9 +
> PVE/QemuServer/Machine.pm | 15 +++
> 2 files changed, 24 insertions(+)
>
> diff --
This patch did not apply correctly anymore since there were some other
patches applied upstream since last time.
A comment about that inline.
On 4/3/25 12:34, Markus Frank wrote:
add dir mapping checks to check_local_resources
Since the VM needs to be powered off for migration, migration shou
Am 07.03.25 um 15:44 schrieb Dominik Csapak:
> and clarify what windows guests will be pinned to.
>
> Signed-off-by: Dominik Csapak
> ---
> new in v2
> qm.adoc | 15 +++
> 1 file changed, 15 insertions(+)
>
> diff --git a/qm.adoc b/qm.adoc
> index 4bb8f2c..16ed870 100644
> --- a/qm.
One comment inline.
On 4/3/25 12:34, Markus Frank wrote:
Signed-off-by: Markus Frank
---
v15:
* removed announce-submounts
www/manager6/Makefile | 1 +
www/manager6/window/DirMapEdit.js | 202 ++
2 files changed, 203 insertions(+)
create mode 100
Some comments inline about undefined values.
Also two small notes about testing the assertions, which both works as
expected (die for Windows + POSIX ACLs and memory hotplug + virtiofs).
On 4/3/25 12:34, Markus Frank wrote:
add support for sharing directories with a guest vm.
virtio-fs needs
On 4/3/25 12:34, Markus Frank wrote:
Signed-off-by: Markus Frank
---
v15:
* moved all options except dirid to an advanced tab
* improved field labels
Great, looks better with less options up front if Advanced is ticked
off. So consider this as:
Reviewed-by: Daniel Kral
Tested-by: Daniel Kr
On 4/3/25 12:34, Markus Frank wrote:
Signed-off-by: Markus Frank
---
v15:
* added fstab entry example in the docs
* added hyperlinks for websites
* removed announce-submounts part
I second Lukas' comments about adding some words about the WebGUI and
the options being in a table, which would m
Am 07.03.25 um 15:44 schrieb Dominik Csapak:
> since they make some problems (e.g. windows hybrid shutdown is enabled
> by default then -> which makes vGPU problem). Libvirt/virsh also
> disables that by default (and tries preventing enabling it.)
>
> This series introduces a new pve1 version for
On 4/3/25 16:20, Friedrich Weber wrote:
> On 03/04/2025 16:03, Stefan Hanreich wrote:
>>
>>
>> On 4/3/25 15:44, Friedrich Weber wrote:
> - when removing a fabric, the IP addresses defined on the interfaces
> remain until the next reboot. I guess the reason is that ifupdown2
> doesn't
Am 26.02.25 um 15:26 schrieb Alexander Zeidler:
> Signed-off-by: Alexander Zeidler
> ---
> bg.po | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
just fyi: you used the wrong format.subjectprefix here
___
pve-devel maili
On 2025-04-03 12:34, Markus Frank wrote:
> Virtio-fs is a shared file system that enables sharing a directory
> between host and guest VMs. It takes advantage of the locality of
> virtual machines and the hypervisor to get a higher throughput than
> the 9p remote file system protocol.
>
Some tho
Am 11.03.25 um 14:27 schrieb Christoph Heiss:
> Comes with a reduction of 52 -> 40 in terms of crate dependencies for
> proxmox-chroot, 198 -> 192 for a full workspace build.
>
> Currently, this is done inconsistently anyway, i.e. there are calls to
> the external mount(8) as well as mount(2) and
On 4/4/25 09:51, Stefan Hanreich wrote:
>>> +///
>>> +/// It checks for the following conditions:
>>> +/// * At most 63 characters long.
>>> +/// * It must not start or end with a hyphen.
>>> +/// * Must only contain ASCII alphanumeric characters as well as hyphens.
>>> +/// * It must not be pur
--- Begin Message ---
Hi Fabian,
>>the first one is the renaming of a blockdev while it is used, which
>>is currently done like this:
>>-- "link" snapshot path to make it available under old and new name
>>-- handle blockdev additions/reopening/backing-file updates/deletions
>>on the qemu layer
>>
On 3/28/25 18:12, Gabriel Goller wrote:
This series allows the user to add fabrics such as OpenFabric and OSPF over
their clusters.
Overview
This series allows the user to create routed networks ('fabrics') across their
clusters, which can be used as the underlay network for a EVPN c
On Tue, Apr 01, 2025 at 04:52:44PM +0200, Stefan Hanreich wrote:
> Add a type for representing Linux hostnames. These are the same
> constraints as the installer enforces [1]. Lowercasing is fine as
> well, since practically everything treats hostnames case-insensitively
> as RFC 952 stipulates:
>
Am 02.04.25 um 17:15 schrieb Friedrich Weber:
> - I needed to install nbdfuse and modprobe nbd -- might be nice to do
> both automatically somehow (though packages of external backup plugins
> could probably add nbdfuse as a dependency?)
No, modprobe nbd is really only needed for the POC testing o
Am 04.04.25 um 10:39 schrieb Maximiliano Sandoval:
> We show the size selection stack page whenever a filesystem is selected
> in the dropdown.
>
> At the moment when one selects certain raid setups (e.g. btrfs RAID10),
> then enters the Advanced Options page and then selects certain non-raid
> se
On Fri, Apr 04, 2025 at 01:26:46PM +0200, Stefan Hanreich wrote:
>
>
> On 4/4/25 09:51, Stefan Hanreich wrote:
> >>> +///
> >>> +/// It checks for the following conditions:
> >>> +/// * At most 63 characters long.
> >>> +/// * It must not start or end with a hyphen.
> >>> +/// * Must only contain
add SEV-SNP limitations, example configuration and hyperlinks for more
information
Signed-off-by: Markus Frank
---
qm.adoc | 51 +++
1 file changed, 39 insertions(+), 12 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 2617a7c..3aa0406 100644
---
Am 07.03.25 um 15:44 schrieb Dominik Csapak:
> So users can disable them (they're enabled by default in QEMU)
>
> Signed-off-by: Dominik Csapak
> ---
> changes from v1:
> * rework the method with suggestions from fiona
> * change way we add flags because we don't have globalflags anymore
>
> PV
On Tue, Mar 11, 2025 at 02:27:29PM +0100, Christoph Heiss wrote:
> Comes with a reduction of 52 -> 40 in terms of crate dependencies for
> proxmox-chroot, 198 -> 192 for a full workspace build.
>
> Currently, this is done inconsistently anyway, i.e. there are calls to
> the external mount(8) as we
Am 07.03.25 um 15:44 schrieb Dominik Csapak:
> Add the pveX variants (where X > 0) to the list too, so one knows they
> exits. Also this allows them to be shown and chosen in the UI.
>
> Signed-off-by: Dominik Csapak
> ---
> new in v2
> PVE/API2/Qemu/Machine.pm | 24 +++-
> 1
Since c761053 ("Check packets come from the correct interface
https://github.com/corosync/corosync/issues/750";) in kronosnet,
corosync will produce log messages in certain broken network setups.
See inner patch for details. Drawing attention to such setups is
desirable because such setups may expe
Am 28.03.25 um 11:19 schrieb Lukas Wagner:
> This commit add the `common_template_data` sub to PVE::Notify,
> providing a convenient way to get a hash with properties that
> should be accessible from all templates, namely hostname, fqdn
> and cluster-name.
>
> Signed-off-by: Lukas Wagner
> ---
>
We show the size selection stack page whenever a filesystem is selected
in the dropdown.
At the moment when one selects certain raid setups (e.g. btrfs RAID10),
then enters the Advanced Options page and then selects certain non-raid
setups (e.g ext4), the `raiddisk` page will still be visible sinc
Am 17.01.25 um 08:51 schrieb Christoph Heiss:
> .. as newly introduced with 1.84.
>
> Namely `elided_named_lifetimes` for the change of `SdnConfig` and
> `clippy::needless_lifetimes` for the rest.
>
> Signed-off-by: Christoph Heiss
> ---
> proxmox-ve-config/src/firewall/parse.rs | 6 +++---
> p
Thomas Lamprecht writes:
> Am 01.04.25 um 15:09 schrieb Maximiliano Sandoval:
>> The commit message should be updated, I will do that if there is a need
>> for v2.
>
> Can you please either send out a v2 or propose a new commit message that I
> can just copy+paste in full?
v2 at
https://lore.
Am 24.03.25 um 14:19 schrieb Christoph Heiss:
> The option was more or less a hack from the beginning anyway, introduced
> during the split of the GUI and the installation configuration.
>
> The required information is already there from `mngmt_nic` - which
> carries the name of the network interf
Currently, only one bitmap name per target is planned to be used.
Simply use the target ID itself as the bitmap name. This allows to
simplify the logic quite a bit and there also is no need for the
backup_access_bitmaps hash table anymore.
For the return value, the bitmap names are still passed al
this was not covered by any other test
Signed-off-by: Dominik Csapak
---
test/cfg2cmd/audio.conf | 15 +++
test/cfg2cmd/audio.conf.cmd | 37 +
2 files changed, 52 insertions(+)
create mode 100644 test/cfg2cmd/audio.conf
create mode 100644 tes
> Andreas Rogge hat am 03.04.2025 18:08 CEST
> geschrieben:
> Am 03.04.25 um 09:24 schrieb Wolfgang Bumiller:
> > I *believe* `qemu-nbd` should be able to bind all the storage types we
> > want to restore to to /dev/nbdXY devices, which would give the provider
> > a bunch of block devices to wr
Am 31.03.25 um 14:20 schrieb Christoph Heiss:
> Fixes #5880 [0].
>
> This can be useful for certain scenarios, such as being able to
> provision a stack of servers using the auto-installer and afterwards
> being able to work on the servers without time pressure, such as e.g.
> removing the install
when we don't have a specific machine version on a windows guest, we use
the creation meta info to pin the machine version. Currently we always
append the pve machine version from the current installed kvm version,
which is not necessarily the version we pinned the guest to.
Instead, use the same
Am 27.03.25 um 16:17 schrieb Christoph Heiss:
> In certain cases, it can be useful for (expected) parse failures, where
> the error message then also comes directly from serde.
>
> Signed-off-by: Christoph Heiss
> ---
> proxmox-auto-installer/tests/parse-answer.rs | 21 +++-
> 1
Am 28.03.25 um 11:19 schrieb Lukas Wagner:
> - try to make template variable names more clear (in preparation
> for #6143)
> - add common tempate variables (fqdn, hostname, cluster-name)
> - Instead of dumping the status-data variable as a JSON blob we
> add template variables for the most usef
The fabrics patch series moved some generic network types into its own
crate, so they can be reused across crates. Migrate proxmox-firewall
to use the new proxmox-network-types crate instead of
proxmox_ve_config.
Signed-off-by: Stefan Hanreich
---
Notes:
This depends on the changes in the pr
So users can disable them (they're enabled by default in QEMU)
Signed-off-by: Dominik Csapak
Reviewed-by: Fiona Ebner
---
changes from v2:
* different name for function
* removed comment intended for next patch
* don't put function call inside 'if ()'
PVE/QemuServer.pm | 2 ++
PVE/Qem
Am 28.03.25 um 11:19 schrieb Lukas Wagner:
> With [#6143] on the horizon, notification templates, template variables
> and template helpers become part of our public API and as such
> we should provide some stability guarantees for them.
> As a result, we use this opportunity to do a 'final' cleanu
The new_backup_provider() method can be used by storage plugins for
external backup providers. If the method returns a provider, Proxmox
VE will use callbacks to that provider for backups and restore instead
of using its usual backup/restore mechanisms.
The backup provider API is split into two pa
superseeded by v3:
https://lore.proxmox.com/pve-devel/20250404125345.3244659-1-d.csa...@proxmox.com/
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Hard-coding a list of sensitive properties means that custom plugins
cannot define their own sensitive properties for the on_add/on_update
hooks.
Have plugins declare the list of their sensitive properties in the
plugin data. For backwards compatibility, return the previously
hard-coded list if no
Changes for version 11:
* Allow declaring storage features via plugin data.
* Introduce new_backup_provider() plugin method.
* Allow declaring sensitive properties via plugin data.
See the api changelog file for details.
Signed-off-by: Fiona Ebner
---
ApiChangeLog | 32 ++
For punching holes via fallocate. This will be useful for the external
backup provider API to discard parts of the source. The 'file-handle'
mechanism there uses a fuse mount, which does not implement the
BLKDISCARD ioctl, but does implement fallocate.
Signed-off-by: Fiona Ebner
---
src/PVE/Stor
Signed-off-by: Fiona Ebner
---
test/run_qemu_img_convert_tests.pl | 18 ++
1 file changed, 18 insertions(+)
diff --git a/test/run_qemu_img_convert_tests.pl
b/test/run_qemu_img_convert_tests.pl
index 20ff387a..29c188d8 100755
--- a/test/run_qemu_img_convert_tests.pl
+++ b/test/ru
While restore_external_archive() already has a check, that happens
after an existing container is destroyed.
Signed-off-by: Fiona Ebner
---
src/PVE/API2/LXC.pm | 14 ++
1 file changed, 14 insertions(+)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 7cb5122..6cd771c 100
First, the provider is asked about what restore mechanism to use.
Currently, 'directory' and 'tar' are possible. The 'directory'
mechanism is for restoring from a directory containing the container's
full filesystem structure, which is restored by piping from a
privileged tar cf - to tar xf - in th
Call job_{init,cleanup}() and backup_{init,cleanup}() methods so that
backup providers can prepare and clean up for the whole backup job and
for individual guest backups.
It is necessary to adapt some log messages and special case some
things like is already done for PBS, e.g. log file handling.
The module includes a run_in_userns() helper to run a Perl subroutine
in a user namespace.
The first use case is running the container backup subroutine for
external providers inside a user namespace. That allows them to see
the filesystem to back-up from the containers perspective and also
improv
The features returned by the 'query-proxmox-support' QMP command are
booleans, so just checking for definedness is not enough in principle.
In practice, a feature is currently always true if defined. Still, fix
the checks, should the need to disable support for a feature ever
arise in the future an
'tar' itself already protects against '..' in component names and
strips absolute member names when extracting (if not used with the
--absolute-names option) and in general seems sane for extracting.
Additionally, the extraction already happens in the user namespace
associated to the container. So
Which looks up whether a storage supports a given feature in its
'plugindata'. This is intentionally kept simple and not implemented
as a plugin method for now. Should it ever become more complex
requiring plugins to override the default implementation, it can
later be changed to a method.
Suggest
For fleecing, the size needs to match exactly what QEMU sees. In
particular, EFI disks might be attached with a 'size=' option, meaning
that size can be different from the volume's size. Commit 36377acf
("backup: disk info: also keep track of size") introduced size
tracking and it was used for flee
some suggestions for rephrasings inline:
On Fri, 4 Apr 2025 14:53:45 +0200
Dominik Csapak wrote:
> and clarify what windows guests will be pinned to.
>
> Signed-off-by: Dominik Csapak
> ---
> changes from v2:
> * mention that windows gets pinned during guest creation
>
> qm.adoc | 15 +++
Virtio-fs is a shared file system that enables sharing a directory
between host and guest VMs. It takes advantage of the locality of
virtual machines and the hypervisor to get a higher throughput than
the 9p remote file system protocol.
build-order:
1. cluster
2. guest-common
3. docs
4. qemu-serve
Add it to both the perl side (PVE/Cluster.pm) and pmxcfs side
(status.c).
This dir.cfg is used to map directory IDs to paths on selected hosts.
Signed-off-by: Markus Frank
Reviewed-by: Fiona Ebner
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
T
Adds a config file for directories by using a 'map' property string for
each node mapping.
example config:
```
some-dir-id
map node=node1,path=/path/to/share/
map node=node2,path=/different/location/
```
Signed-off-by: Markus Frank
---
v16:
* renamed verify_path to pve_verify_pat
Signed-off-by: Markus Frank
Reviewed-by: Fiona Ebner
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
Tested-by: Lukas Wagner
---
no changes in v16
debian/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/control b/debian/contro
add support for sharing directories with a guest vm.
virtio-fs needs virtiofsd to be started.
In order to start virtiofsd as a process (despite being a daemon it is
does not run in the background), a double-fork is used.
virtiofsd should close itself together with QEMU.
There are the parameters
Signed-off-by: Markus Frank
---
v16:
* adapted error message and added comment why there is also an error
message in the GUI
www/manager6/Makefile | 1 +
www/manager6/window/DirMapEdit.js | 204 ++
2 files changed, 205 insertions(+)
create mode 100644 w
Signed-off-by: Markus Frank
---
v16:
* added hint for directory mapping in VirtiofsEdit
www/manager6/Makefile | 1 +
www/manager6/Utils.js | 1 +
www/manager6/qemu/HardwareView.js | 19
www/manager6/qemu/VirtiofsEdit.js | 143 ++
4 fi
Signed-off-by: Markus Frank
Reviewed-by: Daniel Kral
Tested-by: Daniel Kral
---
no changes in v16
www/manager6/Makefile | 1 +
www/manager6/dc/Config.js | 10 +
www/manager6/dc/DirMapView.js | 38 +++
3 files changed, 49 insertions(+)
creat
Signed-off-by: Markus Frank
Reviewed-by: Fiona Ebner
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
Tested-by: Lukas Wagner
---
no changes in v16
PVE/QemuServer.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/PVE/Qe
Signed-off-by: Markus Frank
Reviewed-by: Daniel Kral
---
no changes in v16
qm.adoc | 102 ++--
1 file changed, 100 insertions(+), 2 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 2617a7c..63632fc 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1202
Signed-off-by: Markus Frank
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
Tested-by: Lukas Wagner
---
no changes in v16
www/manager6/Makefile | 1 +
www/manager6/form/DirMapSelector.js | 63 +
2 files
add dir mapping checks to check_local_resources
Since the VM needs to be powered off for migration, migration should
work with a directory on shared storage with all caching settings.
Signed-off-by: Markus Frank
---
v16:
* rebase to master
* replaced push with $mapped_res->{$k} = { name => $entr
Signed-off-by: Markus Frank
Reviewed-by: Fiona Ebner
Reviewed-by: Laurențiu Leahu-Vlăducu
Tested-by: Laurențiu Leahu-Vlăducu
Tested-by: Daniel Kral
Tested-by: Lukas Wagner
---
no changes in v16
PVE/API2/Cluster/Mapping.pm | 7 +
PVE/API2/Cluster/Mapping/Dir.pm | 308 ++
Am 28.03.25 um 18:48 schrieb Christian Ebner:
> The check for dkms kernel modules relies on the output of `dkms
> status`. dkms command invocation will perform the following sanity
> check:
> ```
> if [ ! -e <(echo) ]; then
> warn $"dkms will not function properly if /proc is not mounted."
> fi
On 4/3/25 12:34, Markus Frank wrote:
Signed-off-by: Markus Frank
---
v15:
* removed announce-submounts
Changes LGTM here, so consider this as:
Reviewed-by: Daniel Kral
Tested-by: Daniel Kral
___
pve-devel mailing list
pve-devel@lists.proxmox.com
On 4/3/25 12:34, Markus Frank wrote:
Virtio-fs is a shared file system that enables sharing a directory
between host and guest VMs. It takes advantage of the locality of
virtual machines and the hypervisor to get a higher throughput than
the 9p remote file system protocol.
build-order:
1. cluste
On 04/04/2025 11:40, Thomas Lamprecht wrote:
>> I am starting to lean towards not limiting this here. However, I have
>> seen multiple instances at our support portal where logs are rotated
>> rather quickly and useful messages are lost.
>
> In dmesg (kernel ring buffer) sure, but the systemd jour
In preparation for fixing #6285 [0].
`0` means to just skip writing the module parameter. But (especially)
with the upcoming change in ZFS 2.3 - which makes the size basically
that of the system memory minus 1 GiB - we want to always write some
value.
[0] https://bugzilla.proxmox.com/show_bug.cgi
Fixes #6285 [0].
Came up a few times now in the forum (most recently [0], german) and is
a potential source of confusion for users, if the file does not exist on
(new) installations.
It makes indeed sense to just unconditionally write to
/etc/modprobe.d/zfs.conf. Often users create a separate ZFS
In preparation for fixing #6285 [0].
`0` means to just skip writing the module parameter. But (especially)
with the upcoming change in ZFS 2.3 - which makes the size basically
that of the system memory minus 1 GiB - we want to always write some
value.
[0] https://bugzilla.proxmox.com/show_bug.cgi
and retroactively add descriptions for previous bumps.
Signed-off-by: Dominik Csapak
---
changes from v2:
* added additional sentence to new machine model description
PVE/API2/Qemu/Machine.pm | 9 +
PVE/QemuServer/Machine.pm | 15 +++
2 files changed, 24 insertions(+)
dif
so new guests (or guests with the 'latest' machine type) have that
setting automatically disabled.
The previous default (enabling S3/S4), does not make too much sense in a
virtual environment, and sometimes makes problems, e.g. Windows defaults
to using 'hybrid shutdown' and 'fast startup' when S4
1 - 100 of 275 matches
Mail list logo
