I'm using Vagrant on Virtual Box. The install scripts automatically set up PuTTY for ssh session with the environment. The thing is, it often is slow and lags. The session will freeze while I type and I have to wait about a minute for the text to appear. I was wondering if anyone else had this issue and what they did to resolve it. Thanks !
Related
I'm using Ubuntu 18.04 and it got stuck in 1~2 seconds when I push the tab button for auto-completion.
I've been trying to resolve this problem but I couldn't make it. I even changed my computer to the new one but it has same problem.
One weird thing is that when I connect my ubuntu with ssh in other pc(using teraterm or putty or other pc's ubuntu), the problem is gone and works well.
I don't know why.. Could it be a network problem? My ubuntu pc is behind the firewall and proxy but my companies' ubuntu next to me works well.
Is there anything suspicious to you?
sudo updatedb
The database is rebuilt for auto completion.
Maybe check your hard disk health as this could be a hardware issue, and the disk is struggling to read, and the command is searching the database and taking longer to complete.
I've finally found the answer!!
To resolve this problem, turn off the "Terminal bell" option of terminal.
In terminal,
Edit > Preferences > Sound > Terminal bell
I'm using ssh from a Windows-10 box in two ways: one connects to a SSH server that I've installed on a remote Windows machine (Windows-8 I think...); one connects to a VirtualBox VM that's local.
When I press control-C, the Windows session disconnects. The Linux session simply prints ^C.
I'd like to keep the Windows-hosted session from disconnecting, too. But, what and where's the difference?
I'm still looking for an answer to this one, but I did notice something unusual. This particular machine has sh ... the Cygwin bash-shell. And, if you enter that program, control-C no longer cuts the session! As long as you stay in it. (Although, as I've asked separately, it has other "issues" of its own having to do with backspace and arrow keys.)
I'm using vagrant inside the linux VM using VMWare and the hosted machine is windows-base. So it's a virtual machine inside a virtual machine.
So when I try to boot the vagrant box I got this error
When I google I couldn't able to find the exact solution for this but here in this question Vagrant up timeout #BrainC pointed out that enable GUI mode from vagrant config file it will give you better idea what exactly going wrong here. but still I couldn't able to find any cause of the problem!
So what's the really issue here... is it because of virtual-machine inside virtual-machine or it's something else.
UPDATE:
when i enabled gui option in vagrantfile gui opens it shows some error BUT IT happend so fast I couldn't able to see it, so I've recorded the screen and this is what i got
I am kind of new to using vagrant with oracle's virtual box. I was wondering if anyone knows if it is a good idea or not to use vagrant halt before restarting or rebooting my host machine?
Vagrant halt
is another way of saying shutdown; it is a good practice to do that since it will attempt to shut the VM gracefully where as windows will force it to. As a result you may sometimes get an error saying the VM wasn't shut properly and is now on a protected mode or saved mode and need to be rebuilt.
I am pretty new to vagrant. I have installed an ubuntu 14.04 trusty box on my vagrant and will use it for my web development environment. I want to know which is the best way to disable/close/shutdown a vagrant box so that data in it remain safe in the next session? I mean when I want to shutdown my laptop (in windows 10, my host machine os is win10) there is a message telling me that virtualbox interface is open. so if I close the process then I cant access vagrant box anymore. I want a good way to close vagrant and run it in my next working session.
I read about vagrant halt before host shutdown and using vagrant up in next session but it takes too long to run a vagrant up.
**summary : I WANT A WAY TO DO THIS:
1- close a vagrant box without a data loss in it;
2- shutdown my laptop without seeing the message that tells virtualbox interface is open.
3- run vagrant box and access it with putty as fast as possible when I start working again.
is there a way to do this?**
thanks.
I want to know which is the best way to disable/close/shutdown a vagrant box so that data in it remain safe in the next session
I would not necessarily to recommend vagrant halt which will completely stop your VM and will need to start up after you restart your host.
You can run vagrant suspend which will hold your data and you will retrieve your instance in the same state as it was before on your next startup
You can read more about the differences between halt and suspend