Skip to main content

Access Virtualbox Guest machine via SSH


How to Access via ssh a Virtualbox Guest machine.

By default, the network connection in VirtualBox is set to NAT (Network Address Translation), that is every packet coming from the Guest machine is modified so that it seems as it has come from the Host machine. In this way it’s easy for the Guest machine to connect to all the rest of the network (the internet included) but nobody can start a connection with the Guest Machine since it’s hidden behind the Host one.
So, if you are going to test a server service in your Guest machine (i.e. Apache or ssh) you have two choices:
  1. pass to Virtualbox Host network connection;
  2. make virtualbox forward all the packets arriving to a certain port of the Host machine.
This article will describe how to do the latter, in particular in the case of the ssh server. This is an interesting case because it allows you to simulate very well a quite common condition: connecting to a remote Linux headless machine.




We have a Guest Machine with a running ssh server which accepts connections on the TCP port 22. Our goal is to make any packet arriving at a given TCP port (i.e. 2222) of the Host machine, to be forwarded to the TCP port 22 of the Guest Machine.
Fortunately, there is Virtualbox command which permits to do it almost instantly: VBoxManage.
Let <guestname> be the Guest machine name (quote it if it contains spaces), here are the commands that you have to type in the Host machine console:
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/HostPort" 2222
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/GuestPort" 22
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/Protocol" TCP
You can change the string “ssh” with any other you like more. The HostPort must be greater than or equal to 1024 since listening on ports 0-1023 needs root permssions (and Virtualbox usually doesn’t). Instead, GuestPorthas to be equivalent to the one on which the virtualized ssh is listening.
Once you have typed the above commands, you need to close the Guest Machine (a reboot won’t be sufficient), restart it and then connect via ssh with:
$ ssh -l <user> -p 2222 localhost
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/http/HostPort" 8080
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/http/GuestPort" 80
$ VBoxManage setextradata <guestname> "VBoxInternal/Devices/pcnet/0/LUN#0/Config/http/Protocol" http
The above command will forward port 8080 of host to port 80 of guest. similarly more ports can be forwarded.

For reference : http://mydebian.blogdns.org/?p=148
And this ACTUALLY worked on our systems.

Comments

  1. We have tested the above as Positive on ubuntu Server 9.10 and ubuntu Desktop 9.04, 9.10, 10.04 and 10.10 as guest and Virtualbox-ose running on Linux mint 7 as host as well as Windows 7 as host.

    ReplyDelete
  2. A common problem faced by ubuntu desktop users :
    OPENSSH SERVER IS NOT INSTALLED BY DEFAULT.
    install it first, only then try to ssh, else it will show failure.

    ReplyDelete

Post a Comment

Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

15 minutes of courage

"I Quit" , said she and walked out as briskly as she could, her face as stern as a stone. She didn't look back. I wanted her to. I felt helpless, somewhat creepy, and a sudden chill went down my spine. I didn't know what to do. I wanted to just run away. Run away from her. Run away from this world. Run away to some distant place where I could be myself. Some place where I could cry to my heart's content. But I was not one of those who would leave the ground, wounded! I had always been the one who took life head on. So was it the time to lean back and contemplate what actually went wrong? No. That won't be the man, the world knew! So.. was it the time to build a castle around my feelings and play cold? ~ Prince Mishra

How the Python import system works

How the Python import system works From:  https://tenthousandmeters.com/blog/python-behind-the-scenes-11-how-the-python-import-system-works/ If you ask me to name the most misunderstood aspect of Python, I will answer without a second thought: the Python import system. Just remember how many times you used relative imports and got something like  ImportError: attempted relative import with no known parent package ; or tried to figure out how to structure a project so that all the imports work correctly; or hacked  sys.path  when you couldn't find a better solution. Every Python programmer experienced something like this, and popular StackOverflow questions, such us  Importing files from different folder  (1822 votes),  Relative imports in Python 3  (1064 votes) and  Relative imports for the billionth time  (993 votes), are a good indicator of that. The Python import system doesn't just seem complicated – it is complicated. So even though the  documentation  is really good, it d