Search results

Hello, I'm using pigz for backup (pigz=1 in vzdump.conf). It really helps because of smaller archive size, and in my case the bottleneck is slow backup storage. Therefore, smaller backups writes faster and take less space. But recently I discovered that restore uses gzip, not pigz (you can see...

It will move all vm's only from local host where you run the command.

qm list | awk '{print $1}' | while read VMID; do qm migrate $VMID <DST_HOST> -online --with-local-disks; done Instead of <DST_HOST> insert your destination host (without brackets).

Problem solved by "rootdelay=5" in /etc/default/grub.

Last week we have been struggling to upgrade our Proxmox node from 4.4 to 5.1, and everything going fine except for multipath. In our case we have boot device on multipath, and after upgrade multipath won't do its work, /dev/mapper/pve-root not created by multipath. Instead, lvm tries to mount...

Done https://bugzilla.proxmox.com/show_bug.cgi?id=901

Hello. Non-ASCII characters in comments in firewall rules cause problems. If there is one comment with non-ASCII characters, all rules disappear, including rules with strictly ASCII comments (although they stay in configuration, just don't display). It happens even if comment's language is the...

The cause of the problem is TCP sequence randomization http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_connlimits.html I've disabled it on Cisco ASA inside interface and now TCP sessions works with Proxmox firewall switched on.

I don't know if anyone concerns about this problem anymore, but there was development. It seems that in our case the cause of the problem is our central router/firewall Cisco ASA 5520 with rather old software 8.2(2)-k8. If we replace ASA with Mikrotik, everything works fine when global firewall...

Same problem in 4.1-13 (clean install 4.1, then upgrade to current version).

Still remains in PVE 3.4-9.

I think it can be related to this issue http://forum.proxmox.com/threads/21372-firewall-enabled-in-datacenter-prevent-bridge-VM-comunication-on-the-same-node

Source port is always random, so when you set source port=8006, your rule doesn't work.

Afox, try to leave source port blank, destination port = 8006.

Still remains in PVE 3.4-6.

I have the same problem. I also noticed that problem doesn't appear if networks belongs to the same /8 network. For example, in my case 2 VMs belonging to networks 10.1.0.0/24 and 10.55.1.0/24 (different vmbrs) communicate with each other perfectly fine when global firewall is enabled. On the...