[PVE-User] can't make zfs-zsync working

2015-09-24 Thread Jean-Laurent Ivars
Dear co-users, I just installed a two proxmox cluster with last iso 3.4 and have subscription so i made all the updates. The pve-zsync fonction is really great and I really really would like to succeed make it work. If someone already managed to make it work would you like please tell me how,

[PVE-User] VDI on Proxmox anyone?

2015-09-24 Thread Kyle Bruene
I have a Windows Terminal Services w/ Citrix running under Proxmox. Works fantastic. Nothing special you really need to do. -Original Message- From: pve-user [mailto:pve-user-boun...@pve.proxmox.com] On Behalf Of pve-user-requ...@pve.proxmox.com Sent: Thursday, September 24, 2015 5:00

[PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Gilberto Nunes
Hi guys I have a three nodes cluster with PVE 4 and HA enable. Just one VM with 8GB memory and 1,5 TB of hard disk. If the VM has 2 GB of memory and 32 GB of hard disk, HA works fine. But now, with more memory and hard disk, the HA freeze the VM: ha-manager status quorum OK master proxmox02

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Gilberto Nunes
UPDATE I get this on syslog Sep 24 11:59:30 proxmox02 pve-ha-crm[1360]: service 'vm:120': state changed from 'started' to 'freeze' Sep 24 11:59:40 proxmox02 corosync[1304]: [TOTEM ] A new membership ( 10.1.1.20:224) was formed. Members left: 1 Sep 24 11:59:40 proxmox02 pmxcfs[1055]: [dcdb]

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Thomas Lamprecht
Oh, and after you added the votes, delete the PVE VM and delete it with the pvecm delnode oldvmnode-hostname from the cluster On 09/24/2015 05:08 PM, Thomas Lamprecht wrote: Adapt the corosync.conf file in the /etc/pve folder there, set quorum_votes of one of the node entries from 1 to 2.

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Thomas Lamprecht
Adapt the corosync.conf file in the /etc/pve folder there, set quorum_votes of one of the node entries from 1 to 2. This achieves the same as your current setup but with much less overhead as no VM, which acts as PVE node, is needed. *NOTE*: for real HA three real nodes are needed. If you

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Dietmar Maurer
> I get this on syslog > > Sep 24 11:59:30 proxmox02 pve-ha-crm[1360]: service 'vm:120': state changed > from 'started' to 'freeze' > Sep 24 11:59:40 proxmox02 corosync[1304]: [TOTEM ] A new membership ( > 10.1.1.20:224) was formed. Members left: 1 > Sep 24 11:59:40 proxmox02 pmxcfs[1055]:

[PVE-User] Ceph repository key change

2015-09-24 Thread Fabrizio Cuseo
Hello. Due to the change of ceph repository key, I need to change manually the key. Install curl if not installed: apt-get install curl apt-key del 17ED316D curl https://git.ceph.com/release.asc | apt-key add - apt-get update And now is working fine. How can avoid to do this on each proxmox

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Gilberto Nunes
It's work with 3 nodes, when I run pvecm expected 3!! 2015-09-24 12:08 GMT-03:00 Thomas Lamprecht : > Adapt the corosync.conf file in the /etc/pve folder there, set > quorum_votes of one of the node entries from 1 to 2. > > This achieves the same as your current setup

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Gilberto Nunes
Of course! That what I expect since HA has 3 nodes. If NODE 1 go crash, NODE 2 was suppose to act... 2015-09-24 12:51 GMT-03:00 Dietmar Maurer : > > I get this on syslog > > > > Sep 24 11:59:30 proxmox02 pve-ha-crm[1360]: service 'vm:120': state > changed > > from 'started'

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Dietmar Maurer
> Of course! That what I expect since HA has 3 nodes. If NODE 1 go crash, state 'freeze' means that node 1 was shutdown normally. So HA waits until that the node starts again. ___ pve-user mailing list pve-user@pve.proxmox.com

Re: [PVE-User] PVE 4 - VM Freeze

2015-09-24 Thread Gilberto Nunes
Nice shot Thomas! I need changes in quorum as well, adding two_node: 1 Now is work fine with two nodes.. Thanks a lot! 2015-09-24 12:09 GMT-03:00 Thomas Lamprecht : > Oh, and after you added the votes, delete the PVE VM and delete it with the > pvecm delnode