Hello,
I was wondering how I could mirror my enterprise PDM repo in POM. Usually the enterprise PDM repo should be unlocked once >80% of the PVE nodes managed have a valid >=Basic subscription.
I have a PDM with 4 nodes right now that are all basic licenses.
I tried adding a mirror to POM like...
What do you mean by the same settings?
The same amount of CPU cores, sure. Same amount of memory: no, the hypervisor requires a couple of gigabytes as well. CPU feature flags: yes, set it to type host.
Can confirm this also happens on Dell R740 Generation of Servers with a Skylake CPU in it. Skylake-SP in theory supports AVX512 so it should support v4 (and the VM do indeed boot on V4) but it seems to be rather broken
Hello,
we have some Dell Storage Appliances that we would like to use with Proxmox. They export iSCSI LUNs and we would like to use the LVM (thick) shared storage with them.
Dell wants you to create smaller LUNs (maybe 2TiB or so) but a lot of them to be able to balance the load between the...
I am also experiencing this issue. I just turned on my VM and let it idle in the bootloader to be able to make an online migration which then uses the qemu shim - but this does not seem to work for TPM Disks:
2026-07-03 15:44:35 ERROR: no export formats for...
Hi, I wanted to migrate a VM from one cluster to another with PDM. I recently switched the certificates in the second (target) cluster to ACME provided ones (ACME directory is an internal CA though, not LE). I updated the certificates in PDM and the "Check Certificate" function is happy, all...
Thank you very much for your help, we will restructure how that part of our monitoring is deployed, in theory we don't *need* docker for it.
This also helped with some oddities with the firewall in Proxmox.
Maybe it would be a good idea to put a small warning about that incompatibility on the...
Yup that did the trick... wow o_O Thats... mildly inconvenient.
We usually need docker as some monitoring checks run inside a docker container. At least we now know where the issue lies, not sure yet how to fix that...
sure, here is the output:
root@node01:~# cat /etc/network/interfaces.d/sdn
#version:2
auto v0074
iface v0074
bridge_ports vmbr0.74
bridge_stp off
bridge_fd 0
root@node01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000...
I needed to set up a new cluster anyway for some testing and I managed to reproduce the issue. This time I used normal Linux Bridges from the start and not OVS Bridges, same result. This is the network config:
# network interface settings; autogenerated
# Please do NOT modify this file...
Hi, sorry for the late reply, I was on an two week vacation.
testing from inside the VM trying to ping its gateway:
tap131i0 sees it
v0074 sees it
ln_v0074 doesn't see it
vmbr0 doesn't see it
bond1 doesn't see it
trying to ping another VM that doesn't use the SDN VLAN but just vmbr0 bridge...
Hi Stefan,
I attached the ip a and ifreload output as it is too verbose for a normal post.
The journal looks like this:
root@node02:~# journalctl -u openvswitch-switch.service -b
May 21 18:03:33 node02 systemd[1]: Starting openvswitch-switch.service - Open vSwitch...
May 21 18:03:33 node02...
I was using a VLAN Zone with two VNets and it seemed to work well.
Yesterday evening I updated our staging environment to 9.2.2 and since then I can no longer get connectivity through those VNets - when I use the vmbr0 bridge directly and tag it on the VMs network interface, it works fine...