VirtualBox＋Vagrantでvagrant upエラー(Ubuntu)

WindowsのPowerShellから「vagrant up」を実行したが、エラーが起きてアクセスできない。

> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/xenial64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: ubuntu64_16_default_1714387551066_18501
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

調べたところ同様のエラーにぶつかった方が既に多数おり情報についてはすぐに得られた。どうやらUbuntuの場合に起きる（？）事象らしい。
Hyper-Vを無効にすることで起動するらしいが、DockerではHyper-Vを有効にする必要があるらしく、どちらも使う場合はOn/Offを切り替える必要がありそうなため断念した

（Dockerは使うので切り替えは面倒だ・・・）

参考

https://qiita.com/yukomaki/items/28f9c70cf090114676cb

Hyper-V をオン/オフする方法 - Qiita

以下いろいろな方の検証方法を試したがダメでした
管理者でためす→変わらず
再度vagrant up→変わらず
VirtualBoxの設定で警告の出ているグラフィックスコントローラーをVMSVGAに変えてみる→変わらず