Am 01.02.24 um 22:33 schrieb DERUMIER, Alexandre:
>
>>> To clarify, with my "VM-specific" proposal I mean: The backup job
>>> decides whether to use fleecing or not. The VM decides which storage
>>> to
>>> use for fleecing.
>
>
> Personnaly, for my usage, I prefer to define fleecing storage in b
Am 01/02/2024 um 16:12 schrieb Fiona Ebner:
> It can be security-relevant in some environments. The LVM storage
> documentation can be reached via the "Help" button and contains a few
> more details.
>
> Signed-off-by: Fiona Ebner
> ---
>
> Changes in v2:
> * Improve label text (thanks to Fa
Am 01/02/2024 um 11:42 schrieb Maximiliano Sandoval:
> Signed-off-by: Maximiliano Sandoval
> ---
> es.po | 48 +++-
> 1 file changed, 19 insertions(+), 29 deletions(-)
>
>
applied, thanks!
___
pve-devel ma
Am 01/02/2024 um 10:20 schrieb Fiona Ebner:
> Am 31.01.24 um 12:55 schrieb Friedrich Weber:
>>
>> After changing `warn` to `log_warn` I noticed that pvestatd does not
>> write the warning to the syslog every 10s anymore. Turns out `warn`
>> triggers a custom __WARN__ handler we install for our daem
Am 29/01/2024 um 16:43 schrieb Folke Gleumes:
> proxmox-perl-rs set's SSL_CERT_{DIR,FILE}, which can break ssl in
> containers if their certificate store can't be found in the same spot.
> This patch explicitly unsets those variables before starting the
> container.
>
> Signed-off-by: Folke Gleume
Am 29/01/2024 um 16:43 schrieb Folke Gleumes:
> The keep-env option allows the user to define if the current environment
> should be kept when running 'pct enter/exec'. pct will now always set
> '--keep-env' or '--discard-env' when calling lxc-attach to anticipate
> the upcoming change in default b
Am 26/01/2024 um 16:27 schrieb Max Carrara:
> Adapt the patch that originally disabled certain TLS checks during the
> dashboard's startup and fixes the `ceph dashboard` subcommand becoming
> unavailable if the dashboard crashes during that time.
>
> This is achieved by re-implementing certain che
Am 26/01/2024 um 16:44 schrieb Max Carrara:
> Updated series that includes an unstaged change I had missed to amend
> regarding the corrected typo mentioned in the recent patch for master [0].
> Woops!
>
> [0]: https://lists.proxmox.com/pipermail/pve-devel/2024-January/061499.html
>
> Max Carrara
Am 26/01/2024 um 16:44 schrieb Max Carrara:
> This commit essentially contains all changes from the following
> commits (most recent last):
> * f35168f6713d5f3fa1aaa8c572d754b61c458d91
> * 86a553d66e69176940959530d4fedcbcbbab54d9
> * ab5c03b44d78c4e4b233ff5a310888592dbb9bb4
FWIW, I got a git
Am 29/01/2024 um 10:47 schrieb Alexander Zeidler:
> to avoid a failing null check and its error message. This confused
> users since the activation was successful anyway.
>
> Signed-off-by: Alexander Zeidler
> ---
> v2:
> * use "return" instead of "return undef"
> * add commit message
>
> v1: ht
Am 30/01/2024 um 15:14 schrieb Fiona Ebner:
> Most notable fixes from a Proxmox VE perspective are:
>
> * "virtio-net: correctly copy vnet header when flushing TX"
> To prevent a stack overflow that could lead to leaking parts of the
> QEMU process's memory.
> * "hw/pflash: implement update bu
Am 29/01/2024 um 12:16 schrieb Stefan Lendl:
> When running `zfs mount -a`, prevent the exported datasets (with sharenfs)
> to be truncated (unexported).
> Adds tests to verify shares persist after mount -a
>
> Signed-off-by: Stefan Lendl
> ---
> This was merged upstream via https://github.com/op
Am 26/01/2024 um 13:05 schrieb Fabian Grünbichler:
> installing it at least gives the admin a heads up if our base Debian release
> is
> ever faster shipping a newer version of shim or Grub, which would look
> (something) like this:
>
> Reading package lists... Done
> Building dependency tree..
Am 25/01/2024 um 10:40 schrieb Fiona Ebner:
> This essentially repeats commit 6b7c181 ("add patch to work around
> stuck guest IO with iothread and VirtIO block/SCSI") with an added
> fix for the SCSI event virtqueue, which requires special handling.
> This is to avoid the issue [3] that made the r
14 matches
Mail list logo