Recent content by Andrii

  1. A

    Firewall DHCP enabled

    Do you mean this allow to use DHCP if all other ports are DROPed?
  2. A

    Firewall DHCP enabled

    For what needed option "DHCP enabled" ? I can setup any IPs on the VM with DHCP enabled and without.
  3. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    Is it possible to convert LXC to OpenVZ? - - - Why you support so unstable virtualization like LXC and remove stable OpenVZ? Very stupid decision! Sorry, but it's true.
  4. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    Did not help. But today I was on the server at this moment. avg CPU usage was 50%. One CT with cpulimit 0.8 and cpuunits 8 start to use 100% of 1 core (see in top). load average was 200. When kill the process LA stay lower. Then again have high LA, and NMI watchdog: BUG: soft lockup - CPU#5...
  5. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    No solutions for LXC. The servers was down and down every day.
  6. A

    Unexpected disk util 100%

    #Start arch: amd64 cmode: console console: 1 cores: 1 cpulimit: 0 cpuunits: 1024 hostname: server memory: 2048 net0: name=eth0,bridge=vmbr0,firewall=1,gw=185.162....1,hwaddr=9E:7E:27:93:3A:F8,ip=185.162...../24,rate=6,type=veth onboot: 1 ostype: centos rootfs: lvmthin:vm-500-disk-1,size=10G swap: 0
  7. A

    Unexpected disk util 100%

    I could not find the reason why this happened. LXC is a very unstable. We migrated 5 nodes from OpenVZ to LXC and now have a downtime every 2 days.
  8. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    30-50 CT. But mostly it uses for VPN and other lite service. At least 50% CPU are free. OpenVZ was more stable (( How do you detect these "bad" containers?
  9. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    What limit did you set? 3k was not help me.
  10. A

    NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    Is irqbalance helped for someone?
  11. A

    Unexpected disk util 100%

    During all time, when the disk busy was 100%, was many kernel errors. Short video - https://screencast.com/t/a6iELIP9l9dl