Hi,
In PVE4.0b2 if I have a VM managed by HA, and then I disable HA on that VM, the VM is then powered off. I do not recall seeing this behavior in PVE4.0b1. Can it be reverted back to the original behavior please of not powering off when disabling HA on the VM?
Regards,
m
I initially had several issues when adding 4.0 cluster members. I found the following to help in my situation.
- Make sure name resolution works on all hosts for all hosts
- Make sure time is synchronized on all hosts
- Disable IGMP snooping on your switch(es) if enabled
Due to the multicast...
Hi,
Spice over IPv6 on PVE 4.0 beta 1 does not appear to work. It isn't listening on my hosts:
~# netstat -ntlp | grep spiceproxy
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN 7140/spiceproxy
And when I try to connect to it I get:
Could not connect to proxy...
I actually have two NFS hosts set up like this, both have fully redundant internal everything. One host is used as a datastore, and the other to store vzdump backups on. The data stored in the cluster is not mission critical, so some type of HA setup between the two NFS hosts is not currently...
Seeing as how neither NFS session trunking or pNFS is supported in Proxmox, I was faced with an interesting question as to how to provide multiple parallel links to my NFS storage for both load distribution and path redundancy.
From experience, switch level port aggregation with or without LACP...
On Proxmox 4.0 beta, a VM with iothread enabled on a virtio disk causes the VM to crash during a vzdump snapshot backup. I can reproduce it every single time on 5 different hosts backing up to either NFS or a local disk, whether it is a scheduled backup or an immediate backup.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.