Search results

Is the output, after you've run ifdown and ifup? If so, it clearly didn't work...

I didn't test it myself. I would do it tonight after work and report back. File descriptor 2 is the standard error (stderr). In case of en error, you might want to pipe it to the nirvana (/dev/null) for scripts or dependent programs, who try to interpret the output of the interfaces scripts...

I'd set post-up only on the "real" interfaces and not on the virtual ones. One thing to add would be the path to the "ethtool" and make sure that it is installed. For example: ... iface eno1 inet manual post-up /usr/sbin/ethtool -K $IFACE tso off gso off 2> /dev/null ...

I had this issue today as well. It happened after I started a VM with PCIE passthrough. My ethernet card is Intel I219-LM. The kernel driver in use is e1000e. This one had hang issues. My other ethernet card, which I use for PCIE passthrough, is Intel I210. The kernel driver in use is igb. Is...

Here is the output, you asked: proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3...

It is of course working, unless it is not anymore. It occurs not frequently and only workaround is to reload the page. Is there anything I can look for, when the problem occurs?

What is the most up to date package? That's the version.

Can you report any negative behaviour? It seems you are testing the new version for 4 weeks now.

Yeah, I have the same issue.

There is a new version of the package 3.2-4. Is this problem fixed with it?

There is some cleanup work to be done. See my edits...

Additionally the vzdump zfs snapshots are generated, that can't be deleted. They show only on Web UI, not via zfs list -t snapshot. The Containers are being left in locked state, which can be unlocked again with pct unlock <ID>. Edit: Edit2: The Containers can be backed up, if they are shut...

I’ve updated my system today as well. I’m getting the same error from vzdump from containers with storage pass through: unable to parse volume ID

You have to install VirtualBox guest on your Proxmox VM and set your adapter type to virtio-net with promiscuous mode set to allow all. Your containers will now work as expected. Edit: Your host shouldn't be connected via Wi-Fi, as your router may be blocking other MAC addresses.