Search results

I have been playing with cloud-init support in PVE and am loving it ... however, one of the things I want to disable on certain VMS (for good or for bad, please don't lecture on security) is to enable the root user to be able to ssh into the VMs (at least while we're building them and scp'ing...

Is there a recommended way to change the subnet which CoroSync/Proxmox uses for it's "primary" interface, without breaking the cluster or experiencing excessive downtime? For technical/design reasons, I need (want) to move the corosync traffic to a a different vlan and renumber the admin...

Having upgraded to 5.1-46 (from 5.1-41) all of my VMs are no longer on the network We are using OpenvSwitch for the networking stack, which may be related? Is there a way to downgrade or any recommendations on how to fix this?

We've just run an apt-get dist-upgrade on a node and the result was a little surprising ... and I'm now trying to work out what to do next root@pve-7:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The...