Mac book M3 issue

[milaomrani]

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Using /Users/Documents/code/kubeflow_init/minikf-user-data.vdi for persistent storage.
==> default: Using /Users/Documents/code/kubeflow_init/minikf-user-data.vdi for persistent storage.
==> default: Checking if box 'arrikto/minikf' version '20210428.0.1' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 32123 (guest) => 32123 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Using /Users/Documents/code/kubeflow_init/minikf-user-data.vdi for persistent storage.
==> default: ** Creating adapter for persistent storage **
==> default: Running 'pre-boot' VM customizations...
==> default: Using /Users/Documents/code/kubeflow_init/minikf-user-data.vdi for persistent storage.
==> default: ** Persistent Storage Volume exists, not creating **
==> default: Using /Users/Documents/code/kubeflow_init/minikf-user-data.vdi for persistent storage.
==> default: ** Attaching persistent storage **
==> 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
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'paused' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.