lv.qemu_command is ignored

I'm trying to run an AMD64 image on an M1 mac. The image was built in this same machine with Packer. I set lv.qemu_command = "qemu-system-x86_64" but it still runs qemu-system-aarch64.
Machine: MacBook Air M1
OS: macOS Ventura, Version 13.0 Beta (22A5311f)
❯ vagrant --version
Vagrant 2.2.19
❯ vagrant plugin list
vagrant-qemu (0.1.8, global)

Vagrantfile:
Vagrant.configure("2") do |config|
  config.vm.box = "c10l/debian-11.4"
  config.vm.box_version = "202208.02.0"

  config.vm.synced_folder ".", "/vagrant", disabled: true

  config.vm.provider :libvirt do |lv|
    lv.qemu_command = "qemu-system-x86_64"
  end
end

When I run it:
❯ vagrant up
Bringing machine 'default' up with 'qemu' provider...
==> default: Checking if box 'c10l/debian-11.4' version '202208.02.0' is up to date...
==> default: Importing a QEMU instance
    default: Creating and registering the VM...
    default: Successfully imported VM
==> default: Warning! The QEMU provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.
==> default: Starting the instance...
A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/cassianoleal/src/proxmox/client-go/.vagrant/machines/default/qemu/vgXb4TTamTE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/cassianoleal/src/proxmox/client-go/.vagrant/machines/default/qemu/vgXb4TTamTE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/cassianoleal/src/proxmox/client-go/.vagrant/machines/default/qemu/vgXb4TTamTE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/cassianoleal/.vagrant.d/tmp/vagrant-qemu/vgXb4TTamTE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/cassianoleal/.vagrant.d/tmp/vagrant-qemu/vgXb4TTamTE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/cassianoleal/src/proxmox/client-go/.vagrant/machines/default/qemu/vgXb4TTamTE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:

1 ❯

