Vagrantfile configuration state during host-level upgrades

When updating the Vagrant installation on a host machine, the system must reconcile the existing guest states defined in the Vagrantfile with the new version's provider API. While vagrant reload typically applies configuration changes to active guests, the behavior differs when guests are not in a running state.

There is uncertainty regarding how Vagrant manages state synchronization when a host-level upgrade occurs while guests are in a 'paused' or 'saved' state. If the underlying provider API has shifted, the transition from a saved state to a running state may conflict with updated Ruby DSL interpretations in the Vagrantfile.

• Does Vagrant force a state reset for paused guests during a version transition to ensure configuration alignment?
• How is the local state in the .vagrant directory validated against the new version before a guest is resumed from a saved state?