Search results

PVE does not provides 0 downtime. When High Availability occurs, the VMS are restarted on an other node. If you want IPSEC High Availability, look otherwhere (ex : double IPSEC link + BGP ?).

did you tryed "echo 0 > /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping" ? do you use multi queue on device ? is there a debug mode in the ethernet card module ?

Try disabling snooping. And maybe try virtio network for the VMs ?

https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster https://forum.proxmox.com/threads/best-practise-for-a-two-node-proxmox-storage-cluster.26370/#post-132488 3 nodes is OK. But when you lost one node, you are in the hurry :-)

search other threads : 2 nodes PVE 4 HA cluster is not supported min 3 nodes

Do you use ethernet bonding ? Have you disabled igmp snooping on virtual bridges ?

I read some things about discard : this can lead to performance decreases on disk. It is advised to do the discard job in a crontab. Regarding the bug, I really don't know. Your question is legitimate but I can't help you. Maybe create a new thread, this can be usefull for other members in the...

I have no idea. I saw that on goole "https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359706". Don't you have any oom kills ? Maybe look at ext4 corruption bugs ?

Normaly its makes no sense to run an ntpd inside an VM. Use the correct time at the host and all the VMs have the right time.

I just falled on that : https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files :-)

I didn't put my hands on an HP server since more than 10 years, but the menu you get is not for the motherboard presets ? If so, try Red Hat.

I don't know you storage backend and your infrastructure. But I think this anaware deletion can occur when you have 2 proxmox nodes, not in cluster and using the same mount point for VM disks. If you define 1 VM on the 2 nodes with the same VMID, deleting the VM on one node will delete it on the...

about thin provisionning : http://www.stratoscale.com/blog/storage/advantages-and-disadvantages-of-thin-provisioning/ tool around that : http://manpages.ubuntu.com/manpages/precise/man1/virt-sparsify.1.html I think you are faced to a bug in qcow2. This has already happened. If you do not want...

Hello, The mount point is not the same (10.50.0.2:/home vs 10.50.0.2:/). Please reproduce same initial conditions for the compared tests ? Furthermore, fsync is not the only metric to look at...

Hello, variables used by the installer script are detailed here : https://pve.proxmox.com/wiki/Debugging_Installation They are reported on the installer GUI. I think you should use hdsize. Please try and keep in touch ?

Is there any snapshots in you qcow2 image ? The size increase ca come from this. An other reason could be the data fragmentation when using "thin provisioning" in qcow2 but, it is less likely to be that.

Thanks for the info mweigelt.

mmenaz : thank for your experience sharing. I thinked about a potential upgrade in proxmox HA communication : - either ha layer could discuss with the other nodes on every ethernet interface and on several IPs or at ethernet level (this last is less whicheable in terms of WAN topology) - ie...

Can yo confirm this please : - if you don't need automagical HA, you can have a 2 nodes cluster, but you will have to fight when you will want to migrate VMs from a down node (is it at last possible ?) - if you want automagical HA, you need at last 3 working nodes because of the quorum...

Hello, Hereunder are my tests of HA functions. Before to get it smooth I had some problems, certainly because I didn't let enough time for the HA algorith to react. But this last test is OK. I paste it here as reference for the "restricted" and "no failback" options. Feel free to reveal any...