Ok, so without native support, what I had in mind at start, from what I see now...
Within a single Proxmox:
* create a namespace for each dedicated "zone"
* create bridges, firewall rules, ... in that namespace
* create veth, one in the "zone"...
I'm going to check the other things, but quick answer, turning off the ProxMox firewalls made no difference. Prior to changing subnets, and for another test Proxmox I installed, there were no communication issues (even with the firewalls on).
I found a solution for the other nodes to recognize the LVM of the LUN without having to restart the node.
The node that does not recognize this lvm must be able to recognize the disk, lsblk. In my case is sdc
NAME...
Hello,
You are mixing two VLAN models:
A VLAN-aware trunk bridge (vmbr0), which carries a VLAN trunk and transports tagged VLAN traffic
Per-VLAN access bridges (vmbr50, vmbr200), where tagging is done at the interface level (eno1.50 /...
Ok I configured the graceful shutdown and it worked perfectly. For me personally, this was a much better solution than NUT (although if I end up with a setup in the future with multiple servers connected to the same UPS - or something else...
i figured out how to get it installed.
i went into the proxmox shell and typed:
curl -o cyberpowerpowerpanel.deb https://www.cyberpower.com/tw/en/File/GetFileSampleByType?fileId=SU-18070001-06&fileType=Download%20Center&fileSubType=FileOriginal...
Hardware:
-sys-5029p-wtr
-LSI MegaRAID 9265-8i PCI card
-Intel cpu
Initially could not even get the installer to run, it would freeze on "loading initial ramdisk" but after some changes to the UEFI/BIOS boot options eventually got it installed...
Hello everyone. After updating Proxmox VE 8 using apt update and apt upgrade (now I know that needed to use apt dist-upgrade
instead) from 6.8.12-12 to 6.8.12-17 and rebooting Proxmox booted into emergency mode. Also before the reboot were many...
It seems to be there are instructions for converted source lists and old ones. E.g. the file debian.sources contains after conversion
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://ftp.nl.debian.org/debian/
Suites: trixie...
I've installed vm from template, did backup at every step, i've tried to restore previous backup and it worked
I've tried to backup it on another location and same error
i will try to move from this sources to another and test again
thanks
It seems like there are no rules generated (judging from the nft list ruleset output)
Is the pve-firewall service still running?
Did you enable the firewall on datacenter level? Otherwise no rule will be generated at all.
Hello,
You are mixing two VLAN models:
A VLAN-aware trunk bridge (vmbr0), which carries a VLAN trunk and transports tagged VLAN traffic
Per-VLAN access bridges (vmbr50, vmbr200), where tagging is done at the interface level (eno1.50 /...
Hello,
I recently upgraded pve 8 to 9 with UEFI. I checked I had systemd-boot-efi package correctly installed.
It did update my 2 NVMe EFI partitions automatically.
Get:1 http://ftp.fr.debian.org/debian trixie/main amd64 systemd-boot-efi amd64...
I've enabled 'NUMA node per L3 cache' for my (single socket) 5950X system. It does make it more clear which cores and threads are on which CCD. All I can really say is that it appears to work fine, but it also worked fine before.It seems to...
This is a additonal setting that can be set "NUMA node per L3 cache" but did you also try to set "Nume nodes per node" to a different value then the default? On my side its set to 1 at default. I am interested in knowing if more numa nodes is...
Hi,
if the same error is triggered in stop mode for backup the underlying storage or connection to the target storage might be the culprit. I would check smart values of the disk first.
Have you tried restoring the last backup?