Recent content by MichaelA

  1. M

    KVM: Cannot allocate memory

    Please read my previous post. This is 'by design'. Briefly: make sure all the virtual machines configs (by config but not by real usage) in sum do not exceed total RAM available.
  2. M

    KVM: Cannot allocate memory

    Well. Got it! Everything were right. For example, we have 10Gb RAM node with 6 virtual machines (2Gb RAM per each). We start first VM. It allocates all 2Gb but actually uses 1Gb. Command free shows me 9Gb RAM free but actually I have just 8Gb. If we start 5 VMs which use just 7Gb RAM command...
  3. M

    KVM: Cannot allocate memory

    In messages and kern.log - nothing, syslog and daemon.log just repeats the same what I'm seeing myself in command line (STDERR). This is strace part before error:
  4. M

    KVM: Cannot allocate memory

    Seems to be this is not PVE issue but for whole operation system.
  5. M

    KVM: Cannot allocate memory

    Upgraded server - same issue. New data for discussion: # free total used free shared buffers cached Mem: 65963352 10178520 55784832 0 22792 93792 -/+ buffers/cache: 10061936 55901416 Swap: 3998712 0 3998712...
  6. M

    KVM: Cannot allocate memory

    Hello. I have KVM virtual machines on host with 64Gb RAM. Now total usage of RAM by them achieved almost 30Gb. And I can't start more: # qm start 213 Failed to allocate 4294967296 B: Cannot allocate memory start failed: command '/usr/bin/kvm -id 213 -chardev...
  7. M

    Wrong access right in /etc/pve

    I catched the quorum and got a result: root@node1a ~ # pvecm expected 1 root@node1a ~ # pvecm status Version: 6.2.0 Config Version: 6 Cluster Name: nodesquad Cluster Id: 55506 Cluster Member: Yes Cluster Generation: 52 Membership state: Cluster-Member Nodes: 1 Expected votes: 1 Total votes: 1...
  8. M

    Wrong access right in /etc/pve

    Yes, you right: root@node1a ~ # pvecm status Version: 6.2.0 Config Version: 6 Cluster Name: nodesquad Cluster Id: 55506 Cluster Member: Yes Cluster Generation: 52 Membership state: Cluster-Member Nodes: 1 Expected votes: 2 Total votes: 1 Node votes: 1 Quorum: 2 Activity blocked Active...
  9. M

    Wrong access right in /etc/pve

    Hello, folk. I've got issue when Proxmox hasn't access to the configs from Web-GUI. When I look at file system I see 440 instead of 640 as expected: root@node1a /etc/pve/nodes/node1a/qemu-server # ls -l total 6.5K -r--r----- 1 root www-data 202 Jan 5 11:43 100.conf -r--r----- 1 root...
  10. M

    cannot access /etc/pve: Transport endpoint not connected

    Both servers are in different networks (and even in different cities) and no multicast available. Don't I have chances? :(
  11. M

    cannot access /etc/pve: Transport endpoint not connected

    Will explain from begining. I want to connect two nodes: node1a (v.2.0-18) and node1b (v.2.0-18) What I've got at node1a: What I've got at node1b: Now I try to add a node1b to cluster: And what I've got at node1a: And on node1b:
  12. M

    cannot access /etc/pve: Transport endpoint not connected

    Thank you. Mount with pmxcfs works like a charm. But why I still can't create a file/dir in /etc/pve ?
  13. M

    cannot access /etc/pve: Transport endpoint not connected

    Same issue on version 2.0-18 And the directory /etc/pve particulary empty: Where the rest files could gone (they were before adding this node to cluster)? And there is no way to create there anything: permission denied (under root, whith no chattr +i and rw mount). Restarting cluster...

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!