Latest activity
-
Sspooner replied to the thread Internetzugriff auf Proxmox VMs / Docker Container hinter OPNsense mit Reverse Proxy.Guten Morgen Zusammen und frohe Ostern wünsche ich. Vielen Dank für die Infos. Ich hab bisher auch wenig Erfahrungen mit Docker, weil ich bisher einfach auch immer eher eine VM vorgezogen habe, als ein Docker Container. Obwohl das Prinzip eines...
-
OOther7544 replied to the thread LXC - Omada memory leak?.Thank you @RianKellyIT Option 1 is no go, so I'll try the environment variable JAVA_OPTS path. I assume that goes into the LXC Console, not the node Shell? Interestingly I noticed there was an Omada update to v6.2.x. This came out around the...
-
OThe memory growth is almost certainly the JVM not respecting the LXC container's memory limit. By default, Java allocates its heap based on what it sees as the system's total RAM. In an LXC container, older JVM versions (and even some newer ones...
-
MMikeWebb reacted to naptime's post in the thread Problem/message L1TF CPU bug and data leak with
Like.
NOTE: [Proxmox 8.2.2] These steps worked for me but by choosing correct filename as shown below: Incorrect path filename: nano /etc/kernel/cmdfile Correct path filename: nano /etc/kernel/cmdline -
RRianKellyIT replied to the thread LXC - Omada memory leak?.The memory growth is almost certainly the JVM not respecting the LXC container's memory limit. By default, Java allocates its heap based on what it sees as the system's total RAM. In an LXC container, older JVM versions (and even some newer ones...
-
Sskraw replied to the thread corosync show link flapping (down/up) about every 3-4 minutes, but switch shows no problem.No, I don't have a fine-grained monitoring, and really, this is not exactly the point. I am very sure that all your working nodes are built on an empty network, just like the proxmox doc for corosync says. The thing is this: if I have even an...
-
SteveITS replied to the thread Cluster setup and HA configuration suggestions.Read through https://forum.proxmox.com/threads/fabu-can-i-use-ceph-in-a-_very_-small-cluster.159671/. 3 nodes will technically work but as soon as you reboot one you’re at the minimum 2 replicas. You don’t give disk sizes on the first two but... -
MMaiyannah replied to the thread Suddenly unable to access web UI.So in: pveversion -v ~# pveversion -v proxmox-ve: 9.1.0 (running kernel: 6.17.4-2-pve) pve-manager: 9.1.7 (running version: 9.1.7/16b139a017452f16) proxmox-kernel-helper: 9.0.4 proxmox-kernel-6.17: 6.17.13-2 proxmox-kernel-6.17.13-2-pve-signed...
-
RRedSam posted the thread Intel GPU PCI Passthrough with Windows 11 (Code 43 Error) in Proxmox VE: Installation and configuration.Hi, I'm running proxmox on a mini-PC with Intel Core i9-12950HX processor (Alder Lake, 12th Gen) with Integrated Intel UHD Graphics. I'm trying unsuccessfully to get GPU pass-through with Windows 11. PCI pass-through for USB mouse and keyboard...
-
Kkryrena posted the thread Cluster setup and HA configuration suggestions in Proxmox VE: Installation and configuration.Hi all, I’m putting together a Proxmox cluster with Ceph for HA and wanted to get some feedback before I go ahead and deploy everything. What I’m aiming for is fairly simple: I want proper HA with no data loss and automatic failover, but at the...
-
SSgingold replied to the thread Reboot stuck on GRUB and reinstall attempt doesn't get past Install screen.Thanks for replying again. I tried all your suggestions and the installer just can't get past the first screen. Here's my most recent attempt using Ventoy: Here's the latest iso. I hit enter and get here: Enter again Just like earlier...
-
-
CCycloneB posted the thread [SOLVED] DegradedArray alert day after upgrading pve8 to 9 in Proxmox VE: Installation and configuration.I need some help understanding the alert I received today. I'll give some background, but I'll hide it as a spoiler in case the extra detail isn't relevant. Today I received the following alert: DegradedArray event detected on md device...
-
SSoepgroenten replied to the thread RTX 5080 VFIO passthrough fails on Proxmox VE 9.1 with error getting device from group 13: No such device.Nope MSI main board and VGA in combination with a core 9 ultra 285h (if that makes sense). From what I've read, the VGA isn't able to wake up from d3cold state because the VGA is claimed before it can be used by the VM or container.
-
RRianKellyIT replied to the thread NFS Share on Synology DS218+,.Just to circle back on the DNS angle, because I think the reverse lookup theory was dismissed too quickly. Even though you are connecting to the Synology by IP, the reverse DNS lookup happens on the Synology side, not on Proxmox. When your...
-
PPaddraighNet replied to the thread SDN Simple Zone: SNAT not working with nftables (Tech Preview).The symptoms point to a chain priority ordering issue between the nftables firewall and the NAT rules. When DNS queries go out, the SNAT/masquerade works on the outbound path. But the return DNS response arrives at the host's public IP and needs...
-
Ssmallbear4 replied to the thread CPU limit for VM not working as expected.Thanks for the tip, but that didn't have an effect on this specific issue. As a comparison, I tested OPNsense on bare metal using the same machine. I can get full link speed (~1 Gbps) and the system only draws about 19 W when running the speed...
-
Wweskezm99 replied to the thread Change proxmox logo and link.I previously had luck with the following but it no longer works on pve 9, maybe someone else can use this to figure out 9 if I don't sed -i "s|href: 'https://www.proxmox.com',|href: '/',|g"...
-
Bbluesite replied to the thread ToughArmor MB902SPR-B R1 wird nicht erkannt.also laut Beschreibung hat das Board nen M.2 E Key Slot da könnte man dann sowas hier reinmachen https://www.ebay.de/itm/195207912302 Wenn Du kein Wlan benötigst
-
AAFAIK, exim is the debian default MTA. However, proxmox LXC templates for debian come with postfix installed instead of exim. And, most of all, the /etc/mailname is not created and populated at configuration. This breaks the installation or...
-
AThis actually works, but if I failed a drive via the zpool command it didn't send me a notification as I guess it was an expected consequence. It did work when I pulled a drive out.
