PR which contains an in-memory background operation manager that queues full configure operations as a single job:

• https://github.com/vyos/vyos-1x/pull/4953

Thank you. I see my mistake now. When I read under step 3, "Optionally, the user can attach a CDROM with an ISO as a cloud-init data source", it left me with the impression this was *optional*—that skipping this would not cause problems. I didn't realize that it would mean no default username/password would be set.

If you use the official proxmox image, you have to use cloud-init to set login/pass for the proxmox flavors.
Feel free to improve the documentation.
Thanks.

What is the intended way to apply configuration to a newly created proxmox flavor instance? At the page I referenced, it doesn't give any indication how to login or add a configuration under the "deploy from qcow2" section. Under the deploy from rolling release, it does mention the normal default vyos/vyos credentials.

Proxmox images don't use any default passwords.
You use this flavour incorrectly.

As an update, I didn't realize originally but it seems I need to both the new VM once before the password reset option will work. If I go directly to it on first boot I get a message about no config.boot file and this not being a restore tool. Booting normally once seems to create the default config, then the password recovery option works from the serial interface.

This can be solved with the already existing source-address option. When it's set, advertisments are sent from a unicast IPv6 address, if it's assigned. If it's not assigned, they are not sent.

FRR case where there is a long explanation: https://github.com/FRRouting/frr/issues/15400

Example implementation of such a daemon:
https://github.com/vyos/vyos-1x/pull/4872

This is still a problem. We have found no suitable fixes, and I think we've tried "everything" without avail.

No passthrough.
In general, the configuration looks like this:
HP DL 360G10 Servers
Windows Server 2019 with Hyper-V role
Vyos VMs Generation 2.
NIC ports are grouped at the OS level to Team (like bond in Linux).
After installing a new NIC (HPE P26253-B21, Broadcom BCM57416), we simply changed the members of this Network Team, nothing more.
Up to this point, everything had been working properly for several years.

@lbv2rus Do you passthrough NICs to the VM?

Please share the full configuration. bond0 is not listed in the example above.

I did some deeper debuging:

Yes got the information that the other side is no vyos (sorry didn't expect this) it's an current sophos box with strongswan.
It try to replicate it here between two vyos boxes the next days