Search results

I had two issues. 1. LXC failing, and node restart clears issue. But it still happens. 2. LXC failing, and even node restart didn't fix issue, I had to do some patching for TUN/TAP to work, then it started. No more issues. Both were converted from OpenVZ. Your CT is fresh? or converted from...

I have upto 20 LXC containers. All working fine now.

What is your Proxmox Version?

I have L5640 duel processors. Updating BIOS seems like solved the issue.

Space VS speed, that is your decision.

Your issue got solved after upgrading BIOS? I have a Dell C6100, i think i will try updating BIOS.

If you have more than two windows 2012 KVM you really need SSD drives. With SATA drives, it is going to be dead slow. Always use Virtio drivers for everything, that gives best performance. For drives sue SCSI Virtio drivers.

It is same issue. https://forum.proxmox.com/threads/proxmox-5-1-46-lxc-cluster-error-job-for-pve-container-101-service-failed.41878/ We need Kernel 4.114.20+ to get this issue solved.

I am using Balloon driver for windows 2012 successfully. For an 8GB KVM it as using almost 8GB earlier, after installing Balloon driver, it is reduced to less than 2GB.

Use RAID1 with 2x1TB for Proxmox (local) and RAID5 with SSD drives for VM storage.

What it really matters is you need SSD drives. i7 will work fine if you have SSD drives.

I have almost 25 nodes in 5 clusters, all have same issue. Still waiting for new version with kernel 4.14.20+

5.1.46 also has same issue. I also have same issue https://forum.proxmox.com/threads/proxmox-5-1-46-lxc-cluster-error-job-for-pve-container-101-service-failed.41878/ It is not LXC bug, it is Kernel bug with version 4.13.13. We have to wait for next release with with kernel 4.14.20 .

I have 25 Nodes which are having issues. I reduced ARC size from 8GB to 1GB, and surprisingly, issue is reduced. (not completely gone though) https://forum.proxmox.com/threads/proxmox-ve-5-1-zfs-kernel-tainted-pvestatd-frozen.38408/ This post helped. ARC Size...

It is very useful. I reproduced same error, it never matters LXC is converted from openvz or new LXC, all has issue. And it is random. We need to wait for the next release.

Searching more on internet, it is a kernel bug, not an LXC bug. Kernel 4.14.20 has issue fixed. We have to wait and see when we get updated patch from Proxmox. https://github.com/lxc/lxc/issues/2141

Issue is there on fresh containers also. I took a fresh node and just installed 4 containers, left it like that. And when i tried to stop and start, issue happened. I have 25 nodes, issue happened on all nodes atleast once in last 5 days time.

I like your idea. But, Is it better to wait until a new version comes with the issue solved? There should be many people using LXC with proxmox 5.1, they must be facing same issue.

uname -a Linux T064 4.13.13-6-pve #1 SMP PVE 4.13.13-41 (Wed, 21 Feb 2018 10:07:54 +0100) x86_64 GNU/Linux I also have same version. Any new version available?

I also have exactly same problem.. I have 5 clusters with 5 nodes each. All clusters has same issue. I didn't know LXC has so many issues. I should have stayed with openvz. KVM has no issue in promxox 5.1 though.