I'm running on BlueMix some test VM. Since today, it is impossible to even connect to the virtual machines (ssh, or running applications).
In the bluemix console, machines are running. I even tested to reboot one, without success.
Any idea or problem currently running ?
Were you able to ssh in before? Can you try using your ssh key with another VM to make sure its not an issue with your key
Related
I am running FreeNAS 11.1-U5 at home. I have everything configured and have created VM's for Windows Server, Ubuntu, pfSense, FreePBX. I was able to install Windows and Ubuntu, but shortly after (a few hours after installing them), and after turning them off through the FreeNAS GUI, they have stopped turning on. FreeNAS reports at the top of the GUI that the start was successful, but the VM details still read "stopped".
I have run the VM's before and have the required settings in my CMOS configured for the Host (FreeNAS machine). Restarting the host will fix the problem for a while and it will let me work with the VM's, but I cannot keep restarting FreeNAS. Can anyone tell me why this happens and how to fix it please?
I am new to Hadoop and the Big Data world...
I have installed the Hortonworks Sandbox VM in Virtual Box. It's working great...
Can someone tell me how to install Firefox within the VM? I need it to use NIFI
Thanks a lot for any help!
Installing a browser on the VM and using it through VNC will typically be very slow. The best option is to set up an SSH Tunnel and do a local forward. If you use the PuTTy ssh client on windows then you can follow the following instructions on setting up the local forward which will allow you to use your browser on the host operating system to connect to the NIFI instance running in your VM.
I have several servers running centOS 6 and centOS 7. I am working in an inventory system, and for that I am using ohai, which is installed in all the machines.
When I do ssh myuser#myserver.com ohai it returns a json object with all the information but the network section empty.
However, if I ssh into the server and I run ohai I get the proper network attributes.
Someone has any idea what can be happening? Thanks!
I solved, the problem was that ohai needs root rights to check the nics properties.
I have Windows 7. Installed VirtualBox and Ubuntu 11.04 as guest OS.
Networking is done by NAT.
Everything is fine: I have internet on Ubuntu.
I can access Windows from Ubuntu by its ip.
But i can't access Ubuntu by it's ip which is shown by ifconfig.
I run rails on Ubuntu.
How can I solve this problem: connect to Ubuntu/Rails server on ort 3000 from my Windows?
By default, VirtualBox's NAT allows the virtual machine to access the Internet ; but doesn't allow the physical machine to access the Virtual one.
The simplest solution would be to use another networking setting than NAT, for your Virtual Machine -- for instance, bridge should work fine (your VM would be visible on your network, though).
Another solution would be to use port forwarding ; about that, this article might help : Howto Access via ssh a Virtualbox Guest machine.
I used to struggle with configuring a similar setup until I found Vagrant. Vagrant makes it very simple to setup, connect to and work with a Linux virtual machine. After Vagrant is configured you can just type vagrant ssh to enter the virtual machine and your account has automatic sudo rights and everything works as expected - you don't even have to deal with logging into the vm. The initial setup for ssh does look to be a little more work under Windows though as you need to configure Putty before you can connect.
There is a simple configuration file in Vagrant that you use to specify which ports from the VM you want forwarded to your machine using a syntax like:
config.vm.forward_port("rails", 80, 3000)
config.vm.forward_port("tomcat", 8000, 8080)
and everything is taken care of. Details are here
If, for example, you are using Rails and you start vagrant with the command vagrant up in your Rails project directory than that directory is available on the VM. Since it is the same shared directory between machines, any changes you make in your Rails project directory on your machine using your regular editor is seen on the VM also. This makes testing in other environments very easy.
Instructions for setting Vagrant up with Windows are here and a RailsCast about it is here. Note that Vagrant has nothing to do directly with Rails - you can use it for setup of any virtual machine environment you need.
In short, you can't.
It is a local host not a public domain therefore not publicly accessible outside of your virtualbox environment.
Maybe someone has a clever hack for this but why would you want to do this in the first place?
Your solution is to either use firefox to browse to your localhost within your virtualbox linux session or develop on windows.
Personally I work the other way round I run Ubuntu 11.04 and I have virtualbox installations of xp, 2,000, me, vista and 7 so I can test in different environments. Inevitably I end up sharing my project folder from Ubuntu so that I can run the project in whatever OS I am testing for.
Since yesterday I can't connect through ssh to all of my Debian wheezy instances on my google cloud. I can connect only through the web console. When the web console tries to negotiate the session, there's a message telling me to update the Linux guest environment. But for wheezy, there is no Linux guest environment package.
Do you have any idea to resolve this issue ?
Debian 7 images were deprecated a while a go and as there are no update packages for the Guest Environment, the best approach would be to migrate to Debian 8 or 9.
To access your VMs you might try one of the following options:
1) According to this public issue the old guest environment still work with deprecated keys. If you have an SSH client configured with an old private key, you might still have access to your VMs through it.
2) Accessing the VM via the serial console
3) Mounting, as secondary, the original disk or a copy of it in a VM you do have access to. The steps are very similar to the section “Inspect an instance without shutting it down” on this document". That would allow you to recover your data.