Search results

On that cluster, the hosts are communicating through the software bridges. Yes, bridges have their own L2 settings. This is the default IGMP snoop setting for bridges in Proxmox: root@X# cat /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping 1 root@X#

I'll chime in to say that one of our Proxmox sites is a 3-node DL360G6 that we recently (3 days ago) updated to v3.3. These servers were upgraded from v3.1. There were no issues with the upgrade or after rebooting; the cluster reconnected correctly and has been stable since upgrading. We're...

Yes, that makes sense. However, I can spin up a VM that has zero load (IO or otherwise), and it still only averages around 300Mbit/s for a live storage migration. Offline storage migration is consistently at least double that (if not more - 750Mbit/s is the average I'm seeing at present).

What is the limiting factor(s) when performing storage migration on a running VM? When performing storage migration (NFS => NFS backends), we see a 750Mbit/s average transfer speed when doing storage migration on a VM that is switched off. On a running VM we see 300Mbit/s average on the same...

I learnt this after applying a network change I made in the GUI that I didn't want to restart the host for. I confirmed that after a full network restart (/etc/init.d/networking restart) as you did, the entire networking system comes back up fine. It requires a power cycle of the guest(s) to...

Will do. I notice the PVE kernel has been updated from 2.6.32-16 to 2.6.32-17. As the problem is coming from a user-space program though, I'm guessing the kernel upgrade is not the bug fix - is this correct? Essentially, I don't want to have to reboot the production server unless absolutely...

We have been running Proxmox 2.2.24 in production for a week now. Last night half of our scheduled backups job failed with the same error: 105: Jan 03 01:22:52 INFO: Unable to create new inotify object: Too many open files at /usr/share/perl5/PVE/INotify.pm line 386. 105: Jan 03 01:22:52...