Search results

RESOLVED. Somehow disk image became readonly and even root couldn't move it or change permission. So I had to copy it to a new image. Then I used this new image as main in my 107.conf. Also, set up Tepmlate: 0 Today I've learned a new wisdom: don't mess with important data in friday at the end...

I made a big mistake by trying to create template of a container with a pct template 107 -experimental 1. How do I restore it to a running container? The raw image is renamed to base-107-disk-1.raw after this operation. proxmox-ve: 4.4-88 (running kernel: 4.4.62-1-pve) pve-manager: 4.4-13...

That's what I tried to do until I stuck on that TotalMem bug) Anyway, LA parameter is much more important for me. Don't want to update and reboot prod servers because only memtotal issue fix.

So, the issue is still unresolved. https://github.com/lxc/lxcfs/issues/13 Guess, the only decision is to wait for a patch

I'm running Proxmox based on Debian Jessie: lxc-pve - 2.0.7-4 lxcfs - 2.0.6-pve1 Hope they fixed this behavior in 2.0.8 release. And what about /proc/loadavg? Because I have the same issue with it

Then why /proc/meminfo shows MemTotal amount of the host, not the LXC container?

Eh, those are risky things for production environment) But, I guess, I have no other options. Thank you for response!

is it possible to make partial upgrade without reboot?

pveversion -v proxmox-ve: 4.2-66 (running kernel: 4.4.19-1-pve) pve-manager: 4.2-23 (running version: 4.2-23/d94f9458) pve-kernel-4.4.19-1-pve: 4.4.19-66 lvm2: 2.02.111-2.2+deb8u1 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-46 qemu-server: 4.0-88 pve-firmware: 1.1-9 libpve-common-perl...

oh, right, newer version of Proxmox has field Cores at container creation menu. So I tried to edit my container config and add cores: 2 but operation failed: pct stop 100 vm 100 - unable to parse value of 'cores' - unknown setting 'cores'

Hi! I'm having problem with resource limiting on Proxmox All CPUs of Proxmox host are available inside LXC-container, despite limit is set. pct config 100 arch: amd64 cpulimit: 1 cpuunits: 1024 hostname: test memory: 1024 net0: name=eth0,bridge=vmbr0,hwaddr=BE:C9:EB:5E:0E:15,type=veth ostype...

Hi! I'm using Zabbix to monitor my Proxmox containers and I faced the problem. Zabbix item for getting total memory vm.memory.size[total] returns amount of mem on Proxmox host instead of memory inside a container. Although, value MemTotal from /proc/meminfo is correct. Also, Zabbix uses...