Search results

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

It might looks like an "apt install" without "apt update" first ...

sea serach for qm remote-migrate https://pve.proxmox.com/pve-docs/qm.1.html

there is offline cros cluster migration available via cli in case...qm remote-migrate

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

verify the "promiscous" mode of the vswtich and uplink. by default vswitch only allow the vm mac address on each virtual port

Thanks for the TUI !!!!

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

Raah !! this is the "real root cause" of my issues !!! THANKS a lot for your support ! Proxmox (Staff) Rocks ;-)

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 !

Thanks for the explanation ! If I understand correctly, I need to use backup/restore to migrate LXC with mutiple disks ... while remote-migrate is in "preview"...

Ticket syntax solved, Using the same script, several LXC can't be migrated... ths with big additional raw disks ( eg 100G like this one) For other execution, just changing the VMID in the script and it works ! What could it be ? root@san:~# ./migrate-to.sh Establishing API connection with...

Looks like pct unlock does the trick...

Thanks, Token syntax is ok.. Now next question: After successful run without the --delete 1 , I have two copies of my LXC: one "usable" on the destination node, and one in "locked" mode ( in migration with small plane icon). I can't delete the source LXC ( computer says no: CT is locked...

Thanks for your answer ! Token ahs been deleted just after having created the post ;-) ( and the system is not visible on the Internet) Didn't want to mess up with the value as I was "convinced" my issue was a syntax problem. For what it's worth, a "full example" would be useful in the docs ...