I have CentOS7 installed on Vmware, and I'm able to access it through SSH from my computer where Vmware is installed. I need to access my virtual machine from another computer. Is this possible? and what are the steps to complete this?
It is possible. You need to bridge your network adapter with the one on the VM, and then it will be accessible the same way your PC is.
Related
I am working with an Ubuntu 18.04 virtual machine. I can SSH into this machine via puTTy on the same computer. However, how can I access this machine from another computer? Or do I have any option to set this machine as a cloud server so others can access and run it?
I think that would all depend on how the networking is configured on your VM.
You can configure the network as bridged (where the VM has it's own dedicated IP address on the local subnet), NAT (where the VM shares the IP with the system running Workstation, but NAT rules can be configured to handle traffic), or host-only (where only the system running Workstation is able to connect to it).
Bridged is probably the easiest to use for your situation.
More information on these networking configs: Common Networking Configurations for Workstation
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 am running a virtual machine in Bluemix and want to open the OS's desktop GUI. How do I do this? Thanks for your help.
I've edited your question to what I think you're asking: How can I open the desktop GUI on my virtual machine in Bluemix?
Assuming I understand the question correctly:
To open the desktop GUI on a remote virtual machine, use Virtual Network Computing (VNC). This solution is not specific to Bluemix; it'll work with a VM running on any platform, as long as the VM is running an OS that supports VNC.
To use VNC, you need to have a VNC server running in your VM's OS. You will then run a VNC client (a.k.a. viewer) on your computer to display the VM's desktop. The specific instructions depend on the OS running in the VM and on your computer.
For example, assuming your VM is running Ubuntu v14.04, these resources explain what to do (and a search will find other resources):
"How to Install and Configure VNC on Ubuntu 14.04" -- Installs XFCE4 as the VNC server
"How To Install And Configure VNC On Ubuntu 14.04" -- Also installs XFCE4.
"How to Install VNC Server on Ubuntu 14.04 LTS" -- Installs TightVNC as the VNC server
For a VNC client, I actually connect to remote VMs via a local VM running Ubutu 14.04, so I use Vinagre (a.k.a. the Remote Desktop Viewer app). Options listed by other authors include TightVNC, RealVNC, or UltraVNC.
Good luck and thanks for using Bluemix.
From what I understand, you need some remote desktop tool to get to the UI of the OS of your virtual machine. Some tools available: http://www.techradar.com/us/news/software/applications/7-of-the-best-linux-remote-desktop-clients-716346
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.
I'm running Server 2008 64bit with Hyper-V. I've created a virtual machine with Vista 64bit and installed it. I can't get the Vista virtual machine to see the network adapter.
I've set-up an external network on the Virtual Network Manager (Hyper-V) and associated that with the virtual machine (Vista). I've also tried using a Legacy Network Adapter but that didn't work either although that time the Vista machine saw the network card but couldn't connect through it.
This is (obviously) the first time I've tried to set-up a virtual machine.
Any ideas?
EDIT: I notice that this question has been voted down a couple of times. I know that it's not a programming question but I'm a developer setting up a virtual machine to test my C#/ASP.NET code on and thought that other developers may hit this problem as well when they're doing this...
I don't know Hyper-V, but I know in VMWare you can create a network connection in Bridged mode (meaning the VM will get it's own IP address via DHCP if that's enabled) or host-only mode (meaning the VM can only communicate with the host). When Vista could see the card, could it communicate with the host machine (which would indicate a host-only connection was specified)? What kind of IP address did it have (I would guess Hyper-V has a built-in DHCP server like VMWare does?) -- that might give additional clues.
Sorry I don't know Hyper-V better...
Make sure you have the Hyper-V Tools installed on the Guest VM. You shouldn't need the legacy adapter.
You also may want to make sure you have all of the latest updates which may have addressed your issue. Particularly, KB950050
http://support.microsoft.com/kb/950050
It turns out that Vista x64 running as a VM through Hyper-V doesn't support the virtual network connection/card and that you have to set it up as a legacy network card. When I eventually got the config settings correct for the legacy network and disable the virtual network it connected.
Thanks for the help guys - much appreciated!