Closed edwinpjacques closed 5 years ago
Even after the merge, I am getting this error from windows 10:
PLAY RECAP *********************************************************************
==> vqfx1: Box 'juniper/vqfx10k-re' could not be found. Attempting to find and install...
vqfx1: Box Provider: virtualbox
vqfx1: Box Version: >= 0
==> vqfx1: Loading metadata for box 'juniper/vqfx10k-re'
vqfx1: URL: https://vagrantcloud.com/juniper/vqfx10k-re
==> vqfx1: Adding box 'juniper/vqfx10k-re' (v0.3.0) for provider: virtualbox
vqfx1: Downloading: https://vagrantcloud.com/juniper/boxes/vqfx10k-re/versions/0.3.0/providers/virtualbox.box
vqfx1: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
==> vqfx1: Successfully added box 'juniper/vqfx10k-re' (v0.3.0) for 'virtualbox'!
==> vqfx1: Importing base box 'juniper/vqfx10k-re'...
==> vqfx1: Matching MAC address for NAT networking...
==> vqfx1: Checking if box 'juniper/vqfx10k-re' version '0.3.0' is up to date...
==> vqfx1: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_vqfx1_1561717114148_51769
==> vqfx1: Fixed port collision for 22 => 2222. Now on port 2200.
==> vqfx1: Clearing any previously set network interfaces...
==> vqfx1: Preparing network interfaces based on configuration...
vqfx1: Adapter 1: nat
vqfx1: Adapter 2: intnet
vqfx1: Adapter 3: intnet
vqfx1: Adapter 4: intnet
vqfx1: Adapter 5: intnet
vqfx1: Adapter 6: intnet
vqfx1: Adapter 7: intnet
vqfx1: Adapter 8: intnet
==> vqfx1: Forwarding ports...
vqfx1: 22 (guest) => 2200 (host) (adapter 1)
==> vqfx1: Running 'pre-boot' VM customizations...
==> vqfx1: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "b28655db-5373-4d9a-bdc9-c22737e15281", "--type", "headless"]
Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output file /dev/null (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
root@aburston-P50:/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan#
@edwinpjacques somewhere you missed a /dev/null in the code because it is blowing up on windows.
It could be because when you run this thing on windows you are running under the Ubuntu subsystem and vagrant thinks you are running in linux...
HI @aburston are you still having this issue? Maybe we can do a screen share when you're back. If you're doing this then I guess the test to see if we're running on a Windows host may not be working... may need to implement another test. We'll have to play around with it.
@aburston I am going to create a new issue for this and close this one.
Boot time is terribly slow in the latest version of Virtual Box on OS X. May be an issue with the serial port in BSD since it seems to take forever to display text to the console. Every "vagrant up" times out. Takes maybe 30m to boot on an Intel i7. Tested with Junos 17.4, 18.1 and 18.4.