Search results

Hi, the problem seems to be still here. With the bridge enslaved on a dummyX interface, it works.

This behaviour is the same. If you have juste one bridge (e.g vmbr1), you can have just an IPv6 or a dual stack IPv4+IPv6, it doesn't work. In all cases (one bridge, two bridges, xxx bridges, single stack, dual stack, ....) i have to create dummy interfaces and enslave the bridge in order to...

All tests are done on fresh installations of PVE7 on many servers, so yes, it's ifupdown2 Extract of a /etc/network/interfaces: # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the...

Hi proxmox people ! :-) The way bridges work has really changed in Debian11 / Proxmox 7. When creating a bridge without a slave interface, it works with a private IPv4. But if we assign it an IPv6 of ULA type (fdxx: xxxx: xxxx: xxxx ...), it is impossible to ping this bridge on IPv6. The ip...

Hmmm after some tests, the option Other OS seems not working ... I've many Windows 10 1803 guest that comsume a lot of CPU on the PVE hosts ... Arghhhh

Thanks for your replies ! I've tested with the option 'Other OS'. It works with a couple of Win10 1803 virtual machines, but not all. I'll investigate why. But my first conclusions are : Windows sucks ^_^. Windows lies about the real CPU usage.

Hi, I've some Windows 10 1803 guests on my clusters. They're totally idle (according to the windows process manager) but on the host side they consume a lot of CPU, between 6% and 15%. All the windows installations are fresh installations, with tablet disabled, ballon and qemu guest agent...