Debug Logs
❯ VAGRANT_LOG=debug vagrant up
INFO global: Vagrant version: 2.2.19
INFO global: Ruby version: 2.7.4
INFO global: RubyGems version: 3.1.6
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_INSTALLER_VERSION="2"
WARN global: resolv replacement has not been enabled!
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/podman/plugin.rb
INFO manager: Registered plugin: podman
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/container/plugin.rb
INFO manager: Registered plugin: container
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/snapshot/plugin.rb
INFO manager: Registered plugin: snapshot command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/validate/plugin.rb
INFO manager: Registered plugin: validate command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/autocomplete/plugin.rb
INFO manager: Registered plugin: autocomplete command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/winrm/plugin.rb
INFO manager: Registered plugin: winrm command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/provider/plugin.rb
INFO manager: Registered plugin: provider command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/winrm_config/plugin.rb
INFO manager: Registered plugin: winrm-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/powershell/plugin.rb
INFO manager: Registered plugin: powershell command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/cap/plugin.rb
INFO manager: Registered plugin: cap command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/cloud/plugin.rb
INFO manager: Registered plugin: vagrant-cloud
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/port/plugin.rb
INFO manager: Registered plugin: port command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/commands/upload/plugin.rb
INFO manager: Registered plugin: upload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/void/plugin.rb
INFO manager: Registered plugin: Void host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/hosts/alt/plugin.rb
INFO manager: Registered plugin: ALT Platform host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/communicators/winssh/plugin.rb
INFO manager: Registered plugin: windows ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/alpine/plugin.rb
INFO manager: Registered plugin: Alpine guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/dragonflybsd/plugin.rb
INFO manager: Registered plugin: DragonFly BSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/amazon/plugin.rb
INFO manager: Registered plugin: Amazon Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/rocky/plugin.rb
INFO manager: Registered plugin: Rocky guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/slackware/plugin.rb
INFO manager: Registered plugin: Slackware guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/centos/plugin.rb
INFO manager: Registered plugin: CentOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/bsd/plugin.rb
INFO manager: Registered plugin: BSD-based guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/haiku/plugin.rb
INFO manager: Registered plugin: Haiku guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/trisquel/plugin.rb
INFO manager: Registered plugin: Trisquel guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/kali/plugin.rb
INFO manager: Registered plugin: Kali guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/openwrt/plugin.rb
INFO manager: Registered plugin: OpenWrt guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/elementary/plugin.rb
INFO manager: Registered plugin: Elementary guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/guests/alt/plugin.rb
INFO manager: Registered plugin: ALT Platform guest
INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#<Vagrant::Environment:0x00007f9c9c226948>)
INFO environment:   - cwd: /Users/c10l/src/proxmox/client-go
INFO environment: Home path: /Users/c10l/.vagrant.d
DEBUG environment: Effective local data path: /Users/c10l/src/proxmox/client-go/.vagrant
INFO environment: Local data path: /Users/c10l/src/proxmox/client-go/.vagrant
DEBUG environment: Creating: /Users/c10l/src/proxmox/client-go/.vagrant
DEBUG manager: Enabling localized plugins
INFO manager: Plugins:
DEBUG solution_file: new solution file instance plugin_file=/Users/c10l/src/proxmox/client-go/.vagrant/plugins.json solution_file=/Users/c10l/src/proxmox/client-go/.vagrant/bundler/local.sol
DEBUG solution_file: missing file so skipping loading
DEBUG bundler: solution file in use for init: <Vagrant::Bundler::SolutionFile:/Users/c10l/src/proxmox/client-go/.vagrant/plugins.json:/Users/c10l/src/proxmox/client-go/.vagrant/bundler/local.sol:invalid>
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: generating solution set for configured plugins
DEBUG bundler: Current generated plugin dependency list: []
DEBUG bundler: resolving solution from available specification set
DEBUG bundler: solution set for configured plugins has been resolved
DEBUG bundler: activating solution set
DEBUG bundler: Activating solution set: []
DEBUG solution_file: plugin file does not exist, not storing solution
DEBUG bundler: solution set stored to - <Vagrant::Bundler::SolutionFile:/Users/c10l/src/proxmox/client-go/.vagrant/plugins.json:/Users/c10l/src/proxmox/client-go/.vagrant/bundler/local.sol:invalid>
INFO manager: Loading plugins...
DEBUG manager: Enabling globalized plugins
INFO manager: Plugins:
INFO manager:   - vagrant-qemu = [installed: 0.1.8 constraint: > 0]
DEBUG solution_file: new solution file instance plugin_file=/Users/c10l/.vagrant.d/plugins.json solution_file=/Users/c10l/src/proxmox/client-go/.vagrant/bundler/global.sol
DEBUG solution_file: reading solution file - /Users/c10l/src/proxmox/client-go/.vagrant/bundler/global.sol
DEBUG solution_file: solution validation check CHECKSUM 0f2bef630f0e2279f36eab1fadbaae3d92425e40abd70f79f9487fcd9aa0c103 <-> 0f2bef630f0e2279f36eab1fadbaae3d92425e40abd70f79f9487fcd9aa0c103 VERSION 2.2.19 <-> 2.2.19
DEBUG solution_file: loading solution dependency list
DEBUG solution_file: solution dependency list: [#<Gem::Resolver::DependencyRequest:0x00007f9c9c168268 @dependency=<Gem::Dependency type=:runtime name="vagrant-qemu" requirements="= 0.1.8">, @requester=nil>]
DEBUG bundler: solution file in use for init: <Vagrant::Bundler::SolutionFile:/Users/c10l/.vagrant.d/plugins.json:/Users/c10l/src/proxmox/client-go/.vagrant/bundler/global.sol:valid>
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: loading cached solution set
DEBUG bundler: activating solution set
DEBUG bundler: Activating solution set: ["vagrant-qemu-0.1.8"]
DEBUG bundler: Activating gem vagrant-qemu-0.1.8
INFO manager: Loading plugins...
INFO manager: Loading plugin `vagrant-qemu` with default require: `vagrant-qemu`
INFO manager: Registered plugin: QEMU
DEBUG manager: Successfully loaded plugin `vagrant-qemu`.
INFO loader: Set :root = ["#<Pathname:/Users/c10l/src/proxmox/client-go/Vagrantfile>"]
DEBUG loader: Populating proc cache for #<Pathname:/Users/c10l/src/proxmox/client-go/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/c10l/src/proxmox/client-go/Vagrantfile
INFO loader: Loading configuration in order: [:home, :root]
DEBUG loader: Loading from: root (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[5, :qemu]]
DEBUG environment: Priority sorted usable provider list: [:qemu]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider `qemu` as it is the highest priority in the usable list.
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[5, :qemu]]
DEBUG environment: Priority sorted usable provider list: [:qemu]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider `qemu` as it is the highest priority in the usable list.
INFO loader: Set "2780_machine_default" = []
INFO loader: Loading configuration in order: [:home, :root, "2780_machine_default"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
WARN vagrantfile: Failed to locate c10l/debian-11.4 with version 202208.02.0
WARN vagrantfile: Performing lookup with initial values c10l/debian-11.4 with version 202208.02.0
INFO environment: Running hook: environment_plugins_loaded
INFO runner: Running action: environment_plugins_loaded #<Vagrant::Action::Builder:0x00007f9c6d813290>
INFO environment: Running hook: environment_load
INFO runner: Running action: environment_load #<Vagrant::Action::Builder:0x00007f9c9c294420>
DEBUG checkpoint_client: starting plugin check
INFO cli: CLI: [] "up" []
DEBUG checkpoint_client: plugin check complete
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG checkpoint_client: no information received from checkpoint
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: ["default"]
DEBUG command:  -- options: {:provider=>nil}
DEBUG command: Finding machine that match name: default
INFO loader: Set "2780_machine_default" = []
INFO loader: Loading configuration in order: [:home, :root, "2780_machine_default"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
WARN vagrantfile: Failed to locate c10l/debian-11.4 with version 202208.02.0
WARN vagrantfile: Performing lookup with initial values c10l/debian-11.4 with version 202208.02.0
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[5, :qemu]]
DEBUG environment: Priority sorted usable provider list: [:qemu]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider `qemu` as it is the highest priority in the usable list.
INFO environment: Getting machine: default (qemu)
INFO environment: Uncached load of machine.
INFO loader: Set "2780_machine_default" = []
INFO loader: Loading configuration in order: [:home, :root, "2780_machine_default"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box found: c10l/debian-11.4 (libvirt)
INFO environment: Running hook: authenticate_box_url
INFO host: Autodetecting host type for [#<Vagrant::Environment: /Users/c10l/src/proxmox/client-go>]
DEBUG host: Trying: slackware
DEBUG host: Trying: freebsd
DEBUG host: Trying: void
DEBUG host: Trying: arch
DEBUG host: Trying: darwin
INFO host: Detected: darwin!
INFO runner: Running action: authenticate_box_url #<Vagrant::Action::Builder:0x00007f9c8c998a88>
INFO warden: Calling IN action: #<VagrantPlugins::CloudCommand::AddAuthentication:0x00007f9c9c255540>
WARN authenticate-box-url: Authentication token not found as GET parameter.
INFO warden: Calling OUT action: #<VagrantPlugins::CloudCommand::AddAuthentication:0x00007f9c9c255540>
INFO loader: Set :"3440_c10l/debian-11.4_libvirt" = ["#<Pathname:/Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/Vagrantfile>"]
DEBUG loader: Populating proc cache for #<Pathname:/Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/Vagrantfile
INFO loader: Loading configuration in order: [:"3440_c10l/debian-11.4_libvirt", :home, :root, "2780_machine_default"]
DEBUG loader: Loading from: 3440_c10l/debian-11.4_libvirt (evaluating)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO machine: Initializing machine: default
INFO machine:   - Provider: VagrantPlugins::QEMU::Provider
INFO machine:   - Box: #<Vagrant::Box:0x00007f9c9f31b0d0>
INFO machine:   - Data dir: /Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu
INFO machine: New machine ID: nil
INFO interface: Machine: metadata ["provider", :qemu, {:target=>:default}]
INFO command: With machine: default (#<VagrantPlugins::QEMU::Provider:0x00007f9c9c277438 @machine=#<Vagrant::Machine: default (VagrantPlugins::QEMU::Provider)>, @driver=#<VagrantPlugins::QEMU::Driver:0x00007f9c9c236eb0 @vm_id=nil, @data_dir=#<Pathname:/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu>, @tmp_dir=#<Pathname:/Users/c10l/.vagrant.d/tmp/vagrant-qemu>>, @cap_logger=#<Log4r::Logger:0x00007f9c9c276420 @fullname="vagrant::capability_host::vagrantplugins::qemu::provider", @outputters=[], @additive=true, @name="provider", @path="vagrant::capability_host::vagrantplugins::qemu", @parent=#<VagrantLogger:0x00007f9c9f292988 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x00007f9c9f2a3da0 @name="stderr", @level=0, @formatter=#<Vagrant::Util::LoggingFormatter:0x00007f9c9f2aa9e8 @formatter=#<Log4r::BasicFormatter:0x00007f9c9f2ab668 @depth=7>>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x00007f9c9f292820 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @cap_host_chain=[[:qemu, #<#<Class:0x00007f9c9c276948>:0x00007f9c9c23f790>]], @cap_args=[#<Vagrant::Machine: default (VagrantPlugins::QEMU::Provider)>], @cap_caps={:docker=>#<Vagrant::Registry:0x00007f9c9c276768 @items={:public_address=>#<Proc:0x00007f9c9f261d60 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:60>, :proxy_machine=>#<Proc:0x00007f9c9f261c70 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:65>, :has_communicator=>#<Proc:0x00007f9c9f261b80 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:70>}, @results_cache={}>, :hyperv=>#<Vagrant::Registry:0x00007f9c9c276678 @items={:public_address=>#<Proc:0x00007f9c7c8735a0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:25>, :snapshot_list=>#<Proc:0x00007f9c7c873528 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:30>, :configure_disks=>#<Proc:0x00007f9c7c873500 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:35>, :cleanup_disks=>#<Proc:0x00007f9c7c8734d8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:40>, :validate_disk_ext=>#<Proc:0x00007f9c7c8734b0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:45>, :default_disk_exts=>#<Proc:0x00007f9c7c873488 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:50>, :set_default_disk_ext=>#<Proc:0x00007f9c7c873460 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:55>}, @results_cache={}>, :virtualbox=>#<Vagrant::Registry:0x00007f9c9c2765d8 @items={:forwarded_ports=>#<Proc:0x00007f9c9f249f08 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:27>, :nic_mac_addresses=>#<Proc:0x00007f9c9f249ee0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:32>, :public_address=>#<Proc:0x00007f9c9f249eb8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:37>, :configure_disks=>#<Proc:0x00007f9c9f249e90 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:42>, :cleanup_disks=>#<Proc:0x00007f9c9f249e68 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:47>, :validate_disk_ext=>#<Proc:0x00007f9c9f249e40 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:52>, :default_disk_exts=>#<Proc:0x00007f9c9f249e18 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:57>, :set_default_disk_ext=>#<Proc:0x00007f9c9f249df0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:62>, :snapshot_list=>#<Proc:0x00007f9c9f249dc8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:67>}, @results_cache={}>}>)
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: ["default"]
DEBUG command:  -- options: {:provider=>nil}
DEBUG command: Finding machine that match name: default
INFO loader: Set "2780_machine_default" = []
INFO loader: Loading configuration in order: [:home, :root, "2780_machine_default"]
ERROR loader: Unknown config sources: [:"3440_c10l/debian-11.4_libvirt"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
WARN vagrantfile: Failed to locate c10l/debian-11.4 with version 202208.02.0
WARN vagrantfile: Performing lookup with initial values c10l/debian-11.4 with version 202208.02.0
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[5, :qemu]]
DEBUG environment: Priority sorted usable provider list: [:qemu]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider `qemu` as it is the highest priority in the usable list.
INFO environment: Getting machine: default (qemu)
INFO environment: Returning cached machine: default (qemu)
INFO command: With machine: default (#<VagrantPlugins::QEMU::Provider:0x00007f9c9c277438 @machine=#<Vagrant::Machine: default (VagrantPlugins::QEMU::Provider)>, @driver=#<VagrantPlugins::QEMU::Driver:0x00007f9c9c236eb0 @vm_id=nil, @data_dir=#<Pathname:/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu>, @tmp_dir=#<Pathname:/Users/c10l/.vagrant.d/tmp/vagrant-qemu>>, @cap_logger=#<Log4r::Logger:0x00007f9c9c276420 @fullname="vagrant::capability_host::vagrantplugins::qemu::provider", @outputters=[], @additive=true, @name="provider", @path="vagrant::capability_host::vagrantplugins::qemu", @parent=#<VagrantLogger:0x00007f9c9f292988 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x00007f9c9f2a3da0 @name="stderr", @level=0, @formatter=#<Vagrant::Util::LoggingFormatter:0x00007f9c9f2aa9e8 @formatter=#<Log4r::BasicFormatter:0x00007f9c9f2ab668 @depth=7>>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x00007f9c9f292820 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @cap_host_chain=[[:qemu, #<#<Class:0x00007f9c9c276948>:0x00007f9c9c23f790>]], @cap_args=[#<Vagrant::Machine: default (VagrantPlugins::QEMU::Provider)>], @cap_caps={:docker=>#<Vagrant::Registry:0x00007f9c9c276768 @items={:public_address=>#<Proc:0x00007f9c9f261d60 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:60>, :proxy_machine=>#<Proc:0x00007f9c9f261c70 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:65>, :has_communicator=>#<Proc:0x00007f9c9f261b80 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/docker/plugin.rb:70>}, @results_cache={}>, :hyperv=>#<Vagrant::Registry:0x00007f9c9c276678 @items={:public_address=>#<Proc:0x00007f9c7c8735a0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:25>, :snapshot_list=>#<Proc:0x00007f9c7c873528 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:30>, :configure_disks=>#<Proc:0x00007f9c7c873500 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:35>, :cleanup_disks=>#<Proc:0x00007f9c7c8734d8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:40>, :validate_disk_ext=>#<Proc:0x00007f9c7c8734b0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:45>, :default_disk_exts=>#<Proc:0x00007f9c7c873488 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:50>, :set_default_disk_ext=>#<Proc:0x00007f9c7c873460 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/hyperv/plugin.rb:55>}, @results_cache={}>, :virtualbox=>#<Vagrant::Registry:0x00007f9c9c2765d8 @items={:forwarded_ports=>#<Proc:0x00007f9c9f249f08 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:27>, :nic_mac_addresses=>#<Proc:0x00007f9c9f249ee0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:32>, :public_address=>#<Proc:0x00007f9c9f249eb8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:37>, :configure_disks=>#<Proc:0x00007f9c9f249e90 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:42>, :cleanup_disks=>#<Proc:0x00007f9c9f249e68 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:47>, :validate_disk_ext=>#<Proc:0x00007f9c9f249e40 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:52>, :default_disk_exts=>#<Proc:0x00007f9c9f249e18 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:57>, :set_default_disk_ext=>#<Proc:0x00007f9c9f249df0 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:62>, :snapshot_list=>#<Proc:0x00007f9c9f249dc8 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/providers/virtualbox/plugin.rb:67>}, @results_cache={}>}>)
INFO interface: info: Bringing machine 'default' up with 'qemu' provider...
Bringing machine 'default' up with 'qemu' provider...
INFO batch_action: Enabling parallelization by default.
INFO batch_action: Disabling parallelization because only executing one action
INFO batch_action: Batch action will parallelize: false
INFO batch_action: Starting action: #<Vagrant::Machine:0x00007f9c8c9440a0> up {:destroy_on_error=>true, :install_provider=>false, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
INFO machine: Calling action: up on provider QEMU (new)
DEBUG environment: Attempting to acquire process-lock: machine-action-6fdf74554a6cf795a3f1ed8a421b6379
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: machine-action-6fdf74554a6cf795a3f1ed8a421b6379
INFO interface: Machine: action ["up", "start", {:target=>:default}]
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00007f9c9c2e5f50>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::HandleBox:0x00007f9c8ca90080>
INFO handle_box: Machine already has box. HandleBox will not run.
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00007f9c9c3698a0>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BoxCheckOutdated:0x00007f9c9c369878>
INFO interface: output: Checking if box 'c10l/debian-11.4' version '202208.02.0' is up to date...
INFO interface: output: ==> default: Checking if box 'c10l/debian-11.4' version '202208.02.0' is up to date...
==> default: Checking if box 'c10l/debian-11.4' version '202208.02.0' is up to date...
INFO box: box update check is under the interval threshold
INFO box: Skipping box update check
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00007f9c9c3793b8>
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00007f9c9c27c500>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::IsState:0x00007f9c9c235f10>
DEBUG is_state: Checking if machine state is 'not_created'
DEBUG is_state: -- Machine state: not_created
INFO warden: Calling IN action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x00007f9c8cb02590>
DEBUG storeboxmetadata: Writing box metadata file to /Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/box_meta
INFO warden: Calling OUT action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x00007f9c8cb02590>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::IsState:0x00007f9c9c235f10>
INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x00007f9c9f2b1e78>
INFO warden: Calling IN action: #<Proc:0x00007f9c8caeaa08 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:126 (lambda)>
INFO warden: Calling IN action: #<VagrantPlugins::QEMU::Action::Import:0x00007f9c9f2b1d88>
INFO import: Found box image path: /Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/box.img
INFO import: Found qemu dir: /opt/homebrew/share/qemu
INFO interface: output: Importing a QEMU instance
INFO interface: output: ==> default: Importing a QEMU instance
==> default: Importing a QEMU instance
INFO interface: detail: Creating and registering the VM...
INFO interface: detail:     default: Creating and registering the VM...
    default: Creating and registering the VM...
INFO subprocess: Starting process: ["/bin/cp", "/opt/homebrew/share/qemu/edk2-aarch64-code.fd", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/bin/cp", "/opt/homebrew/share/qemu/edk2-arm-vars.fd", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/opt/homebrew/bin/qemu-img", "create", "-f", "qcow2", "-F", "qcow2", "-b", "/Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/box.img", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Formatting '/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=68719476736 backing_file=/Users/c10l/.vagrant.d/boxes/c10l-VAGRANTSLASH-debian-11.4/202208.02.0/libvirt/box.img backing_fmt=qcow2 lazy_refcounts=off refcount_bits=16
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO interface: detail: Successfully imported VM
INFO interface: detail:     default: Successfully imported VM
    default: Successfully imported VM
INFO machine: New machine ID: "2KHndMEWOYE"
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00007f9c9c172330>
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00007f9c9c2feb18>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::IsState:0x00007f9c7c859358>
DEBUG is_state: Checking if machine state is 'running'
INFO machine: Calling action: read_state on provider QEMU (2KHndMEWOYE)
INFO interface: Machine: action ["read_state", "start", {:target=>:default}]
INFO runner: Running action: machine_action_read_state #<Vagrant::Action::Builder:0x00007f9c9c21ce20>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00007f9c8cb63728>
INFO warden: Calling IN action: #<VagrantPlugins::QEMU::Action::ReadState:0x00007f9c8cb63700>
INFO warden: Calling OUT action: #<VagrantPlugins::QEMU::Action::ReadState:0x00007f9c8cb63700>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00007f9c8cb63728>
INFO interface: Machine: action ["read_state", "end", {:target=>:default}]
DEBUG is_state: -- Machine state: stopped
INFO warden: Calling IN action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x00007f9c9c2a5658>
DEBUG storeboxmetadata: Writing box metadata file to /Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/box_meta
INFO warden: Calling OUT action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x00007f9c9c2a5658>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::IsState:0x00007f9c7c859358>
INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x00007f9c7c850910>
INFO warden: Calling IN action: #<Proc:0x00007f9c8cb43798 /opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:126 (lambda)>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x00007f9c7c850690>
INFO provision: Checking provisioner sentinel file...
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::EnvSet:0x00007f9c9c1ccd30>
INFO warden: Calling IN action: #<VagrantPlugins::QEMU::Action::PrepareForwardedPortCollisionParams:0x00007f9c9c1ccc90>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x00007f9c9c1cc9e8>
DEBUG environment: Attempting to acquire process-lock: fpcollision
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: fpcollision
INFO handle_port_collisions: Detecting any forwarded port collisions...
DEBUG handle_port_collisions: Extra in use: {}
DEBUG handle_port_collisions: Remap: {2222=>50022}
DEBUG handle_port_collisions: Repair: false
DEBUG handle_port_collisions: Remap port override: 2222 => 50022
INFO environment: Released process lock: fpcollision
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO warden: Calling IN action: #<VagrantPlugins::SyncedFolderNFS::ActionCleanup:0x00007f9c9f2c2340>
WARN nfs: nfs_valid_ids not set, cleanup cannot occur
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x00007f9c9c296ef0>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Delayed:0x00007f9c9f373578>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolders:0x00007f9c9f373550>
INFO synced_folders: SyncedFolders loading from cache: false
INFO warden: Calling IN action: #<VagrantPlugins::QEMU::Action::WarnNetworks:0x00007f9c8c9f6ca0>
INFO interface: warn: Warning! The QEMU provider doesn't support any of the Vagrant
high-level network configurations (`config.vm.network`). They
will be silently ignored.
INFO interface: warn: ==> default: Warning! The QEMU provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.
==> default: Warning! The QEMU provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SetHostname:0x00007f9c8c9f6c00>
INFO warden: Calling IN action: #<VagrantPlugins::QEMU::Action::StartInstance:0x00007f9c9c362f28>
INFO interface: output: Starting the instance...
INFO interface: output: ==> default: Starting the instance...
==> default: Starting the instance...
INFO subprocess: Starting process: ["/opt/homebrew/bin/qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
ERROR warden: Error occurred: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x00007f9c9c1cc9e8>
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00007f9c9c172330>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00007f9c9c3793b8>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock: machine-action-6fdf74554a6cf795a3f1ed8a421b6379
INFO environment: Running hook: environment_unload
INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00007f9c9c63d130>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<VagrantPlugins::QEMU::Errors::ExecuteError: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout: >
ERROR vagrant: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
ERROR vagrant: /Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/driver.rb:160:in `execute'
/Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/driver.rb:88:in `start'
/Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/action/start_instance.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/set_hostname.rb:17:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/action/warn_networks.rb:14:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/delayed.rb:19:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/plugins/synced_folders/nfs/action_cleanup.rb:14:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:52:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/action/prepare_forwarded_port_collision_params.rb:29:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/env_set.rb:19:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/provision.rb:80:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builder.rb:149:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `block in run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/Users/c10l/.vagrant.d/gems/2.7.4/gems/vagrant-qemu-0.1.8/lib/vagrant-qemu/action/import.rb:49:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builder.rb:149:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `block in run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/box_check_outdated.rb:93:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/builder.rb:149:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `block in run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in `run'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/machine.rb:246:in `action_raw'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/machine.rb:215:in `block in action'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/environment.rb:614:in `lock'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/machine.rb:201:in `call'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/machine.rb:201:in `action'
/opt/vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'
INFO interface: error: A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
A command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["qemu-system-aarch64", "-machine", "virt,accel=hvf,highmem=off", "-cpu", "cortex-a72", "-smp", "2", "-m", "4G", "-device", "virtio-net-device,netdev=net0", "-netdev", "user,id=net0,hostfwd=tcp::50022-:22", "-drive", "if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on", "-drive", "if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd", "-chardev", "socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off", "-mon", "chardev=mon0,mode=readline", "-chardev", "socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off", "-serial", "chardev:ser0", "-pidfile", "/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid", "-parallel", "null", "-monitor", "none", "-display", "none", "-vga", "none", "-daemonize", {:notify=>[:stdout, :stderr, :stdin]}]

Stderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes

Stdout:
INFO interface: Machine: error-exit ["VagrantPlugins::QEMU::Errors::ExecuteError", "A command executed by Vagrant didn't complete successfully!\nThe command run along with the output from the command is shown\nbelow.\n\nCommand: [\"qemu-system-aarch64\", \"-machine\", \"virt,accel=hvf,highmem=off\", \"-cpu\", \"cortex-a72\", \"-smp\", \"2\", \"-m\", \"4G\", \"-device\", \"virtio-net-device,netdev=net0\", \"-netdev\", \"user,id=net0,hostfwd=tcp::50022-:22\", \"-drive\", \"if=virtio,format=qcow2,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/linked-box.img\", \"-drive\", \"if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-aarch64-code.fd,readonly=on\", \"-drive\", \"if=pflash,format=raw,file=/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/edk2-arm-vars.fd\", \"-chardev\", \"socket,id=mon0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket,server=on,wait=off\", \"-mon\", \"chardev=mon0,mode=readline\", \"-chardev\", \"socket,id=ser0,path=/Users/c10l/.vagrant.d/tmp/vagrant-qemu/2KHndMEWOYE/qemu_socket_serial,server=on,wait=off\", \"-serial\", \"chardev:ser0\", \"-pidfile\", \"/Users/c10l/src/proxmox/client-go/.vagrant/machines/default/qemu/2KHndMEWOYE/qemu.pid\", \"-parallel\", \"null\", \"-monitor\", \"none\", \"-display\", \"none\", \"-vga\", \"none\", \"-daemonize\", {:notify=>[:stdout, :stderr, :stdin]}]\n\nStderr: qemu-system-aarch64: Addressing limited to 32 bits, but memory exceeds it by<PHONE_NUMBER> bytes\n\n\n\nStdout: "]

1 ❯

hi @c10l
Thanks for your help.
But seems what you are using is not my plugin.
If you check https://github.com/billyan2018/vagrant-qemu/blob/main/VERSION which is 0.2.22
And your version is 0.1.8...
You may installed some other plugin which is also named vagrant-qemu
If you execute
vagrant plugin list

You should be able to see sth like
vagrant-qemu (0.2.22, global)
  - Version Constraint: 0.2.22

Thank you, and sorry for wasting your time! Indeed that plugin was installed with vagrant plugin install vagrant-qemu, and that one doesn't seem to support overriding the command.
I'll try yours now and see if it helps. I'll close this issue now since it clearly does not apply.


Some recipes don't work unless you break and replace the Projector

https://www.youtube.com/watch?v=4RUvnEbN4j4
This is on FTB University 1.16, which has compactcrafting-1.0.0-beta.3

Same issue on Ragnamod VI with compactcrafting-1.0.0-beta.3

Please let me know if this is still an issue with beta 5/6. Those versions have additional toggles for more logging, which can help track this down.

Can no longer reproduce this in the latest code. Closing as it will be solved in beta 8.


Bluetooth pairing

The "Improving your Bluetooth pairing experience" hyperlink takes you to a page (https://docs.microsoft.com/en-us/windows-insider/at-home/Whats-new-wip-at-home-20h1#improving-your-bluetooth-pairing-experience-build-18985) that has no "Bluetooth pairing" content.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d651de3c-b8eb-e8d9-8138-1eadb758bf2e
Version Independent ID: a19a8b65-0f4a-efd5-7f83-56bd07cc8c3b
Content: What's new in Windows 10, version 2004 - What's new in Windows
Content Source: windows/whats-new/whats-new-windows-10-version-2004.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

(ref. #8923 )

(ref. #8923 )

Closing via #8923
Thank you

Closing via #8923
Thank you


FileSystemGlobbing passes invalid path upon upgrade to Core 2.0

From @JeremyKuhne on Monday, November 6, 2017 9:57:21 AM
From https://github.com/dotnet/home/issues/88 opened by @HarelM:
An unhandled exception of type 'System.ArgumentException' occurred in System.Private.CoreLib.dll
The path is not of a legal form.

System.Private.CoreLib.dll!System.IO.Path.GetFullPath(string path)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileSystemGlobbing.dll!Microsoft.Extensions.FileSystemGlobbing.InMemoryDirectoryInfo.InMemoryDirectoryInfo(string rootDir, System.Collections.Generic.IEnumerable<string> files, bool normalized)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileSystemGlobbing.dll!Microsoft.Extensions.FileSystemGlobbing.MatcherExtensions.Match(Microsoft.Extensions.FileSystemGlobbing.Matcher matcher, string rootDir, System.Collections.Generic.IEnumerable<string> files)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileSystemGlobbing.dll!Microsoft.Extensions.FileSystemGlobbing.MatcherExtensions.Match(Microsoft.Extensions.FileSystemGlobbing.Matcher matcher, string file)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.ReportChangeForMatchedEntries(string path)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnFileSystemEntryChange(string fullPath)	Unknown	No symbols loaded.
 	Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnRenamed(object sender, System.IO.RenamedEventArgs e)	Unknown	No symbols loaded.
 	System.IO.FileSystem.Watcher.dll!System.IO.FileSystemWatcher.NotifyRenameEventArgs(System.IO.WatcherChangeTypes action, string name, string oldName)	Unknown	No symbols loaded.
 	System.IO.FileSystem.Watcher.dll!System.IO.FileSystemWatcher.ParseEventBufferAndNotifyForEach(byte[] buffer)	Unknown	No symbols loaded.
 	System.IO.FileSystem.Watcher.dll!System.IO.FileSystemWatcher.ReadDirectoryChangesCallback(uint errorCode, uint numBytes, System.Threading.NativeOverlapped* overlappedPointer)	Unknown	No symbols loaded.
 	System.Private.CoreLib.dll!System.Threading._IOCompletionCallback.PerformIOCompletionCallback(uint errorCode, uint numBytes, System.Threading.NativeOverlapped* pOVERLAP)	Unknown	No symbols loaded.

More details are in the source issue. His site is here:

This is the relevant repository snapshot as I'm planning to check-in the downgrade to 1.1 later tonight.
https://github.com/IsraelHikingMap/Site/tree/fb4e06310e1c5135f446ded685ee548c7e948e28

Note that we (CoreFX) have not made any changes in System.IO from 1.1 to 2.0 that are in this code path.
Copied from original issue: aspnet/FileSystem#299

From @HarelM on Monday, November 6, 2017 1:22:15 PM
Might be a timing issue that is happening only in 2.0 for some reason as this issue is not happening all the time, but when updating my database on my development environment this happens and so I can reproduce it with high probability (at least this was the case when I opened this issue).

From @czietsman on Wednesday, November 8, 2017 10:29:13 PM
I've seen our AspNetCore 2.0 app crash a few times. This morning it wrote out a similar stacktrace:
System.ArgumentException: The path is not of a legal form.
   at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
   at System.IO.Path.GetFullPathInternal(String path)
   at Microsoft.Extensions.FileSystemGlobbing.InMemoryDirectoryInfo..ctor(String rootDir, IEnumerable`1 files, Boolean normalized)
   at Microsoft.Extensions.FileSystemGlobbing.MatcherExtensions.Match(Matcher matcher, String rootDir, IEnumerable`1 files)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.ReportChangeForMatchedEntries(String path)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnFileSystemEntryChange(String fullPath)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnRenamed(Object sender, RenamedEventArgs e)
   at System.IO.FileSystemWatcher.OnRenamed(RenamedEventArgs e)
   at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* overlappedPointer)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

We use a PhysicalFileProvider to watch a settings file. The app ran overnight and there was no activity until this morning when I logged in. The app is running in a VM with Windows Server 2016 installed. Here is the setup code for watching the settings file which is located in UserRootPath:
Directory.CreateDirectory(UserRootPath);
UserRootFileProvider = new PhysicalFileProvider(UserRootPath);
...
changeToken = UserRootFileProvider.Watch(SETTINGS_FILE);

From @imamy4 on Wednesday, November 29, 2017 3:11:53 AM
Hi! I get this exception when saving file in VS2017.
Method Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnRenamed received RenamedEventArgs where FullPath is saving file name and OldFullPath is NULL. Further LegacyNormalizePath throws exception because get empty string as argument.
I watched FileSystemWatcher.cs, CompletionStatusChanged method contains which call NotifyRenameEventArgs(WatcherChangeTypes.Renamed, name, oldName) where oldName is NULL.
The problem began after upgrading my app to .NET Core 2.0

From @yp87 on Monday, December 11, 2017 2:12:54 PM
Our application crashes on that line since upgrade to 2.0 {"The path is not of a legal form."}:
 [Managed to Native Transition]        Annotated Frame
     mscorlib.dll!System.IO.Path.NewNormalizePath(string path, int maxPathLength, bool expandShortPaths) Line 500    C#    Symbols loaded.
     mscorlib.dll!System.IO.Path.NormalizePath(string path, bool fullCheck, int maxPathLength, bool expandShortPaths) Line 423    C#    Symbols loaded.
     mscorlib.dll!System.IO.Path.GetFullPathInternal(string path) Line 368    C#    Symbols loaded.
     Microsoft.Extensions.FileSystemGlobbing.dll!Microsoft.Extensions.FileSystemGlobbing.InMemoryDirectoryInfo.InMemoryDirectoryInfo(string rootDir, System.Collections.Generic.IEnumerable files, bool normalized) Line 56    C#    Symbols loaded.
     Microsoft.Extensions.FileSystemGlobbing.dll!Microsoft.Extensions.FileSystemGlobbing.MatcherExtensions.Match(Microsoft.Extensions.FileSystemGlobbing.Matcher matcher, string rootDir, System.Collections.Generic.IEnumerable files) Line 108    C#    Symbols loaded.
     Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.ReportChangeForMatchedEntries(string path) Line 258    C#    Symbols loaded.
     Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnFileSystemEntryChange(string fullPath) Line 235    C#    Symbols loaded.
     Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.OnRenamed(object sender, System.IO.RenamedEventArgs e) Line 181    C#    Symbols loaded.
     System.dll!System.IO.FileSystemWatcher.OnRenamed(System.IO.RenamedEventArgs e) Line 921    C#    Symbols loaded.
     System.dll!System.IO.FileSystemWatcher.CompletionStatusChanged(uint errorCode, uint numBytes, System.Threading.NativeOverlapped* overlappedPointer) Line 590    C#    Symbols loaded.
     mscorlib.dll!System.Threading._IOCompletionCallback.PerformIOCompletionCallback(uint errorCode, uint numBytes, System.Threading.NativeOverlapped* pOVERLAP) Line 135    C#    Symbols loaded.
     [Native to Managed Transition]        Annotated Frame

From @natemcmaster on Thursday, December 14, 2017 9:27:20 AM
cc @muratg for triage

From @muratg on Thursday, December 14, 2017 9:52:01 AM
@natemcmaster Any idea how this may have regressed?  Assigning to you, but we can load-balance later based on the workload.

From @natemcmaster on Thursday, December 14, 2017 12:34:57 PM
@muratg  I can probably take a look at this next week.
@HarelM  @yp87 @imamy4 @czietsman if any of you have a minimal repro, that would be great. The snippets you shared are good clues for an investigation, but still not a full repro since I don't know what kind of values you're passing in to PhysicalFileProvider and other APIs.

From @czietsman on Friday, December 15, 2017 3:55:59 AM
@natemcmaster I'll see if I can put something together for you. I was running my app from within a VM (Hyper-V) with the host drive shared as G:. My binaries were build on the host. It happened pretty frequently if my working directory was also on the shared drive (G:), but hasn't been happening if I started the app from the VM's C: drive.
This setup made it a little bit more tricky to debug the input values coming from OnRenamed().

From @HarelM on Friday, December 15, 2017 6:09:57 AM
Sorry, Not sure how to create a minimal repro as in my case it seems like it has to do with timing.

From @yp87 on Friday, December 15, 2017 8:16:55 AM
In our case, it is aspnetcore's content root physicalFilesWatcher that triggers this issue. The self hosted aspnetcore server is used by a component that is part of a much larger software.  We do not even use the content root, but it was pointing to the base folder of our software (which has some tmp files being created/modified/deleted). The issue happened when a change to one of those file was done (not always). When the issue occurs, the FileSystemWatcher detects a rename of a tmp file root/aa.tmp -> root/ which does not even make sense..

From @jmorrill on Monday, January 1, 2018 11:57:49 AM
I'm hitting this with a fairly simple web app.  It is triggered by writing an HLS stream to "wwwroot/streams/[guid]/video.m3u8".  HLS creates, renames and deletes quite a bit.
Here is a screenshot of where the problem "starts" at:
// Previous FILE_ACTION_RENAMED_OLD_NAME with no new name
NotifyRenameEventArgs(WatcherChangeTypes.Renamed, null, oldName);

Here's the "RenamedEventArgs" the PhysicalFilesWatcher.cs gets

Notice e.FullPath is ONLY a directory path that does not contain a file.

Might be because this is already a month old but I'm getting the following warning when using @natemcmaster 's instructions:
warning NU1603: IsraelHiking.Web depends on Microsoft.Extensions.FileProviders.Physical (>= 2.0.1-rtm-215) but Microsoft.Extensions.FileProviders.Physical 2.0.1-rtm-215 was not found. An approximate best match of Microsoft.Extensions.FileProviders.Physical 2.1.0-preview1-27256 was resolved

And using this version I still get the following error:
An unhandled exception of type 'System.ArgumentException' occurred in System.Private.CoreLib.dll
The path is not of a legal form.

It takes a few minutes to simulate it using my project, but I can reproduce it almost every time I try.
See the linked project above, I have created a .NetCore2.1 branch to try and reproduce the issue.
Let me know if you would like to test this project as the setup is not straight forward...

Ignore my last comment, Apprently VS doesn't restore on build after changing .csproj file.
I have deleted my last message, it seems like this patch solves the problem.
Please let me know when I can get it from NuGet.

Any updates on when an official release will have this fix?

It's in the patch release that went out yesterday.
https://www.nuget.org/packages/Microsoft.Extensions.FileProviders.Physical/2.0.1

@natemcmaster, Thanks for the update, hopefully I will be able to migrate to 2.0 finally :-)!


Different files?

Why do u put all the code in one file why don't u separate the files like SystemNotify.js

https://github.com/ru-alpha/discord-relay/issues/18


[WIP] Update Qurro to support pandas v1 and up, and thus newer versions of QIIME 2

Port CI from Travis to GitHub Actions (close #316)

Made use of the nice matrix functionality in GitHub Actions to automatically test on multiple QIIME 2 versions.
Currently, we just test on the oldest and newest QIIME 2 versions that Qurro supports (2020.11 and whatever the latest is). (The reason 2020.11 is the oldest Q2 version we support is because it's the first that switched over to pandas >= 1.)
Added a standalone CI, analogous to EMPress' standalone CI.

Updated the code to not use pd.SparseDataFrame, and instead use pd.DataFrame with sparse arrays (close #258, close #315)

This required much less work than it sounds like, because biom.Table.to_dataframe() does all the heavy lifting. Previously, Qurro was actively avoiding using that function due to a bug with it (https://github.com/biocore/biom-format/issues/808), but -- now that that bug is fixed in all biom versions that Qurro accepts -- we can just delegate to it.

Updated the code to remove various sources of warnings. A lot of things have become deprecated in the past few years (e.g. pd.DataFrame.append(), using a set as an indexer in pandas, np.matrix, ...)

Updated the documentation regarding the minimum Q2 version stuff

This PR is almost ready to go -- the main things I need to fix are

[ ] rerunning all of the example notebooks now that there aren't five million warnings being created from #258

as an extra difficulty spike, some of the dependencies of these notebooks are now incompatible with the sort of conda environments we set up (e.g. Songbird explicitly requires a pandas version < 1). There are various ways to get around this, ranging from "convert the notebooks to markdowns and call it a day", "split into separate notebooks", etc; let's see what's easiest.

[ ] updating the changelog

Codecov Report

Merging #322 (94d5129) into master (005cc44) will increase coverage by 1.26%.
The diff coverage is 100.00%.

:exclamation: Current head 94d5129 differs from pull request most recent head 07d7665. Consider uploading reports for the commit 07d7665 to get more accurate results

@@            Coverage Diff             @@
##           master     #322      +/-   ##
==========================================
+ Coverage   95.09%   96.36%   +1.26%
==========================================
  Files          19        3      -16
  Lines        1408      771     -637
  Branches      234      139      -95
==========================================
- Hits         1339      743     -596
+ Misses         57       28      -29
+ Partials       12        0      -12

Impacted Files
Coverage Δ

qurro/support_files/js/display.js
95.86% <100.00%> (+0.08%)
:arrow_up:

qurro/__init__.py

qurro/_df_utils.py

qurro/_json_utils.py

qurro/_metadata_utils.py

qurro/_rank_utils.py

qurro/generate.py

qurro/q2/_visualizers.py

qurro/qarcoal.py

qurro/scripts/_plot.py

... and 7 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2509145...07d7665. Read the comment docs.

as an extra difficulty spike, some of the dependencies of these notebooks are now incompatible with the sort of conda environments we set up (e.g. Songbird explicitly requires a pandas version < 1). There are various ways to get around this, ranging from "convert the notebooks to markdowns and call it a day", "split into separate notebooks", etc; let's see what's easiest.

Honestly I think we should just not run the notebooks and keep them static. Dependencies issues are going to accumulate and I don't think we should be expected to maintain them continually specifically for notebooks. Maybe just add a note that dependencies may have changed since creation. (Willing to change my mind on this, though.)

Honestly I think we should just not run the notebooks and keep them static. Dependencies issues are going to accumulate and I don't think we should be expected to maintain them continually specifically for notebooks. Maybe just add a note that dependencies may have changed since creation. (Willing to change my mind on this, though.)

That's fair -- this is definitely the more sustainable way to handle this :) That being said, I figure things are pretty stable for the time being: after looking into things, the bulk of the problems wound up coming from Songbird now being incompatible with Qurro's environments.
In my opinion, supporting the combo of Songbird + Qurro is important, so I took some time and updated the "Red Sea" notebook to explain how to run Songbird and Qurro in separate conda environments. That fixed most of the problems (the other main thing was updating the ALDEx2 notebook, which wasn't too bad); the notebooks are now all up-to-date (and, as a nice bonus, now the users don't see all of those pandas warnings about SparseDataFrame being deprecated...) However, if things break horribly in a month, ... then I'll probably just add a note, like you suggest.
This PR should now be ready for review / merging.


How to load a dynamic page ?

thanks for this cool plugins.
I can load static pages including index.html.
but, I had spent a whole day to figure out the way to serve a dynamic page, e.g.:
http://localhost:7000/apicall?A=1&B=2&C=3
is't ok for you to bring us examples for Dynamic pages and example Helper?

Dynamic pages don't have the right name. They should really be called static pages. You can set there content but you can't render them on a request specific basis.

It has been a goal to work in an event based system for rendering pages as they come. This is somewhat hard to do as I need to get the request to bubble up safely from client thread to volt thread and then to the main thread, then all the way back again.


Reset module variable after all tests in module are completed.

Refactor looks good, very similar to what I did in the new API PR...

Due to the issues with a similar change in the 0.4.x branch, I'm going to hold on merging this until I can verify it works against a couple apps

Okay had some minor updates around tests and the name used by the module. @rwjblue would appreciate one more quick review before merging.