I have 2 new releases. One is proxmox-kernel 6.19.2 (unofficial) — Linux 6.19.2 + OpenZFS 2.4.1, which is based on Ubuntu 6.19.0-6.6. I made it an official release, as The Resolute Raccoon has it as a stable release. I have updated it to have...
Yes, it's all file based and there is no 1:1 migration path available, especially with LVM because it's block storage. This question is asked a lot and there is no working and stable open source solution for this in the Linux realm with block...
Every time the kernel is updated, I have to re-install the nvidia divers, they do not survive the update.
I install them by:
./$(ls -t NVIDIA-Linux-x86_64-580.126.18.run | head -n 1) --dkms --disable-nouveau --kernel-module-type proprietary...
It also depends on the underlying hardware, emulating a 4-socket system on a 2-socket system makes technically no sense and will not help in any way, even if the total core count is identical. The devil is in the details here, so as @pulipulichen...
I assume this Virtiofs-Device is then also included in the pbs backup?
Thanks for sharing, I think both ways will work now I have to just decide which way to use :D
Hello all,
I am trying to activate my Subscriptions on the clients (PVEs) using the following command.
proxmox-offline-mirror-helper offline-key --source http://proxmox-offline-mirror.domain.example/
I get the error:
Error: parameter...
Yes, we're running this for many years without any problem. ZFS on ZFS can be a problem performancewise, but will technically work without a problem. With this setup you seperated both adequately and can manage everything directly in the VM, have...
Just the 40 VMs are actually 40 vCPUs, for example.
Threads or cores?
But since I don't know anything about how Proxmox will detect the CPU,
there you go.
Have a good af
Hello,
I am trying to backup a very large VM (around 2 TiB).
At 1.2 TiB I get:
zstd: error 70 : Write error : cannot write block : File too large
and then write error - broken pipe.
Is there anything I can do to make my backup possible?
Checkbox can be kept with logic underneath to deploy "the regular version" vs "VPP version" or any other version (OVS+DPDK) when it appears.
From user perspective, creating a specific option doesn't make sense.
I'm migrating a VM from one cluster to another.
In Task Viewer, the progress of the data transfer is displayed as a veeeery long line because line breaks aren't shown.
However, when I copy and paste this line from Task Viewer into a text editor...
It also depends on the underlying hardware, emulating a 4-socket system on a 2-socket system makes technically no sense and will not help in any way, even if the total core count is identical. The devil is in the details here, so as @pulipulichen...
Verify speed: 1068.22 MB/s is a bit curious given the rest of the numbers.. but I guess this should be amortized when processing chunks in parallel. the TLS speed also looks better than your actual throughput.
dd-ing /dev/zero is not a valid...
Indeed, Chris says that this is in the pipeline and I'm good with that. Problem with retries is we have VM's going up to 12TB of disk so could be 2-3 days of verify job hogging bandwidth on a single VM. The retries planned with be very helpful.
what does "proxmox-backup-client benchmark --repository <...>" say if you run it on one of the PVE hosts? at what speed does a single backup task peak?
might be that the actual transfer over HTTP 2.0/TLS with a single TCP connection is your...