How to Transfer files between the Host and Qemu via SSH and NFS

Last week, I wrote a blog post explaining how to copy files to a qemu image by mounting the qemu image in the host. This is only useful if emulated platform does not support networking.

If networking is enabled, using SSH (Secure Shell) or NFS (Network File System) is more convenient.

Using SSH with Qemu

To initiate the SSH connection from qemu, there is actually nothing extra to do as long as you have sshd installed and running on the host. If it is not installed simply run  sudo apt-get install openssh-shell on the host. This will install and automatically sshd.

To initiate the SSH connection from the host, you’ll have to redirect the ssh port to an unknown port and start qemu as follow (for overo):

sudo qemu-system-arm -M overo -m 256 -drive file=./overo_sd_alip.img,if=sd,cache=writeback -clock unix -serial stdio -device usb-kbd -device usb-mouse -redir tcp:2222::22

Please refer to Beagleboard Emulator in Ubuntu with Qemu for the detailed instructions on how to setup qemu to emulate beagleboard or overo (OMAP3 Platforms)

Then install dropbear – a lightweight SSH server – in qemu:

sudo apt-get install dropbear

This will also start dropbear automatically.

Once this is done, you can access qemu from the host as root or another user you may have added (Please note that  is the IP of the host):

ssh -p 2222 [email protected]
The authenticity of host ‘[]:2222 ([]:2222)’ can’t be established.
RSA key fingerprint is e1:3d:e2:0a:aa:2b:23:9e:7a:f9:97:48:3a:78:11:3b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘[]:2222’ (RSA) to the list of known hosts.
[email protected]’s password:
Welcome to Linaro 11.08 (GNU/Linux 3.0.0-1004-linaro-omap armv7l)

* Documentation:
[email protected]:~#

If you do not wish to enter the password each time you connect, follow the instructions at No password SSH – Login to a SSH server with private/public keys

No SSH access is working fine, simply use scp to copy files between the host and qemu, for example:

scp -P 2222 [email protected]:~

Using NFS with Qemu

You can basically follow the instructions given on Setting Up an NFS Server on Ubuntu to configure the host, with the difference that you’ll need to add the insecure option or the NFS connection will be denied (NFS4ERR_PERM) as  the insecure option allows to use IP ports that are above 1024. So the /etc/exports file would look like:

/mnt/nfs *(rw,no_root_squash,async,no_subtree_check,insecure)

Once the NFS server is configured on the host, you should be able to mount the NFS share in qemu:

[email protected]:~# mkdir /mnt/nfs
[email protected]:~# mount /mnt/nfs
[email protected]:~# mount | grep nfs on /mnt/nfs type nfs (rw,vers=4,addr=,clientaddr=
[email protected]:~#



Support CNX Software! Donate via PayPal or cryptocurrencies, become a Patron on Patreon, or buy review samples

Notify of
7 years ago

Is this post up to date with the QEMU 1.4.0 Ubuntu 13.04 distribution?
I mean if all the required support are avaible to do ssh communication are enablead for beagleboard or overo machines?

Is there a setup on the emulation code that has to be done before been able to ssh? (by this I meen that for been able to use more than one uart on bealge I had to add more serial_hds arguments to this function :omap3_mpu_init(cpu_model, ram_size, NULL, NULL, serial_hds[0], NULL) in bealge.c and I wonder If I have to do somthing like this for ethernet type connections)

7 years ago

I installed Open-ssh-client and server on both guest and host. I also installed dropbear on both. Qemu cmd used: sudo qemu-system-arm -M overo -m 512 -sd ./test.img -clock unix -device usb-mouse -device usb-kbd -serial pty -serial pty -serial pty -monitor pty -redir tcp:2222::22 I do an info usernet on QEMU<s monitor to get this: (qemu) info usernet VLAN 0 (user.0): Protocol[State] FD Source Address Port Dest. Address Port RecvQ SendQ TCP[HOST_FORWARD] 7 * 2222 22 0 0 then on the host side I use : $ ssh -p 2222 [email protected] ssh: connect to host port 2222: Connection refused… Read more »