Search results

I had custom setting for this container that caused the issue: lxc.aa_profile: lxc-container-default-with-nfs This was set for the container to get NFS mounting support. Obviously this stopped working with the recent PVE upgrades. After removing that custom AppArmor profile, everything...

Seems to work with: proxmox-ve: 4.2-58 (running kernel: 4.4.13-2-pve) pve-manager: 4.2-17 (running version: 4.2-17/e1400248)

Also having similar issue: pveversion: # pveversion -v proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve) pve-manager: 4.2-17 (running version: 4.2-17/e1400248) pve-kernel-4.4.13-1-pve: 4.4.13-56 pve-kernel-4.4.13-2-pve: 4.4.13-58 pve-kernel-4.4.15-1-pve: 4.4.15-60 pve-kernel-4.4.10-1-pve...

Theoretically there could be a VM/client daemon that calls PVE API to request disk resize and then later reacts to handle the internal fs resize too. Tricky, hacky and disaster waiting to happen - but doable. I personally do not feel that this kind of daemon should be offered by PVE itself. ;)

Sorry that this is not a solution to your original question, but I'd still recommend changing your publicly posted knock code. Finding your servers public IPv4 should take only tens of seconds with proper tools to scan only ~240 possible IPv4 addresses.

For full management access you need to forward all of these: Web interface: 8006/tcp VNC Web console: 5900-5999/tcp SPICE console: 3128/tcp VNC port is chosen by PVE within that range. For full compatibility you really need 5900-5999. Also, VNC ports are open only when specifically...

The transmit hash policy you've used for slave selection might not be fully LACP (802.3ad) compliant. This might throw LACP with the Cisco and your NIC out of sync due to hash mismatch. Kernel module docs list only options "0" or "layer2" as fully 802.3ad compliant. I'd go with...

I've seen this happen when Corosync is having issues with L2 switch IGMP snooping. This caused node dropping from the cluster every five minutes with exact same errors you are seeing. Multicast packets weren't simply getting trough. Unfortunately the lower-end HP ProCurve did not offer...

Yes, .ovf file is simply a description of virtual machine, but there is also .ova which is an archive format used for delivering both the disk images and .ovf description. One example of open source project offering an OVA packaged virtual appliance is Graylog. Currently using OVA appliances...

Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances. It would be nice if Proxmox VE would offer a built-in utility for importing OVF packaged virtual machines. Many OSS and commercial appliances are distributed in OVF format. Right now...