-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Description
Debug output
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31969
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31969
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31969
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31969
DEBUG subprocess: Exit status: 1
INFO environment: Running hook: environment_unload
INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000073cb70481ae8>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VBoxManageError:"There was an error while executing `VBoxManage`, a CLI used by Vagrant\nfor controlling VirtualBox. The command and stderr is shown below.\n\nCommand: [\"showvminfo\", \"fad824f5-72bc-4e37-a04e-e63c8ea84faa\"]\n\nStderr: Warning: program compiled against libxml 212 using older 209\nVBoxManage: error: Failed to create the VirtualBox object!\nVBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)\nVBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.\n">
ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
Stderr: Warning: program compiled against libxml 212 using older 209
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/driver/base.rb:444:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/util/retryable.rb:20:in `retryable'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/driver/base.rb:402:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/driver/version_5_0.rb:933:in `vm_exists?'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/driver/meta.rb:102:in `initialize'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/provider.rb:61:in `new'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/provider.rb:61:in `machine_id_changed'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/providers/virtualbox/provider.rb:41:in `initialize'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/machine.rb:144:in `new'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/machine.rb:144:in `initialize'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/vagrantfile.rb:84:in `new'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/vagrantfile.rb:84:in `machine'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/environment.rb:756:in `machine'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/plugin/v2/command.rb:183:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/plugin/v2/command.rb:207:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/plugin/v2/command.rb:189:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/plugin/v2/command.rb:189:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/plugins/commands/up/command.rb:88:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/cli.rb:67:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/lib/vagrant/environment.rb:317:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-2.4.9/bin/vagrant:238:in `<main>'
INFO interface: error: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
Stderr: Warning: program compiled against libxml 212 using older 209
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["showvminfo", "fad824f5-72bc-4e37-a04e-e63c8ea84faa"]
Stderr: Warning: program compiled against libxml 212 using older 209
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
INFO interface: Machine: error-exit ["Vagrant::Errors::VBoxManageError", "There was an error while executing `VBoxManage`, a CLI used by Vagrant\nfor controlling VirtualBox. The command and stderr is shown below.\n\nCommand: [\"showvminfo\", \"fad824f5-72bc-4e37-a04e-e63c8ea84faa\"]\n\nStderr: Warning: program compiled against libxml 212 using older 209\nVBoxManage: error: Failed to create the VirtualBox object!\nVBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)\nVBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.\n"]
Expected behavior
vagrant up should always work and should not require me to use the workaround.
Current workaround is to remove:
<ExtraDataItem name="HostOnly/vboxnet0/IPAddress" value="192.168.56.1"/>
<ExtraDataItem name="HostOnly/vboxnet0/IPNetMask" value="255.255.255.0"/>
This lines from my Virtualbox.xml config and after that vagrant up works fine and doesn't time out.
Actual behavior
vagrant up works and adds:
<ExtraDataItem name="HostOnly/vboxnet0/IPAddress" value="192.168.56.1"/>
<ExtraDataItem name="HostOnly/vboxnet0/IPNetMask" value="255.255.255.0"/>
In my VirtualBox.xml config
vagrant halt works fine
vagrant up doesn't work the second time anymore, it just hangs and ends with following exception given in debug output.
Vagrant version
Vagrant 2.4.9
Host operating system
Linux ThinkPad-P1 6.14.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 7 18:32:38 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 25.04 with Wayland
Guest operating system
Virtualbox 7.1.12
Issue
Why does vagrant write HostOnly/vboxnet0/IPAddress into VirtualBox.xml config? can this also be removed or cleaned up? Why is this issue happening? Is it a Vagrant or Virtualbox problem?
Thank you for your help!