Search results

Upgrade to 4.15 kernel.

kernel 4.15 solved the issue

Are you sure about this? I was just giving an way to achieve what Valerio needs, which I have tried and worked for me. If you have another way answer to him,

You can create new guest and restore any other guest backup, there is no issue. I do it all the time. I have 25 live nodes with atleast 10 guests each. Rather than editing MAC and making mistake, it is better to delete network device and add it. That is what i do when i clone a guest.

Create a new CT/KVM then restore backup to it. Then before starting it remove and add network device. It will get a new MAC. With same MAC it will not work.

You have SSD or SATA drives? For SSD drives you could ignore these errors to some extend. Select node - Disks - look at Wearout value for your SSD drive, up to 50-60% it is ok. I don't mean drive is ok, but we can ignore, after that it is time to replace the SSD drive.

Obviously not possible. If you have 16 cores/16GB memory in the node, you can create 10 KVM/VT each with 16 cores/16GB memory. But for a single KVM/CT you can not have more than 16 cores/16GB memory.

I upgraded all 25 live nodes to Kernel 4.15 and everything is running fine for last 24 hours. Now 4.15 kernel is available in no-subscription repo.

I am using this method now and it works fine. LXC extra IP with different subnet adding steps. If LXC has different subnet than extra IP........ First add interface eth0 via GUI in the Node for the guest Then login to guest and create extra config file for each IP. 1] login to proxmox...

On reboot LXC loses all extra IPs. I am adding eth1 with new IP, but on reboot it is gone.

Actually kernel 4.13 has 3 issues 1. LXC starting issues. 2. kworker using 100% CPU 3. Extra IP in LXC is gone after restart. Kernel 4.15 solved issue some issues For example issue 1. is solved with kernel 4.15. I am still testing issue 2. with kernel 4.15 inb 25 live nodes, no issues so...

LXC extra IP with different subnet adding steps. If LXC has different subnet than extra IP........ First add interface eth0 via GUI in the Node for the guest Then login to guest and create extra config file for each IP. 1] login to proxmox select CT XXX > Network > add one NIC with...

Try with new kernel 4.15.

I ran kernel 4.15 for 54 hours with 5 LXC with cron to stop and start every 5 minutes. No issues at all.

I had same issue running kernel 4.13 with 25 live nodes, Kworker using 100% CPU. Now I moved all 25 live nodes to 4.15 kernel, no issues so far.

I stopped the test. It ran 54 hours without an issue. And I moved all my 25 live nodes to kernel 4.15, no issues so far.

We also face same issue. On reboot all LXC loses all extra IPs. what is exact procedure to add second IP? I am adding eth1 with new IP, but on reboot it is gone.

48 hours passed, no issues.

I set it to 10 minutes now. My SSD may wear out. I have 5 LXCs.

36 hours passed, no issues.