Cannot Start VirtualBox on Ubuntu 14.04

[signsanssignified]

Host OS: Ubuntu 14.04
Guest OS: 'Ubuntu_64'
VirtualBox: 5.0.16 r105871
Vagrant: 1.7.4

Attempting to start up VirtualBox & vagrant this morning via 'vagrant up', I got the following error message:

Code: Select all

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg*)" at line 71 of file VBoxManageHostonly.cpp

Working with people at vagrant & using this post (https://www.vagrantup.com/docs/other/debugging.html) as a guide, I did the following:

Code: Select all

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

yielding this error message:

"sudo: /Library/StartupItems/VirtualBox/VirtualBox: command not found"

Attached is the relevant vbox.log.

Not sure if you need my vagrantfile, but here are the contents of that:

Code: Select all

# -*- mode: ruby -*-
# vi: set ft=ruby :

vagrant_dir = File.expand_path(File.dirname(__FILE__))

Vagrant.configure("2") do |config|

  # Store the current version of Vagrant for use in conditionals when dealing
  # with possible backward compatible issues.
  vagrant_version = Vagrant::VERSION.sub(/^v/, '')

  # Configurations from 1.0.x can be placed in Vagrant 1.1.x specs like the following.
  config.vm.provider :virtualbox do |v|
    v.customize ["modifyvm", :id, "--memory", 1024]
    v.customize ["modifyvm", :id, "--cpus", 1]
    v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    v.customize ["modifyvm", :id, "--natdnsproxy1", "on"]

    # Set the box name in VirtualBox to match the working directory.
    vvv_pwd = Dir.pwd
    v.name = File.basename(vvv_pwd)
  end

  # Configuration options for the Parallels provider.
  config.vm.provider :parallels do |v|
    v.update_guest_tools = true
    v.optimize_power_consumption = false
    v.memory = 1024
    v.cpus = 1
  end

  # Configuration options for the VMware Fusion provider.
  config.vm.provider :vmware_fusion do |v|
    v.vmx["memsize"] = "1024"
    v.vmx["numvcpus"] = "1"
  end

  # Configuration options for Hyper-V provider.
  config.vm.provider :hyperv do |v, override|
    v.memory = 1024
    v.cpus = 1
  end

  # SSH Agent Forwarding
  #
  # Enable agent forwarding on vagrant ssh commands. This allows you to use ssh keys
  # on your host machine inside the guest. See the manual for `ssh-add`.
  config.ssh.forward_agent = true

  # Default Ubuntu Box
  #
  # This box is provided by Ubuntu vagrantcloud.com and is a nicely sized (332MB)
  # box containing the Ubuntu 14.04 Trusty 64 bit release. Once this box is downloaded
  # to your host computer, it is cached for future use under the specified box name.
  config.vm.box = "ubuntu/trusty64"

  # The Parallels Provider uses a different naming scheme.
  config.vm.provider :parallels do |v, override|
    override.vm.box = "parallels/ubuntu-14.04"
  end

  # The VMware Fusion Provider uses a different naming scheme.
  config.vm.provider :vmware_fusion do |v, override|
    override.vm.box = "netsensia/ubuntu-trusty64"
  end

  # VMWare Workstation can use the same package as Fusion
  config.vm.provider :vmware_workstation do |v, override|
    override.vm.box = "netsensia/ubuntu-trusty64"
  end

  # Hyper-V uses a different base box.
  config.vm.provider :hyperv do |v, override|
    override.vm.box = "ericmann/trusty64"
  end

  config.vm.hostname = "vvv"

  # Local Machine Hosts
  #
  # If the Vagrant plugin hostsupdater (https://github.com/cogitatio/vagrant-hostsupdater) is
  # installed, the following will automatically configure your local machine's hosts file to
  # be aware of the domains specified below. Watch the provisioning script as you may need to
  # enter a password for Vagrant to access your hosts file.
  #
  # By default, we'll include the domains set up by VVV through the vvv-hosts file
  # located in the www/ directory.
  #
  # Other domains can be automatically added by including a vvv-hosts file containing
  # individual domains separated by whitespace in subdirectories of www/.
  if defined?(VagrantPlugins::HostsUpdater)
    # Recursively fetch the paths to all vvv-hosts files under the www/ directory.
    paths = Dir[File.join(vagrant_dir, 'www', '**', 'vvv-hosts')]

    # Parse the found vvv-hosts files for host names.
    hosts = paths.map do |path|
      # Read line from file and remove line breaks
      lines = File.readlines(path).map(&:chomp)
      # Filter out comments starting with "#"
      lines.grep(/\A[^#]/)
    end.flatten.uniq # Remove duplicate entries

    # Pass the found host names to the hostsupdater plugin so it can perform magic.
    config.hostsupdater.aliases = hosts
    config.hostsupdater.remove_on_suspend = true
  end

  # Private Network (default)
  #
  # A private network is created by default. This is the IP address through which your
  # host machine will communicate to the guest. In this default configuration, the virtual
  # machine will have an IP address of 192.168.50.4 and a virtual network adapter will be
  # created on your host machine with the IP of 192.168.50.1 as a gateway.
  #
  # Access to the guest machine is only available to your local host. To provide access to
  # other devices, a public network should be configured or port forwarding enabled.
  #
  # Note: If your existing network is using the 192.168.50.x subnet, this default IP address
  # should be changed. If more than one VM is running through VirtualBox, including other
  # Vagrant machines, different subnets should be used for each.
  #
  config.vm.network :private_network, id: "vvv_primary", ip: "192.168.50.4"

  config.vm.provider :hyperv do |v, override|
    override.vm.network :private_network, id: "vvv_primary", ip: nil
  end

  # Public Network (disabled)
  #
  # Using a public network rather than the default private network configuration will allow
  # access to the guest machine from other devices on the network. By default, enabling this
  # line will cause the guest machine to use DHCP to determine its IP address. You will also
  # be prompted to choose a network interface to bridge with during `vagrant up`.
  #
  # Please see VVV and Vagrant documentation for additional details.
  #
  # config.vm.network :public_network

  # Port Forwarding (disabled)
  #
  # This network configuration works alongside any other network configuration in Vagrantfile
  # and forwards any requests to port 8080 on the local host machine to port 80 in the guest.
  #
  # Port forwarding is a first step to allowing access to outside networks, though additional
  # configuration will likely be necessary on our host machine or router so that outside
  # requests will be forwarded from 80 -> 8080 -> 80.
  #
  # Please see VVV and Vagrant documentation for additional details.
  #
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Drive mapping
  #
  # The following config.vm.synced_folder settings will map directories in your Vagrant
  # virtual machine to directories on your local machine. Once these are mapped, any
  # changes made to the files in these directories will affect both the local and virtual
  # machine versions. Think of it as two different ways to access the same file. When the
  # virtual machine is destroyed with `vagrant destroy`, your files will remain in your local
  # environment.

  # /srv/database/
  #
  # If a database directory exists in the same directory as your Vagrantfile,
  # a mapped directory inside the VM will be created that contains these files.
  # This directory is used to maintain default database scripts as well as backed
  # up mysql dumps (SQL files) that are to be imported automatically on vagrant up
  config.vm.synced_folder "database/", "/srv/database"

  # If the mysql_upgrade_info file from a previous persistent database mapping is detected,
  # we'll continue to map that directory as /var/lib/mysql inside the virtual machine. Once
  # this file is changed or removed, this mapping will no longer occur. A db_backup command
  # is now available inside the virtual machine to backup all databases for future use. This
  # command is automatically issued on halt, suspend, and destroy if the vagrant-triggers
  # plugin is installed.
  if File.exists?(File.join(vagrant_dir,'database/data/mysql_upgrade_info')) then
    if vagrant_version >= "1.3.0"
      config.vm.synced_folder "database/data/", "/var/lib/mysql", :mount_options => [ "dmode=777", "fmode=777" ]
    else
      config.vm.synced_folder "database/data/", "/var/lib/mysql", :extra => 'dmode=777,fmode=777'
    end

    # The Parallels Provider does not understand "dmode"/"fmode" in the "mount_options" as
    # those are specific to Virtualbox. The folder is therefore overridden with one that
    # uses corresponding Parallels mount options.
    config.vm.provider :parallels do |v, override|
      override.vm.synced_folder "database/data/", "/var/lib/mysql", :mount_options => []
    end
  end

  # /srv/config/
  #
  # If a server-conf directory exists in the same directory as your Vagrantfile,
  # a mapped directory inside the VM will be created that contains these files.
  # This directory is currently used to maintain various config files for php and
  # nginx as well as any pre-existing database files.
  config.vm.synced_folder "config/", "/srv/config"

  # /srv/log/
  #
  # If a log directory exists in the same directory as your Vagrantfile, a mapped
  # directory inside the VM will be created for some generated log files.
  config.vm.synced_folder "log/", "/srv/log", :owner => "www-data"

  # /srv/www/
  #
  # If a www directory exists in the same directory as your Vagrantfile, a mapped directory
  # inside the VM will be created that acts as the default location for nginx sites. Put all
  # of your project files here that you want to access through the web server
  if vagrant_version >= "1.3.0"
    config.vm.synced_folder "www/", "/srv/www/", :owner => "www-data", :mount_options => [ "dmode=775", "fmode=774" ]
  else
    config.vm.synced_folder "www/", "/srv/www/", :owner => "www-data", :extra => 'dmode=775,fmode=774'
  end

  config.vm.provision "fix-no-tty", type: "shell" do |s|
    s.privileged = false
    s.inline = "sudo sed -i '/tty/!s/mesg n/tty -s \\&\\& mesg n/' /root/.profile"
  end

  # The Parallels Provider does not understand "dmode"/"fmode" in the "mount_options" as
  # those are specific to Virtualbox. The folder is therefore overridden with one that
  # uses corresponding Parallels mount options.
  config.vm.provider :parallels do |v, override|
    override.vm.synced_folder "www/", "/srv/www/", :owner => "www-data", :mount_options => []
  end

  # The Hyper-V Provider does not understand "dmode"/"fmode" in the "mount_options" as
  # those are specific to Virtualbox. Furthermore, the normal shared folders need to be
  # replaced with SMB shares. Here we switch all the shared folders to us SMB and then
  # override the www folder with options that make it Hyper-V compatible.
  config.vm.provider :hyperv do |v, override|
    override.vm.synced_folder "www/", "/srv/www/", :owner => "www-data", :mount_options => ["dir_mode=0775","file_mode=0774","forceuid","noperm","nobrl","mfsymlinks"]
    # Change all the folder to use SMB instead of Virtual Box shares
    override.vm.synced_folders.each do |id, options|
      if ! options[:type]
        options[:type] = "smb"
      end
    end
  end

  # Customfile - POSSIBLY UNSTABLE
  #
  # Use this to insert your own (and possibly rewrite) Vagrant config lines. Helpful
  # for mapping additional drives. If a file 'Customfile' exists in the same directory
  # as this Vagrantfile, it will be evaluated as ruby inline as it loads.
  #
  # Note that if you find yourself using a Customfile for anything crazy or specifying
  # different provisioning, then you may want to consider a new Vagrantfile entirely.
  if File.exists?(File.join(vagrant_dir,'Customfile')) then
    eval(IO.read(File.join(vagrant_dir,'Customfile')), binding)
  end

  # Provisioning
  #
  # Process one or more provisioning scripts depending on the existence of custom files.
  #
  # provison-pre.sh acts as a pre-hook to our default provisioning script. Anything that
  # should run before the shell commands laid out in provision.sh (or your provision-custom.sh
  # file) should go in this script. If it does not exist, no extra provisioning will run.
  if File.exists?(File.join(vagrant_dir,'provision','provision-pre.sh')) then
    config.vm.provision :shell, :path => File.join( "provision", "provision-pre.sh" )
  end

  # provision.sh or provision-custom.sh
  #
  # By default, Vagrantfile is set to use the provision.sh bash script located in the
  # provision directory. If it is detected that a provision-custom.sh script has been
  # created, that is run as a replacement. This is an opportunity to replace the entirety
  # of the provisioning provided by default.
  if File.exists?(File.join(vagrant_dir,'provision','provision-custom.sh')) then
    config.vm.provision :shell, :path => File.join( "provision", "provision-custom.sh" )
  else
    config.vm.provision :shell, :path => File.join( "provision", "provision.sh" )
  end

  # provision-post.sh acts as a post-hook to the default provisioning. Anything that should
  # run after the shell commands laid out in provision.sh or provision-custom.sh should be
  # put into this file. This provides a good opportunity to install additional packages
  # without having to replace the entire default provisioning script.
  if File.exists?(File.join(vagrant_dir,'provision','provision-post.sh')) then
    config.vm.provision :shell, :path => File.join( "provision", "provision-post.sh" )
  end

  # Always start MySQL on boot, even when not running the full provisioner
  # (run: "always" support added in 1.6.0)
  if vagrant_version >= "1.6.0"
    config.vm.provision :shell, inline: "sudo service mysql restart", run: "always"
    config.vm.provision :shell, inline: "sudo service nginx restart", run: "always"
  end

  # Vagrant Triggers
  #
  # If the vagrant-triggers plugin is installed, we can run various scripts on Vagrant
  # state changes like `vagrant up`, `vagrant halt`, `vagrant suspend`, and `vagrant destroy`
  #
  # These scripts are run on the host machine, so we use `vagrant ssh` to tunnel back
  # into the VM and execute things. By default, each of these scripts calls db_backup
  # to create backups of all current databases. This can be overridden with custom
  # scripting. See the individual files in config/homebin/ for details.
  if defined? VagrantPlugins::Triggers
    config.trigger.before :halt, :stdout => true do
      run "vagrant ssh -c 'vagrant_halt'"
    end
    config.trigger.before :suspend, :stdout => true do
      run "vagrant ssh -c 'vagrant_suspend'"
    end
    config.trigger.before :destroy, :stdout => true do
      run "vagrant ssh -c 'vagrant_destroy'"
    end
  end
end

Trying to restart VirtualBox failed:

Code: Select all

sudo /etc/init.d/vboxdrv restart

yields this message:

Stopping VirtualBox kernel modules ...done.

Starting VirtualBox kernel modules ...failed!

(modprobe vboxnetflt failed. Please use 'dmesg' to find out why)

I was then informed that the issue is entirely a VirtualBox issue.

I ran this command:

Code: Select all

$ dmesg | grep VirtualBox

getting this result:

[ 5067.037574] warning: `VirtualBox' uses 32-bit capabilities (legacy
support in use)


Then I ran

Code: Select all

sudo modprobe -v vboxdrv

which did absolutely nothing after I entered the password at the prompt:

Code: Select all

$ sudo modprobe -v vboxdrv

[sudo] password for selfspunwebs:

Trying this:

Code: Select all

$ sudo apt-get install linux-headers-generic build-essential

got me this:

Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Then I tried this:

Code: Select all

sudo depmod -a

and then modprobe again:

Code: Select all

sudo modprobe -v vboxdrv

which again yielded nothing.

Please advise.

Thanks.

[Perryg]

I have already told you that we can not help you with this because you are using vagrant.

Have you tried to simply use VirtualBox without the vagrant assist modules?

What happens if you type virtualbox in a terminal? Does it open the main manager? Do you see your guest and can it start from the main manager?

[signsanssignified]

I apologize. I never saw your first message.

I am able to bring up VirtualBox via the CLI as you suggested. I'm not sure where to see the guest or how to determine whether it starts from the main manager (I'm new to all this, in case you hadn't guessed).

Please advise.

Thanks.

Ethan

[signsanssignified]

One more thing. You responded:

I have already told you that we can not help you with this because you are using vagrant.

I came to virtualbox.org after being told by the vagrant folks that they couldn't help me because this is a VirtualBox issue. Now I'm being told that the VirtualBox people can't help me because I'm running vagrant. I'm a bit confused--how & from whom can I get help given this feedback? Or does this mean I have to uninstall vagrant in order to debug & fix VirtualBox? if that's the case, how do I do it & what happens to my WordPress sites on vvv/VirtualBox?

Please advise.

Thanks.

[Perryg]

I never said that the fault was only vagrant, just that we can not help because of it. They change and use strange code to make things happen their way and since we do not use vagrant it is impossible to isolate any issue you may have.

Now you say you can start the VirtualBox main manager so you should be able to see a guest, however since vagrant was involved with your guest creation then it may not actually show. I suggest you try installing a Linux guest like mint to see if it works. Use the defaults since this is only a test and if it works then you know it is a vagrant issue. If not then we will have something to work with.

[signsanssignified]

Perry--

I don't know if this clarifies things or not, but I took a screenshot of VirtualBox (attached) after starting it via the CLI. There was a message saying it was starting up without full network access or some such thing (sorry I didn't capture that). I new enough that I don't know if it qualifies as seeing the guest or not.

Please advise.

Thanks.

VirtualBox screenshot

160409_virtualbox_screenshot.png (15.93 KiB) Viewed 5259 times

[Perryg]

Exact error messages are absolutely necessary. I can say that the screen shot you post is still trying to run the vagrant guest and it may not work in VBox either since it is still using the control files that vagrant builds themselves. Like I said download and install a new guest through VirtualBox like mint and leave everything set to default. Then post the guests log of the new Linux mint if it does not work. You should also post the /var/log/vbox-install.log as an attachment.

[signsanssignified]

OK. I've installed LInux Mint 17 in VirtualBox & started it up. I can see the guest. Attached are the VBox.log & vbox-install.log (zipped) files.

Please let me know if you need anything else.

Thanks.

160711_VBoxlog.txt

vbox.log file

(75.88 KiB) Downloaded 6 times

vbox-installlog.zip

(554 Bytes) Downloaded 6 times

[Perryg]

This log file shows you are booting from the CD and it is working. But you need to finish and actually install it to be sure you do not have any real issues. That said I can tell you that it shows you do not have an issue with the host or VirtualBox at this point, so it points to the vagrant portion that you have eliminated with this test.

One other thing I would like to see. Post the results of the following from the hosts terminal:

Code: Select all

VBoxManage list hostonlyifs

[signsanssignified]

1. What CD? It was installed.
2. No matter if I run

Code: Select all

VBoxManage list hostonlyifs

in vagrant-local, LINUXMINT17 or VirtualBox VMs, I get the same result:

"~/vagrant-local$ VBoxManage list hostonlyifs
selfspunwebs@xsbfvjn-Inspiron-3521:"

i.e., nothing.

Also, for a lark, I tried to startup vagrant again. I got the following error message in the cli:

"A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again."

Please advise.

Thanks.

[socratis]

@Perryg
You, sir, have my utmost respect for hanging on to this thread. Some people have way too thick heads to understand what they're told. In plain English...

[Perryg]

00:00:15.870997 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231
00:00:15.871504 VMMDev: Guest Log: BIOS: Boot from Floppy 0 failed
00:00:15.872127 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:15.920560 VMMDev: Guest Log: BIOS: Booting from CD-ROM...

The log file you posted shows you are booting from the CD-ROM. This means that you either did not install it or you forgot to remove the install media after the install.


You keep asking for advise when you try to use vagrant. I can't say it any clearer than I have already. We don't support nor use vagrant.

You need to answer these questions very clearly and procise.

• 1) where did you get your VirtualBox from?
  2) Did you install it yourself?
  3) where do/did you get the guest/s?

[signsanssignified]

1. I got VirtualBox here:

https://www.virtualbox.org

2. I did the nstallation myself via the terminal on 12/4/15.

3. I got the Ubuntu 14.04 guests as part of the installation of VVV here:

https://github.com/varying-vagrant-vagrants/vvv

I got Linux Mint 17 here:

https://www.linuxmint.com/edition.php?id=204

[Perryg]

You seem to have a valid official copy of VirtualBox and from the /var/log/vbox-install.log it appears that is should be functional.
Now back the Mint guest. You say that you installed it but the previous log showed it was still booting from CD.

Question:
Have you verified that you actually installed it and there is no CD in the virtual CD and that it actually boots to where you can use it?

Next question:
You should be able to start the VirtualBox main manager if from nowhere else but the terminal with typing virtualbox. Once you have the main manager running look at the top and click on File then preferences and find the network icon and click on it. Look to the right and click on the host-only tab and see if there is an entry called vboxnet0 and report back the findings of all the above questions.

[signsanssignified]

Have you verified that you actually installed it and there is no CD in the virtual CD and that it actually boots to where you can use it?

1. I actually installed it.
2. There is no CD in the virtual CD. Not clear what you mean when you say "that it actually boots to where you can use it." Please clarify. I apologize for being new to all this.

3.

You should be able to start the VirtualBox main manager if from nowhere else but the terminal with typing virtualbox.

Yup. No problem there.

4.

...see if there is an entry called vboxnet0.

There's no entry whatsoever under the host-only tab.