Hello everyone,
I just updated my pve node and got the following changelog after running apt-get dist-upgrade:
This did not cause me any real concern as it outlines a couple of possibly breaking changes. (So I am assuming this is...
Hi - Running PVE 9.2.10
I've created a WS 2025 VM and then converted it to a template. As well the system disk, it has an EFI and TPM disks, both 4M
When I try to create a full clone from the template, it fails at the start when creating the...
Ran into an edge-case with a PBS virtual machine that had the chunks stored the host, backed by virtiofs. Garbage collection would consistently fail with "ENFILE: File table overflow"
Finding the limit wasn't the easiest since it isn't enforced...
Thank you very much for the response, I thought it was related to the anomalous behavior of ProxMox, I've noted it, I also have an open ticket with Veeam about the issue.
PVE doesn't have a 'supported' list, I am assuming this is a list of VMs you're wanting to export from an existing system like vSphere?
You can run essentially any x86-64 OS, so all of those are fine. The OS Type field in PVE isn't a...
Sending notifications for exceeding storage limits is not possible with the current PBS feature set, using external monitoring is the best way to achieve this [0].
FWIW there is some development work in adding protections for datastores running...
A bit more on the proxmox-offline-mirror tool, it creates local repositories, with a snapshoted subdirectories.
These snapshots are folders that are named after the exact moment the sync was done, so each time you use the tool a new folder is...
Had a similar experience when trying to download updates for our cluster in China.
I ended up singeling out the IP address for the Proxmox CDN in Singapore and added that IP address to the /etc/hosts file. (each host)
I basically pinned the...
iSCSI isnt deprecated or dead, which is to say the driver stack is included with every modern operating system. having said that, iscsi makes little sense in a world where nvof exists.
Hi,
tl;dr: Yes, running pve-network-interface-pinning generate and then rebooting is sufficient.
Our documentation provides some more details: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_pve_network_interface_pinning_tool
This can be done gradually, but needs a bit of care. We're currently in the process of finishing a migration helper tool and providing documentation for how to do this.
Our current working theory is that the issue is caused by a newer firmware in conjunction with a newer kernel. Generally downgrading the firmware to an older version has been reported to work, although it's always hard with issues like these that...
Dein Plan passt, aber die Bridge musst du nicht wegwerfen. cluster und cluster.4001 bleiben genau wie sie sind, du legst nur ein Bond an und tauschst bridge-ports enp1s0f1np1 gegen bond0. Also bond-slaves enp1s0f0np0 enp1s0f1np1, bond-mode...
pro tip: use ventoy to make a boot stick, it create a multi boot usb stick.
usage:
1) install ventoy to usb stick
2) copy any ISOs to the stick, and boot the iso of your choice.
This can be done gradually, but needs a bit of care. We're currently in the process of finishing a migration helper tool and providing documentation for how to do this.
@yangsm AFAIK, Ceph 20.2.4 / 19.2.6 packages are only available in Test repository, you should avoid using it unless for testing. Proxmox is working on the process to rotate the keys [1], although we still don't know the details, on paper it...
Dein Plan passt, aber die Bridge musst du nicht wegwerfen. cluster und cluster.4001 bleiben genau wie sie sind, du legst nur ein Bond an und tauschst bridge-ports enp1s0f1np1 gegen bond0. Also bond-slaves enp1s0f0np0 enp1s0f1np1, bond-mode...