This will work, thanks.
On Sun, Aug 24, 2014 at 11:32 PM, Alvaro Miranda Aguilera wrote:
> what I would do will be
>
> - set a share folder between the host and the vm, mount as read only
> - shell provisioner to copy and set permissions, and i will use rsync
> locally between this folder and t
if you have a simple vagrant file, example
config.vm.box = "box"
and that's ist, it should not use ssh at all
ssh is used to configure the guest SO.
so comment out everything, and see if that works.
you should be able to use configuration that is external, like those
virtualbox/vmware provisio
Hi,
I use vagrant to boot a customized virtual machine [the linux kernel is
customized]. The vm boots fine, when i use the vagrant up command. In the
next step vagrant tries to run vagrant ssh and tries to insert the
insecure_key. As the kernel is customized, it does not understand the
command
Hello,
64 bits VM require Virtualization extension on the host.
you should try 64 bit host, 32 bit vm, then 32bit vm
otherwise, you should use a different virtualization tool that allow that.
vmware, lxc, docker.
Alvaro.
On Tue, Aug 26, 2014 at 12:51 AM, Santhosh Kumar
wrote:
> Hi Torben,
docker is an isolation layer, let me cut this down on what will be shared,
and they you can say YES, I WANT THOSE THINGS ISOLATED! (with a bad mood
manager face)
Let's use vagrant here, simple approach, just 1 vm, no docker.
You will end with 1 VM, with a linux OS
1 user vagrant, with a known pub
Can you please explain the test case?
You want to avoid anyone using it?
why?
you mean, ssh server in the guest, or make 'vagrant ssh' command to work?
ssh is used between vagrant (tool) and the guest to perform tasks, so if
you lock the ssh, then you wouldn't be able to shutdown the vm properly
As noted in this article:
https://blog.abevoelker.com/rails-development-using-docker-and-vagrant/
When the `d.build_dir = "."` is used the stdout docker build logs are
hidden from the user.
It would be nice if this were not the case somehow.
--
You received this message because you are subscr
Hi,
Is there any way i could disable the vagrant ssh functionality after
executing the vagrant up command?
Thanks!
-varun
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an em
Thanks for the reply!
I agree, going forward I think my best best is to:
Device a secured box that meets my guidelines
Use that as the base box when provisioning
However, now we come to *how* to provision. People have suggested I use
Docker, but is that possible or easy with this scenario:
I
Hi Torben,
Made the changes you mentioned and also made gui=true and made no. of cpus
as one
I get the following error in VirtualBox GUI
VT-x/AMD-V hardware acceleration is not available on your system. Your
64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.
Regards,
Hi Santhosh,
cool, good to know that nested 32bit VMs do work! It was quite some
time ago when I tried VirtualBox inside VirtualBox...
Concerning your issue: have you tried enabling / disabling VT-X?
These VBoxManage commands might be helpful:
VBoxManage modifyvm --hwvirtex off
VBoxManage modi
Hi Torben,
32 bit VM in a virtualbox inside VirtualBox is working, only 64 bit isn't
working.
Is there a specific reason for that.
On Monday, 25 August 2014 16:13:49 UTC+5:30, Torben Knerr wrote:
>
> Hi Santhosh,
>
> to my best knowledge it is not possible to run VirtualBox inside
> VirtualBox
Hi Santhosh,
to my best knowledge it is not possible to run VirtualBox inside VirtualBox.
You can run VirtualBox VMs inside a VMWare VM though...
Cheers,
Torben
On Mon, Aug 25, 2014 at 12:14 PM, Santhosh Kumar wrote:
> I'm using Windows-7 host & VirtualBox 4.3.12
> Guest - CentOS-6.5 64bit ,
Hi Manish,
you might wanna have a look at the
https://github.com/tmatilai/vagrant-proxyconf plugin, which configures
the proxy on the guest machine.
Also make sure you have the `http_proxy` and `https_proxy` env vars
set on the host.
HTH,
Torben
On Mon, Aug 25, 2014 at 11:22 AM, Manish Mehra
I'm using Windows-7 host & VirtualBox 4.3.12
Guest - CentOS-6.5 64bit , Im trying to run vagrant up from the guest
I get the following error in the log: VT-x not available
Box used in Vagrant file: puppetlabs/centos-6.5-64-puppet
Is it possible to run a 64 bit VM within a vm ?
On Friday, 22 Augus
I'm using Windows-7 host & VirtualBox 4.3.12
Guest - CentOS-6.5 64bit , Im trying to run vagrant up from the guest
I get the following error in the log: VT-x not available
Box used in Vagrant file: puppetlabs/centos-6.5-64-puppet
On Friday, 22 August 2014 12:21:14 UTC+5:30, Santhosh Kumar wrote:
>
Hi Team
I am working in a corporate proxy environment. I followed the steps given
under
"http://swaeku.github.io/blog/2013/03/09/installing-vagrant-on-ubuntu-12-dot-10/";
to install a new virtual box in my machine but I got following error:
"Timed out while waiting for the machine to boot. Thi
17 matches
Mail list logo
