Search results

yeah, or you go via the GUI and add a Linux VLAN Device.

I would by now set up the VLANs via the SDN. That makes it easy if you have more than one node. Even with only one physical interface, the config will most likely not change much. The VLAN 209 for MGMT only, should be configured as mentioned. Then you can configure a new VLAN zone in the...

first of, why do you have that many bridge ports? If you want network redundancy, look into bonds! Adding many bridge ports is like plugging in multiple cables to the same switch. If those bridge ports connect to the same physical switch, you got a few ethernet loops... should vmbr0.209 only be...

Hast du mal nachgeschaut, auf einer Node die noch läuft? In /etc/pve/nodes/pve3/qemu-server, bzw lxc sollten die configs liegen. Wenn kein HA aktiviert ist, was die Gäste automatisch recovered, musst du das von hand machen. Z.B. mit mv /etc/pve/nodes/pve3/qemu-server/103.conf...

/etc/pve/qemu-server und /etc/pve/lxc (OpenVZ ist noch da, aber wohl schon lange nicht mehr verwendet) zeigt immer die lokale node. Aber unter /etc/pve/nodes/NODE/... sollte die Ordnerstruktur für alle Nodes da sein. In der GUI sollte aber auch noch ersichtlich sein, welche Gäste auf der...

Changing the Ceph cluster network is easy. Change it in the config file and restart the OSDs. Only one host at a time! systemctl restart ceph-osd.target. The Ceph Public network is a bit more involved because it is not just the config file. The Ceph MONs also have their internal monmap. The...

Hier scheint nur das Debian Security Repo konfiguriert zu sein? Das reguläre Debian Repo scheint zu fehlen. Entsprechend wirds da wohl zu Problemen kommen.

Just out of personal experience, filling all 4 slots with DIMMs and setting a faster XMP profile, default is 3600, everything above is overclocking with profile, would cause one host with an AMD 7900X to behave glitchy and reboot occasionally out of the blue. Setting the RAM speed slower, to...

in /etc/hosts, change the second line back to the FQDN and single hostname the machine had before. Also check if /etc/hostname contains the correct hostname. Then try to run ifreload -a to apply the config from /etc/network/interfaces again or reboot the host.

On a wild hunch, how many memory slots are populated and at what speeds is the memory configured? I don't have that particular Ryzen CPU, but had similar issues with all 4 RAM slots populated and an XMP profile enabled. Only after setting the memory to the base speed without any XMP profile did...

The remaining node is now basically in this scenario https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_separate_node_without_reinstall Follow the steps on this node until the pvecm delnode command (which would be on a node still in the cluster)

Wait a second, what if you go to the web UI and list the contents of the storage? Do you see the disks? Because in a non-HCI variant, you need to provide all the necessary infos to access the external cluster to the RBD command. The RBD storage plugin of PVE is doing the same...

The Ceph cluster reports HEALTH_OK? Can the PVE node reach(ping) the Ceph MONs and other potential Ceph nodes? You don't by any chance use a large MTU that might not work as expected anymore?

Ich wäre sehr vorsichtig andere MGMT utilities zu installieren. Im schlimmsten Fall grätscht es in PVE rein und verkonfiguriert Dinge die dann mühsam zum Troubleshooten sind.

Users that were created in the PVE realm or PAM? PAM realm users are backed by the local linux users via the PAM system. PVE users will most likely have a second file for the password hashes. Check with ls -l for any files starting with a dot, or/and in the /etc/pve/priv directory.

could it be the same thing as a few years ago? https://forum.proxmox.com/threads/blurry-font-text.91015/#post-398802

The PBS is a backup target. It does not offer any other kind of storage functionality out of the box. But, it is based on Debian Linux. Therefore, no one is stopping you to set up a ZFS dataset and export it as NFS, or install iSCSI tools and configure it as a target for iSCSI over ZFS. How...

You could also pin an older kernel version: proxmox-boot-tool kernel list proxmox-boot-tool kernel pin {kernel} No need to downgrade the full node. Those were released in 2012 if I am not mistaken? I would be prepared that they will be more and more of a problem in the future.

systemctl stop ksmtuned.service systemctl mask ksmtuned.service´ will stop and mask it, so it can't be started in the future.

What exactly do you mean? And is this maybe an answer to your question? https://forum.proxmox.com/threads/feature-request-cinder.140890/#post-632575