Search results

You can power off a VM on local storage and migrate it to another local storage host without issue. Why can't an online migration with local storage be done when an offline one can?

Sorry to resurrect an old thread. There is a script for this functionality at https://github.com/kvaps/pve-autosnap. It works pretty well. Schedule it as a cron job.

In Proxmox 4.2, if I attempt to add a firewall security group to a VM it does not allow me to select the security group. The group is there and can be chosen, but it is not allowed to populate the field. To reproduce, go to [Datacenter] -> [Firewall] -> [Security Group] and create a new one...

I had a similar issue. Turning off IGMP snooping on my switches solved the issue for me.

I would like to know this as well. It would be nice to be able to have the Nexus 1000v in Proxmox.

Rolling back to kernel 4.1.3 returned normal functionality for me.

Rolling back to kernel 4.1.3 returned normal functionality for me.

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

Same here on a Dell PowerEdge R620.

I experienced the same thing after the upgrade. Disable ACPI on the VM and it will boot.

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...

Certainly. It has been filed as bug 683.

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...

+1 for Observium. It is by far the easiest open source NMS to use.

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.