Recent content by BobhWasatch

Glad to hear you got it sorted. Please mark the thread solved by editing your first post.

One thing I don't get about homelabbers is using a bunch of vlans and then making sure there is complete connectivity between them.

You can have multiple vlans on a single VM. They can all use DHCP.

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 cable doesn't make the bridge go away, and usually...

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 gui may bind to specific interfaces on startup...

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 trivial thing to get working and depending on what...

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 are connected to the same network (and even that is...

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 devices "on demand". When you make a VM a virtual...

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 of the manual.

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 to VM storage. That being said, it can be done...

So do that and use Hyper-V as the hypervisor.