Search results

it seems like there is also no number allowed in the thin-pool name through the webinterface :(

if i create a new thin pool named "1tb_thin" i can't create a new data pool within that through the webinterface cause it claims "illegal characters" I think this is wrong on your side - but i'm not sure... - for now i'll recreate this LV with another name without the underscore... ;-)

OK that worked - easier than expected... ;-) Is it a problem if i want to create a cluster on an proxmox 4.2-5/7cf09667 and add an full updated proxmox 4.2-11/2c626aa1 as the second node? or do they need to have the same patchlevel? Btw.: how to patch a cluster propperly? just one after the...

THX I will test that: first thing that I stumbled above is the "pvecm" creation section, there is written: pvecm create <clustername> -bindnet0_addr 10.10.10.151 -ring0_addr one-corosync is it a typo that the ipv4 address differs from the created on "10.10.1.151"?

we want to have the ability to maove running VMs between hosts online - but we nodn't really need HA - so is there something to consider regarding the setup that is explained in https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x to achive that or am i going the wrong way? if this setup...

worked well, at first i created a volumegroup that owns the whole raid6: vgcreate pve-raid /dev/md0 than I created a logical volume for the qcow2 based VMs using 50% of the space: lvcreate -l50%VG -n data pve-raid than I created a logical volume that used 50% of the volumegroup for the...

is there a "best pratice" on how to setup both (lv & lvm-thin)?

how would be this done in pve 4.2 ?

i installed a second server next to our old pve 4.1 machine for extended testing of cluster systems. to achive that i installed pve on a ssd and after isntallation and setup I created a raid6 via mdadm out of 5 3tb hdds. i mounted these into /var/lib/vz - to be able to move the .qcow2 storage...

does anyone have the same problem?

the quota option was diasabled - I verified that by creating a new Container and double checked if the quota option is not checked - still the same. But when I delete the network card - than the system boots! Re-Adding produces the same error again. So it defiantly has something todo with the...

thanks for the hint - it seems to be related to the network creation: lxc-start: conf.c: instantiate_veth: 2767 failed to create veth pair (veth126i0 and veth80ITPG): Operation not supported lxc-start: conf.c: lxc_create_network: 3084 failed to create netdev lxc-start: start.c: lxc_spawn...

My Proxmox VE 4.1 Server can not start newly created LXC Containers. What is going wrong here? lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348...

yeah - I thought that too - as a longtime user of ZFS I was pretty amazed by this approach. but so many things doesn't work on zfs (live migration and on the fly backups for example) and zfs needs RAM - a lot of - so we decided to separate Storage and VM - so the vmserver has its ram for the vms...

is this script working on an proxmox 4.1 setup?

Ran into the same problem today - hard to find the real problems if the logs are spammed