Search results

I found the problem, but not the solution. After creating and/or removing some interfaces in the Server Network configuration site und "Apply Configuration" some IPv6 Connection from VMs starts to flapping. After restarting the entire Server everything was fine again. So it happens when...

I updated my (non-subscription) pve server some days ago and had a lot of trouble with IPv6. After upgrading today everthing is fine again. I guess there was a bug in the kernel (or other?) before. Additional I saw some threads with IPv6 problems here recently. pve-kernel-5.13.19-2-pve ->...

That is a common mistake with proxmox on hetzner servers. You must not using a bridge to your public interfaces. You have to use a routet solution. Background: pve creates another virtial device (for firewalling) with random mac adresses for each host and put in the bridge too. So hetzner will...

Wenns Probleme mit Platten gibt sieht man das im Regelfall zuerst in dmesg. Wenn dort was steht liegts zu IMHO 90% an defekten Kabeln. Gibts die Möglichkeit die Kabel versuchsweise zu tauschen bzw. die SSD mal an einen anderen Rechner anzuschliessen? Wenn ich nicht mehr weiter wüßte würde ich...

Are your sure the FORWARD is ACCEPTed in iptables? Please post output from "iptables-save".

I can confirm some trouble with network speed, in particular in VMs. LXC containers are not affected. I tried E1000, virtio and RTL8139 network adapters in VM, virtio is the fastest, but got only max 460Mb/s from 1000Mb/s available. Very strange. Maybe a bug in newer kernel/qemu versions? Not...

Hab mich auch mal versucht zum Thema einzulesen und folgenden Post gefunden, daher hier mal kurz hinzugefügt: https://www.ikus-soft.com/en/blog/2017-02-25-proxmox-kvm-vs-lxc/ grobe Zusammenfassung (Stand 2017): wenns um Rechenleistung geht alle annähernd gleich, bei Platten-IO liegt LXC vor KVM.

The Wikipage https://pve.proxmox.com/wiki/Renaming_a_PVE_node is outdatet/not complete. I renamed a PVE 7 (standalone) instance and after the reboot no VM/CT came up. Failure: Configuration file 'nodes/$NEWHOSTNAME/lxc/100.conf' does not exist and so on. So it looks like the folder...

I can confirm, this did the magic: # systemctl edit container-getty@.service fill in: [Service] ExecStart= ExecStart=-/sbin/agetty --autologin root --noclear --keep-baud tty%I 115200,38400,9600 $TERM Save & reboot. Tested with Debian.