On Mon, Oct 05, 2015 at 05:44:03PM +0530, Ritesh Raj Sarraf wrote: > On Mon, 2015-10-05 at 17:00 +0530, L. Guruprasad wrote: > > Other than that, does starting a Guest VM work from the VBox > > interface > > > ? > > > > > > That'd be the quickest for you to determine if the problem is with > > VBox > > > or Vagrant. > > > > Yes, I am able to start the VM using the VirtualBox GUI and it works > > absolutely fine. But when I do vagrant up, the VM gets created but > > does > > not get powered on for some reason That is why I suspected the issue > > to > > be with vagrant and reported the bug against it. > > > > Thanks for confirming. In that case, it may be specific to vagrant, or > the way vagrant interacts with VBox.
it works just fine for me, and I didn't have to install anything besides
virtualbox
$ dpkg-query --show virtualbox vagrant
vagrant 1.7.4+dfsg-1
virtualbox 5.0.6-dfsg-1
$ dpkg-query --show virtualbox-ext-pack
dpkg-query: no packages found matching virtualbox-ext-pack
$ pwd
/tmp/vbtest
$ vagrant init debian/jessie64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'debian/jessie64' could not be found. Attempting to find and
install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'debian/jessie64'
default: URL: https://atlas.hashicorp.com/debian/jessie64
==> default: Adding box 'debian/jessie64' (v8.2.0) for provider: virtualbox
default: Downloading:
https://vagrantcloud.com/debian/boxes/jessie64/versions/8.2.0/providers/virtualbox.box
==> default: Successfully added box 'debian/jessie64' (v8.2.0) for 'virtualbox'!
==> default: Importing base box 'debian/jessie64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/jessie64' is up to date...
==> default: Setting the name of the VM: vbtest_default_1444057364439_98530
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version
of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If
you see
default: shared folder errors, please make sure the guest additions within
the
default: virtual machine match the version of VirtualBox you have installed
on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.3.18
default: VirtualBox Version: 5.0
==> default: Mounting shared folders...
default: /vagrant => /tmp/vbtest
[...provisioning log...]
$ vagrant ssh -- dpkg --print-architecture
amd64
we need more details, logs and whatnot to figure out what is going on on
your system.
--
Antonio Terceiro <terce...@debian.org>
signature.asc
Description: PGP signature
