Recent content by gallew

I ended up with: auto eth0 iface eth0 inet static address XX.XX.XX.XX/XX gateway NN.NN.NN.NN offload-gso off offload-gro off offload-tso off offload-rx off offload-tx off offload-rxvlan off offload-txvlan off offload-sg off offload-ufo off...

Apparently it is not fixed. Just got it from freshly installed instance: Jan 12 12:27:07 dev06 kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: TDH <a5> TDT <3> next_to_use <3> next_to_clean <a5> buffer_info[next_to_clean]...

Thank you nikc. Proxmox node connection can be a little sipler. You don't actually need to assign IP address for your NIC, it is enough if you have address on your first bridge. My setup is like that: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto vmbr0 iface vmbr0...

Look at this thread please. https://forum.proxmox.com/threads/proxmox-node-freezes.44618/

Click to "Datacenter" There is "Storage" and there you can select storage and there is a button "Remove"

I'm not sure, maybe developers can confirm it but i my case, i have changed network config via web only once, and that was long time ago, but i did not notice that something were missing. I guess that best way to do it would be to test if parameters are still there on not after network...

Big dido here about fixing kernel module. Unfortunately after running little bit over two months, one of machines suffered again from e1000e hang. Investigation showed that still, e1000e module hangs repeatedly, regardless of checksum offloading. There was many hangs in log, but latest took...

Can confirm. AFTER you configure replication, used size in ZFS pool is doubled. ZFS is created as: zpool create -f -o ashift=12 data mirror /dev/sda4 /dev/sdb4 As you can see, for example VM 513 disk image in GUI shows as 32GB, but in CLI, it shows as 65.2GB, doubeled, as all VM image disk...

I had same problem with Hetzner machines (two clusters). I don't know if it helps, been running 2 weeks now without problems (knocking on wood), so i think it is worth sharing: # e1000e module hang problem /sbin/ethtool -K eth0 tx off rx off When executing, expect second or two outtage. I use...

Why this happens (and how to avoid swapping, if you have enough RAM) is covered in: https://forum.proxmox.com/threads/swappiness-question.42295/page-2 > I always hear the same "you need swap in case you run out of ram" crap. And what if you run out of swap too? Remember, everyone don't have...

So, until fixed do: 1) create file /etc/rc.local (if it does not exist) with content: #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or...

If after deletion disk space does not become available, then some process must be accessing that file. Try: "lsof -n| grep FILENAME" to find out, what process access it, and restart this process. If lsof is not available, then "apt install lsof"

Update 3: since some proxmox processes (pveproxy for example) gets restarted (in case of ssl cert update for example), it will inherit cgroups swappiness parameter. So in order for proxmox processes not to use swap you'll have to also change cgroup swappiness, otherwise, after process restart...

Oh, that's is a long topic. Cluster in hetzner is set up using udp, since hetzner does not support multicast. Fore shared storage, i use NFS on every machine, but i use NFS storage only for live migration. I move vm disks from ZFS to NFS, then migrate server, and then on new node, move disks...

For every failover IP address, you'll have to create route in node. Example: ip r add FAIL.OVER.IP.ADDRESS/32 dev vmbr0 Actual problem is, if yo want to do live migration between cluster nodes, then you have to: 1) migrate VM 2) change default route inside VM 3) remove route from source node 4)...