Search results

Does this also affect I/O Wait on KVM containers? Have always used OpenVZ containers but lack of user quota in LXC may force me to switch to KVM. My containers are I/O intensive. How will this effect me?

Will user quotas ever be possible in LXC containers? If I need them in the future will they work on ZFS or should I be using ext4?

How much longer will Proxmox 3 be supported?

I had proxmox 4.0 running for couple months then did apt-get update then upgrade to move to 4.1 proxmox. This is on Supermicro hardware with 3 sata drives using ZFS to do a RAID1 type setup. Everything seemed fine until I decided to reboot. No longer have access to server. Any idea what...

So how do unprivileged containers work in 4.1? How do we enable this? Can AppArmor safely be turned off now or how does that work?

I have an issue installing DirectAdmin on any machines without user quota abilities. Any idea when this will be ready? Is this due to ZFS file system? I am almost thinking of moving my latest Proxmox box from v4 back to Proxmox v3 where most things worked fine on openvz. Part of my issues...

>>> (we're experimenting with unprivileged container support, too, currently, so that could help). How is that going? Will that be introduced?

So I am assuming many services are going to encounter this? I see similar issue with httpd here. http://forum.proxmox.com/threads/23561-Issue-with-CentOS7-httpd-spawing-Permission-denied-(PVE4-beta-2) I am guessing its an issue that services cannot have a privatetmp inside a LXC container...

Has anyone tried this fix? http://forum.proxmox.com/threads/24416-Centos-7-LXC-Container-and-Bind?p=122896#post122896

I have a Centos 7 Openvz container running on Proxmox 3.x and DNS works without these changes. Is the reason for that AppArmor, LXC or what? Thanks.

I think I am. # apt-get update Ign http://ftp.us.debian.org jessie InRelease Hit http://ftp.us.debian.org jessie Release.gpg Hit http://ftp.us.debian.org jessie Release Hit http://ftp.us.debian.org jessie/main amd64 Packages Hit http://ftp.us.debian.org jessie/contrib amd64 Packages Hit...

# pveversion -v proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-57 (running version: 4.0-57/cc7c2b53) pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1 libqb0: 0.17.2-1 pve-cluster: 4.0-24 qemu-server: 4.0-35 pve-firmware: 1.1-7 libpve-common-perl...

When creating a new LXC Centos 7 container in Proxmox 4.x and I select use host DNS settings it uses an IP in 10.0.0.0/8 range, forget exactly what IP, rather then host DNS server.

After making this change to container I had to reboot it to get named to start. Now it does though. Does this change affect the security of the container? Is this something that will be fixed up stream eventually or do I need to do this every time I install a Centos 7 container on Proxmox 4...

I was moving one of my DNS servers to Proxmox 4. I created a Centos 7 LXC container and installed bind on it it with "yum install bind bind-utils". Named will not start. service named start Redirecting to /bin/systemctl start named.service Job for named.service failed. See 'systemctl status...

Seeing same issue. Cannot get named to start on a Centos 7 LXC container.

How do I tell if compression is already enabled? How do I see existing ZFS settings for partitions etc?

Is it best to enable compression?

So how do ssd cache drives work on ZFS?

The server will be located a good distance away and I like idea that raid1 with 3 disks will mean even if one disk in array fails I still will not have to be in any rush to replace it. As I understand looking at proxmox docs zfs supports raid-1 and raid-z1 among others. Z1 I am guessing is...