Just a quick update - and a THANK YOU for the guidance.,
I was able to edit the ProxMox interfaces to remove all IP addressing except for eno1, which is my admin LAN link for the hypervisor. I was then able to update the proxmox to 8.4.14...
Having more than one NIC on the same network isn't a good idea for Windows either, although they do have differences in the way they handle that.
Even listening to 0.0.0:8006 won't really solve the problem because it is a bridge. Unplugging the...
What shouldn't be what way? Don't know what you mean by that. What I stated is how the kernel has always worked and it is why having multiple IP's on the same subnet can result in confusing behavior.
The other thing, of course, is that the PVE...
Both bridges are in the same network, so the kernel will pick one at random for reply packets. Remove the IP from the "slow" one and it should use the "fast" one.
Backup jobs sort of "pre-start" the VM (I forget why), so if the VM has a pass-thru device that is also passed to another VM that is running you will see this problem.
You are setting up a very complex scenario. I don't have time this morning to walk you through all the complexities of what you are trying to do with regard to the dual ISP setup. It is called "multi-homing" and you can look it up. That is not a...
Did you set a DNS when you configured the VM? If it gets an IP via DHCP, make sure the DHCP server is sending the DNS option. The settings on your PVE host are not relevant to the VM.
This is kind of a mess. You should not have gateways specified for all the bridges, and you should not have a gateway that's on a different network than the bridge, and you should not have the same /24 on multiple interfaces unless they really...
Again, I advise to read the manual. You have what's called an LVM-thin setup.
The installer set up the Logical Volume Manager, which is different from traditional partitions. It manages a chunk of disk space by carving it up into virtual block...
That isn't what you want to do.
You see that 1.7 TB "pve-data" thingy? That should show up in the gui as "local-lvm" or similar. That is where your VMs will go. Just set that as the storage when you create a VM. Then read the storage section...
As already explained by @BobhWasatch ProxmoxVE main target audience are NOT homelabs although (thanks to it's open source) nature) you can use it also in homelabs. I'm doing this myself because in my dayjob I have nothing to do with our...
I don't run a cluster but AFAIK the storages don't have to be the same size on all nodes for migration to work. You just need to have sufficient space on the target.
Why did you bring it up then?
As far as I know the GUI only supports creating an LVM-thin on a whole disk. It isn't exactly an enterprise use-case to have other things on the same disk as your VM's, while it is one to have entire disks dedicated...
In that case you might be better served by a desktop virtualization solution: virt-manager, vmware, virtualbox. PVE is pitched as an enterprise solution and that comes with certain expectations of the users. Those other solutions claim to be easy...