Search results

https://lkml.org/lkml/2016/11/19/158 About how long will it be until proxmox gets this patched in? I imagine will wait on upstream kernel?

Seeing same issue. Any resolution yet?

Are there any disadvantages of converting from privileged to unprivileged vs reinstalling? Is there anyway to make the Proxmox GUI default to unprivileged?

Is there anyway to get user quotas to work with LXC so we can install applications that require them such as Directadmin?

Has this been resolved yet or is it just not safe to do 3 drives in ZFS RAID 1 for some reason?

What is proper way to update Proxmox 3.x to latest Proxmox 3.x version? apt-get update apt-get upgrade Or is the "apt-get dist-upgrade" needed like on Proxmox 4.x?

Does this work on ZFS containers that are on ZFS raid1 type array? I assume not.

The one I did 2 x (4TB) in ZFS-RAID-1 did not do it. 3X seems too.

I have Proxmox 4.x installed on a 32gb RAM quad core box with a couple 4TB SATA drives installed using ZFS in raid 1 format. How will the disk random I/O speed of a Centos 7 XFS KVM running under Proxmox compare to if it were on bare metal? What I always liked about OpenVZ is there was not...

# zfs get recordsize NAME PROPERTY VALUE SOURCE rpool recordsize 128K default rpool/ROOT recordsize 128K default rpool/ROOT/pve-1 recordsize 128K...

I am not sure about using it with proxmox but I have used software raid mdadm on Centos servers over years and it has always worked great. Have also used it on proxmox 3.x and it seemed fine. With ZFS in proxmox 4.x I guess it is no longer necessary.

I am creating a Centos 7 VM inside Proxmox 4.x with ZFS. I plan on using Ext4 or XFS for a file system in the Centos VM. When setting up the disks on Centos should I use "Standard Partition", "LVM" or "LVM Thin Provision"? I would not mind the ability to make the root partition bigger down...

# cat /etc/pve/qemu-server/106.conf bootdisk: virtio0 cores: 1 ide2: local:iso/CentOS-7-x86_64-Minimal.iso,media=cdrom memory: 1024 name: rs2.************* net0: e1000=**************,bridge=vmbr0 numa: 0 ostype: l26 smbios1: uuid=******************************************* sockets: 1 virtio0...

I used IDE because it was default. Installed another VM with virtio. It seems to do same thing but not quite as bad. Trying to do a constant ping from VM while running the backup. Occasionally even get this error inside the VM. Message from syslogd@rs2 at Mar 3 10:52:36 ... kernel:BUG...

cat /etc/pve/qemu-server/104.conf bootdisk: ide0 cores: 1 ide0: zfs_storage:vm-104-disk-1,size=200G memory: 1024 name: resolver1.******** net0: e1000=*************,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 smbios1: uuid=*************************** sockets: 1

Thanks. So what is: "sockets: 1" vs "vcpus: 1"?

There was really not much/any change when the backup started and the VM started to freeze. Top and w did not really indicate the host was that bogged down. # zpool iostat 5 capacity operations bandwidth pool alloc free read write read write ----------...

After install on a ZFS RAID1 two drive array I created my storage pool like so: zfs create rpool/zfs_storage_pool Then in Proxmox I created: ID: zfs_storage ZFS Pool: rpool/zfs_storage_pool Enable and Thin Provision checked. Disk Image and Container The backups go to a separate Ext4 2TB drive.

I installed Proxmox 4 on a Supermicro motherboard, Xeon dual core X3430 2.4ghz CPU with 16GByte of ram. Installed using ZFS raid1 across two 4TB sata 7200 rpm drives. I also added a 2TB 5400 rpm sata drive formatted ext4 and use it only for backups. I created a KVM VM with 200GB space, 1GByte...

Changed from 1 core too 2 cores in Proxmox GUI. Now even after shutting down VM it seems to be impossible to change back too 1 core. Also, clicked on CPU Options and now cannot remove vmpus=1 from container. Is there a config file somewhere I can edit?