Latest activity

  • J
    In this particular case, the situation and environment are quite complex, so there is no single approach that can be universally considered the “best.” However, if the goal is to ensure a stable and reliable recovery, the following approach can...
  • D
    Based on the screenshot, VM102 exists on node2, but the issue is that the VM disk vm-102-disk-0 exists on local-lvm of Server3. I am not sure why vm-102-disk-0, which should originally have been on local-lvm of node2, was moved. However, in this...
  • UdoB
    UdoB reacted to psalkiewicz's post in the thread Proxmox multi-ring corosync with Like Like.
    Hi, There are 2 issues in your config - the main issue is MTU flapping. KNET's Path MTU Discovery runs globally across all links. When a node rejoins on link 0 (eno1, MTU 1500), KNET resets the global PMTUD process for that link. While it's...
  • UdoB
    I would further slow down. My goal would be to adjust to the speed the PBS is actually capable to absorb - to keep the fleecing file small. If that runs stable I would (relatively) slowly increase the bwlimit. Just my thought... and a very slow...
  • P
    Hmm, “classic” is probably the right word here, in the sense that it’s usually not done this way anymore nowadays ;) Isn’t that a bit overkill for a homelab? I mean, unless you are trying to replicate a large enterprise environment with...
  • P
    Hi, The hard disk is on another node. The local-lvm datastore is local to the host - not a shared storage. So when a virtual machine failed on one host it cannot be restarted on the other. You have to move the virtual machine back to the other...
  • A
    AidanWV reacted to aaron's post in the thread RAM Display Bug on PVE 9.0.3 ? with Like Like.
    Memory accounting gets complicated very quickly once you peek a bit behind the curtains. First of, a VM doesn't necessarily use all the memory right after boot. Linux VMs that don't need most of their memory for example. With the new line in the...
  • P
    Hi, I would start with the memory. The two fleece images together preallocate metadata for ~3TB — this can push memory usage over the edge after days of uptime with gradual memory pressure. Please check if it's not out of memory type of issue...
  • A
    AidanWV reacted to aaron's post in the thread RAM Display Bug on PVE 9.0.3 ? with Like Like.
    This is regarding the VM summary panel on Proxmox VE. In your screenshots you have "Memory Usage" with the line chart and one line below that is the "Host memory usage". Those values are the same in both screenshots → Proxmox VE did not get any...
  • P
    Yes, I believe that is a classic setup. And yes, there are two fully fledged firewalls. One on the edge to the internet and one behind it at the edge of my private LAN. It does seem so. Unless, of course, Proxmox take up my suggestion to have...
  • P
    psalkiewicz replied to the thread Proxmox multi-ring corosync.
    Hi, There are 2 issues in your config - the main issue is MTU flapping. KNET's Path MTU Discovery runs globally across all links. When a node rejoins on link 0 (eno1, MTU 1500), KNET resets the global PMTUD process for that link. While it's...
  • D
    In this particular case, the situation and environment are quite complex, so there is no single approach that can be universally considered the “best.” However, if the goal is to ensure a stable and reliable recovery, the following approach can...
  • P
    Only the VMs live in the DMZ. The PVE that serves them does not. The PVE management interface, of course, is on a separate management network and not reachable from the DMZ.
  • powersupport
    This issue does not look like a CPU or RAM problem. The behavior you described (GUI freezing for 10–15 minutes and then recovering) is usually related to storage I/O delays. Since you have around 200 VMs, it’s possible that too many backups...
  • P
    Up to now, it has been my policy to not allow anything from the outside into my inner firewall. Ideally, I would like to keep it that way. If no viable other solutions exist, port forwarding would indeed be an easy option. But how would I...
  • P
    Up to now, it has been my policy to not allow anything from the outside into my inner firewall. Ideally, I would like to keep it that way. If no viable other solutions exist, wireguard certainly would be an option. And how would I use that to...
  • P
    Or wait, do you mean that by “inner firewall” you are actually doing double NAT? Internet → NAT on Firewall 1 → DMZ → NAT on Firewall 2 → LAN? Are we even talking about actual firewalls here, or just two routers placed behind each other? If the...
  • K
    Hello, We have a 7-node hyperconverged cluster that was originally running Corosync on a single ring over eno1 (copper, MTU 1500) without issues. To introduce redundancy, we added a second network using a bonded Mellanox interface (bond0)...
  • A
    Hallo Forum, ich habe ein einem zfs pool eine defekte Platte die ich austauschen will. Hat das jemand schon mal getan unter Proxmox? Wie gehe ich am besten vor? Es wäre nett wenn mir jemand hilft die richtigen Schritte zu tun damit ich kein...
    • 1775983925058.png
  • news
    news reacted to UdoB's post in the thread Proxmox installing to incorrect nvme disk with Like Like.
    My thoughts: Erase both disks. Completely! (If you just delete partitions some signatures may still be present.) Use any rescue image to boot and run something like "dd if=/dev/zero of=/dev/nvem0 bs=1M status=progress" for both of them. Remove...