Search results

  1. Firewall DHCP enabled

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

    For what needed option "DHCP enabled" ? I can setup any IPs on the VM with DHCP enabled and without.
  3. 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. 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. NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    No solutions for LXC. The servers was down and down every day.
  6. 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. 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. 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. NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    What limit did you set? 3k was not help me.
  10. NMI watchdog: BUG: soft lockup - CPU#5 stuck for

    Is irqbalance helped for someone?
  11. Unexpected disk util 100%

    During all time, when the disk busy was 100%, was many kernel errors. Short video -
  12. Unexpected disk util 100%

    The same issue on the other server one day ago.
  13. Unexpected disk util 100%

    Sorry, I said about %busy of course. It is a bug of munin. When you use all resources you have it can write incorrect information. Must be 100% of course. Can't access to the server at this moment.
  14. Unexpected disk util 100%

    Have not high iops usage, the disk latency was fine, but disk util 100%. I saw that two times with different nodes and only on LXC. Why it can be? Is that a bug of LXC?
  15. i/o disk limit

    IO limits dos not work on LVM-Thin.
  16. iostat into CT

    We use and VM too. But CT is cheeper. And the staff have access to guest system, so we can help to our client faster. Also we can share the drive, and we can't do it on KVM and save the snapshot at that time. CT use smaller memory then VM. And it is a simpler to setup CT from template and make...
  17. iostat into CT

    How can I hide to display block devices using iostat and other utils? Asking about LXC.


The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!