Hi all,
I was trying to spin up a matterv single-node nested deployment on my PVE cluster, just so I could poke around and check it out. The install goes fine, but as soon as I get to the step where I configure the VM bridge on the matterv host, the PVE host where it's running loses all network communication.
The matterv bridge doesn't have any IP range assigned to it yet. It's also a different naming scheme than the bridge on the PVE host, though I can't imagine that makes a difference.
Why would this happen? How can I troubleshoot?
I was trying to spin up a matterv single-node nested deployment on my PVE cluster, just so I could poke around and check it out. The install goes fine, but as soon as I get to the step where I configure the VM bridge on the matterv host, the PVE host where it's running loses all network communication.
The matterv bridge doesn't have any IP range assigned to it yet. It's also a different naming scheme than the bridge on the PVE host, though I can't imagine that makes a difference.
Why would this happen? How can I troubleshoot?