Your monitor input select might be set to "auto"
selecting diplayport input on your monitor instead of auto might prevent it to "fall back" to your proxmox
In my case, "master node " hosted the vm disks ( exposed via NFS) so without it, cluster would be down anyway.
But yes, this setup is not very compatible with the spirit of multi master qorum
https://forum.proxmox.com/threads/homelab-3-nodes-cluster-2-diskless-and-one-exposing-storage-via-nfs.68587/#post-307776
more or less the same kind of idea. changing the number of votes worked very well IN MY HOMELAB
My experience is the oposite:
unmanaged switches don't dare to look at vlan tags and act as all ports being "hybrid" ports. ( forward tagged and untagged packets "everywhere" )
This is from memory ( I've no access to ESXI anymore).... and my memory is slow ( saw your post yesterday and trying since then to remember the word "promiscous"..)
Glad you could solve your issue !
EC
what's your ethernet card ? I had problems with old connectx2: they can't have all 4096 vlan actives.
Had to limit the number of vlan to the range I'm using..
bridge-vlan-aware yes
bridge-vids 1900-2020
Hey proxmox team ;-)
Resourse spent on dark theme development when this push functionality is still on the backlog is a strange sense of priorities ;-)
Look very useful !!
I'd like to know if PBS needs "uptime on its own" to do housekeeping prune...
If Yes, where is the schedule defined ?
I'd like to make my PBS server "mostly powered down" except when backups jobs need it ( like this one) but also allow it to do its housekeeping.
Thanks
token has been created for root@pam ( root@pam is the only existing user on both source and destination pve).
I made sure the token is not restricted ( don't have the system at hands)
But I'll try to deactivate "fuse" and keep trying !