Search results

When I login to a container and list mounts I see container's ext4 thin partition is mounted and data=prdered and I would like to change it as data=writeback. How can I do this since lxc.rootfs.options is depricated?

This helped echo 2 > /proc/sys/vm/drop_caches

ext4 with lvm thin pool as storage for CTs.

free -gh shows only 1GB of cache and 10GB of used memory. How can this be cache?

I have a small lxc container with 1GB of RAM but a large disk partition which is 800GB of images which are synced with rsync. While the rsync is syncing data over network the container RAM usage is max 10%. The problem is that the host's memory usage is increasing over time and finally gets to...

Does pct restore support any king of bandwidth limiting? Restoring from backup always makes the dedicated server not usable during the restore process....

I am getting closer :) Few more error, hope you can point me to the right direction vzdump 100 --stdout | ssh root@SERVER -- pct restore 226 - --rootfs data:20 can't use storage 'local' for backups - wrong content type command 'tar xpf - --totals --sparse --numeric-owner --acls --xattrs...

would something like this be possible? vzdump 119 --stdout | ssh root@remote.server.com | pct restore --rootfs 20 119 -

Thank you.

Restart did not help. Storage 'data' is lvm thin type.

This is just a test CT, still did not start. arch: amd64 cores: 1 hostname: test.server.com memory: 1024 net0: name=eth0,bridge=vmbr0,gw=10.10.10.1,hwaddr=4A:76:2B:83:18:EB,ip=10.10.10.198/24,type=veth onboot: 1 ostype: debian rootfs: data:vm-198-disk-1,acl=0,quota=1,size=8G swap: 512...

pveversion -v proxmox-ve: 4.4-80 (running kernel: 4.4.35-2-pve) pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74) pve-kernel-4.4.35-2-pve: 4.4.35-79 pve-kernel-4.4.40-1-pve: 4.4.40-80 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-1 libqb0: 1.0-1 pve-cluster: 4.0-48 qemu-server: 4.0-109...

Is this a bug? If you ask me this is since you can not create and normally start an unprivileged container....

Fixed. Open you ct's conf file as /etc/pve/lxc/ID.conf and append lxc.autodev: 0

I juct sreated mu debian 8 ct as an unprivileged container and got an error 'failed to run autodev hooks for container' .... Is there a way to fix this?

Hi dietmar, Is this something I can hide or do I have to wait for the lxc team to implement something? Thanks

I notices when logged inside lxc container if I do cat /proc/partitions I will have access to hosts's partitions. Is there a way to hide host's partitions? pveversion pve-manager/4.4-12/e71b7a74 (running kernel: 4.4.35-1-pve)

Do you plan to support OpenVZ 7.0? http://openvz.livejournal.com/53870.html

Paste output of df -hi

The server I used was idle, running few test lxc containers and one kvm machine. The server is Enterprise MG-128 - 128G 2xE5-2630v3 Server with RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2208 [Thunderbolt] (rev 05)