sachdev...@gmail.com
VBoxManage --version
4.3.22r98236
vagrant --version
Vagrant 1.7.2
I modified the Vagrantfile to add another host ip
config.vm.network "private_network", ip: "192.168.33.10"
The list of gems is as following
gem list bosh
*** LOCAL GEMS ***
bosh-template (1.2840.0)
bosh_cli (1.2840.0)
bosh_common (1.2840.0)
On running "vagrant up --provider=virtualbox" get the following logs
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/precise32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise32' is up to date...
==> default: Setting the name of the VM: bosh_cli-128400_default_1424418788654_7
3001
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 80 => 8080 (adapter 1)
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:
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 its 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.2.0
default: VirtualBox Version: 4.3
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => C:/Ruby21-x64/lib/ruby/gems/2.1.0/gems/bosh_cli-1.2840.0
Seems that all the vagrant configuration is successful. I am able to successfully ping 192.168.33.10. However, when I try to set it as Director, its not successful.
bosh target 192.168.33.10 lite
DL is deprecated, please use Fiddle
Usage: target [<director_url>] [<name>]
No error message comes. But when I try to see status, it shows target not set.
Need some help in troubleshooting this issue.
Koper, Dies
Just wondering, but have you tried vagrant ssh’ing into the VM and using bosh CLI inside?
That’s what I did when I used bosh-lite on Windows to work around issues bosh CLI had with uploading and downloading files on Windows.
Regards,
Dies Koper
To unsubscribe from this group and stop receiving emails from it, send an email to bosh-dev+u...@cloudfoundry.org.
Jones, Daniel
Hi all,
I haven’t had the below issue with BOSH Lite on Windows, but I have had instances on three different machines of the BOSH Lite VM ‘hanging’ for seconds at a time every 30 seconds or so. This is manifested by the odd connectivity issue when using the CLI, and by hanging when typing during a `vagrant ssh` session. The machines are fairly decent spec (quad core, 8 or 16GiB RAM, SSDs) and the virtualisation platform is VirtualBox.
I’d originally put this down to idiosyncrasies of the installation on my machine, but having seen the same thing on two further machines I’m wondering if it would be worth investigating further? Has anyone else experienced this? Are there any common gotchas of VirtualBox config that I may have missed?
Regards,
Daniel Jones
Daniel Jones I 723 6362 I +44 (0)1732 776362 I Cell: +44 (0)79 8000 9153
Fidelity Worldwide Investment I 130 Tonbridge Road, Hildenborough, Kent, TN11 9DZ
The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Fidelity only gives information on products and services and does not give investment advice to retail clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142) and Financial Administration Services Limited (Reg. No. 1629709) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg. No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ.
Daniel Mikusa
Hi all,
I haven’t had the below issue with BOSH Lite on Windows, but I have had instances on three different machines of the BOSH Lite VM ‘hanging’ for seconds at a time every 30 seconds or so. This is manifested by the odd connectivity issue when using the CLI, and by hanging when typing during a `vagrant ssh` session. The machines are fairly decent spec (quad core, 8 or 16GiB RAM, SSDs) and the virtualisation platform is VirtualBox.
I’d originally put this down to idiosyncrasies of the installation on my machine, but having seen the same thing on two further machines I’m wondering if it would be worth investigating further? Has anyone else experienced this?