Recent content by masterdead

  1. M

    Starting node takes 10 minutes... before boot

    Can you pls start this VM via CLI and paste output here?
  2. M

    Starting node takes 10 minutes... before boot

    Did you try start node from CLI? Do you use external mounts like nfs?
  3. M

    Loading kernel modules... ERROR: could not insert 'configfs': Exec format error

    I lost quorum in cluster (without touch). I dont know why, because only 3 nodes from 16 are affected with this problem, and after reboot affected nodes, cluster goes to hell. Corosync processes growing in memory to full utilization of available ram (64gb ram on server, and corosync process have...
  4. M

    Loading kernel modules... ERROR: could not insert 'configfs': Exec format error

    I have same problem, but my cluster (with 16 nodes) has broken and i must restart nodes with 2.6.32-37 kernel. After reboot broken nodes i must restart cman and corosync on all nodes. That is problematic when cluster have 300+ virtuals. This problem becomes very often, when i running on kernel...
  5. M

    Jessie and 3.10.0 OpenVZ kernel and the future

    OpenVZ kernel for 3.10 is already here > https://src.openvz.org/projects/OVZ/repos/vzkernel/browse but still is under development :/
  6. M

    Slow Network, High CPU Usage, Large data files,

    What kernel do you use? Did you try 3.10? Check, if server has installed irqbalance and check context switches and interupts.
  7. M

    /dev/mapper/pve-root full

    Or try this method http://forum.proxmox.com/threads/18349-root-partition-quot-full-quot?p=93732#post93732
  8. M

    High CPU-load kipmi0

    I have same problem with dell servers and proxmox v3. When i'm restart iDrac, kipmi goes to 100%
  9. M

    /dev/mapper/pve-root used 100%

    Try this http://forum.proxmox.com/threads/18349-root-partition-quot-full-quot
  10. M

    ksoftirqd/0 high cpu usage

    have you installed irqbalance? install from https://packages.debian.org/wheezy-backports/irqbalance More info in /proc/interupts
  11. M

    proxmox 3.2 new installation and unable to start VMs

    You dont have virtualization support, or its not enabled in bios.
  12. M

    root partition "full"

    Try this: Create dir in for example /mnt/temp-root mount /dev/pve/root /mnt/temp-root du -shx /mnt/temp-root/* The most situation, when is at to root mounted another file system like pve-data has no reporting data "under" the mount.
  13. M

    Clean install proxmox

    do you have enabled virtualization in bios? or you cpus have virtualization support?

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!