Emulate an ARM Plaform with QEMU on Ubuntu 10.10

Orange Pi Development Boards

When developing software for embedded systems, you may need to support multiple architectures such as  arm, mips, x86, powerpc, alpha etc.. but you may not have the hardware required on hand to test them.

This is where QEMU – a processor emulator – comes to the rescue. In a way, QEMU is similar to VirtualBox, VMWare or Citrix Xendeskop except it can support multiple architectures.

I’ll show how to run Debian Lenny ARMEL in QEMU on a computer running Ubuntu 10.10 (aka Ubuntu Maverick Meerkat).

QEMU (Qemu-kvm) Installation

First install qemu-kvm and qemu-kvm-extras (the latter contains qemu-system-arm):

sudo apt-get install qemu-kvm qemu-kvm-extras

Let’s check qemu version:

[email protected]:~/edev$ qemu –version
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard

Debian ARM Installation in QEMU

Create a directory to store the required files for the emulator and  download the Debian Lenny ARMEL kernel (vmlinuz) and debian installer rootfs (initrd.gz):

mkdir ~/arm-emul

cd ~/arm-emul

wget ftp://ftp.debian.org/debian/dists/lenny/main/installer-armel/current/images/versatile/netboot/vmlinuz-2.6.26-2-versatile

wget ftp://ftp.debian.org/debian/dists/lenny/main/installer-armel/current/images/versatile/netboot/initrd.gz

Create a raw virtual hard disk large enough (e.g. 2GB) for Debian:

qemu-img create -f raw hda.img 2G

Run the ARM virtual machine and follow the instructions to install Debian. This may take several hours, since all instructions are decoded by software:

qemu-system-arm -m 256 -M versatilepb -kernel ~/arm-emul/vmlinuz-2.6.26-2-versatile -initrd ~/arm-emul/initrd.gz -hda ~/arm-emul/hda.img -append “root=/dev/ram”

After the system reboots, close QEMU.

Running Debian ARM in QEMU

Once the installation is complete, mount the first disk partition of the QEMU disk image with a loop device (offset 32256) in order to copy the initrd (rootFS) (mount QEMU images):

mkdir mount
sudo mount -o loop,offset=32256 ~/arm-emul/hda.img ~/arm-emul/mount
cp ~/arm-emul/mount/boot/initrd.img-2.6.26-2-versatile ~/arm-emul/
sudo umount ~/arm-emul/mount

Then run Debian ARMEL in QEMU as follows:

qemu-system-arm -m 256 -M versatilepb -kernel ~/arm-emul/vmlinuz-2.6.26-2-versatile -initrd ~/arm-emul/initrd.img-2.6.26-2-versatile -hda ~/arm-emul/hda.img -append “root=/dev/sda1”

That’s it, you now have a running ARM virtual machine. You can cross-compile your application or library in your host PC (compiling them in the emulator would be very slow), copy them to the VM (via NFS for example) and run them in your ARM emulator. As long as those are not graphics intensive or processor intensive, they should work just fine.

Once the emulator is running you can check the emulated CPU is an ARM926E-JS Core.

QEMU ARM926ej-s-linux-2.6.26.2

I got most of the instructions from http://blog.troyastle.com/2010/07/building-arm-powered-debian-vm-with.html

25
Leave a Reply

avatar
24 Comment threads
1 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
11 Comment authors
dseichterSahilARM cross compiling in 5 minutes | myBitBoxA Little Ludwig Goes A Long Way » Grab bag of raspberry pi dev infoBrian Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Datanasty
Guest
Datanasty

You need to be consistent with your image name; first you use ‘flash.img’, then proceed to reference it as ‘hda.img’. Pick one or the other.

rafal98
Guest
rafal98

Thx a lot, it’s a very useful topic.

Sander
Guest
Sander

After “mkdir arm-emul” I suppose there must be a “cd arm-emul”?

Sander
Guest
Sander

PS: I had to “mkdir ~/arm-emul/mount” too. Correct?

Sander
Guest
Sander

And some more remarks:

Thanks to your blog I was able to run Debian on ARM on Qemu on Ubuntu 11.04. Thank you.

On the first try, I choose to also install X / the Desktop Environment, but that lead to problems, probably because the 2 GB virtual disk was too small. On the second try, I choose only the default install (without X). Maybe worth to mention.

Sometimes Qemu will ‘grab’ the mouse and I couldn’t switch to Ubuntu anymore. You must press CTRL + ATL to escape it again (as Qemu clearly says in it’s Window ;-( )

Is there a graphical but non-X game I can install and play in Debian?

Sander
Guest
Sander

And some more feedback:

The last instruction ( to run Debian ARMEL in QEMU) contains a new line (making it harder to copy-paste) and strange double-quotes at the end (maybe caused by your web layout program): plain ” is needed.

FWIW: I created a 5GB harddisk, installed Debian including “Desktop Environment”. However, at ‘startx’ I get an old-skool X server error message. I have never learned how to solve those problems 🙁

Strangely enough wget en lynx work, but ping and mtr show no response …

Someone Special
Guest
Someone Special

Why in the world are you using KVM to emulate ARM architechture? KVM is x86(-64) only! It makes no sense to try to use KVM, unless you are also emulating x86 CPUs. Just install qemu-system, that is all you need!

marcegarba
Guest
marcegarba

Thanks very much for your blog post.

Ashwin
Guest

Even worked for Ferdora13 64bit…
Very nicely written….

Greg
Guest
Greg

Hi, nice blog post. I wasn’t able to get the loopback mount command to work. It gives the following error.

mount: you must specify the filesystem type

I tried things like ext2, ext3, etc but still could not mount. Any idea what to do?

Greg
Guest
Greg

Hi cnx, here is what I got. N.b. this is the 3.2 kernel & installer, so maybe that is why the offset don’t match. Everything else seems working fine.

$ file hda.img
hda.img: x86 boot sector; partition 1: ID=0x83, active, starthead 32, startsector 2048, 3911680 sectors; partition 2: ID=0x5, starthead 190, startsector 3915774, 276482 sectors, code offset 0xb8
$ fdisk hda.img
Command (m for help): p

Disk hda.img: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000664f1

Device Boot Start End Blocks Id System
hda.img1 * 2048 3913727 1955840 83 Linux
hda.img2 3915774 4192255 138241 5 Extended
hda.img5 3915776 4192255 138240 82 Linux swap / Solaris

Greg
Guest
Greg

Ah, figured it out. The “startsector 2048” means that the partition starts at 2048 * 512 = 1048576.

Using the new offset works great!

Brian
Guest
Brian

@Greg: Thanks for the tip!

@cnxsoft: What are you using for compiler options to gcc on the host? When I build a “hello world” with “arm-linux-gnueabi-gcc-4.6 -mcpu=arm926ej-s -o /tmp/hello hello.c” and copy it to the VM, I end up with an illegal instruction error.

trackback

[…] arm emulation guide adn this one have a little more detail on how to generate and modify the ondisk image, I might want to mix these […]

Sahil
Guest
Sahil

But this only gives the console.
Is there any way to get the GUI??

Sahil
Guest
Sahil

@cnxsoft
Thanks a lot!

dseichter
Guest
dseichter

additional hint:
If you are trying this really great tutorial, you maybe fail on the step on mounting the hda.img as loop device:
sudo mount -o loop,offset=32256 ~/arm-emul/hda.img ~/arm-emul/mount

for example, you will receive the error
mount: wrong fs type, bad option, bad superblock on /dev/loop0

This happens, because of your installation process (I installed Debian Jessie).
You have to correct the offset-value. This will be done really simple:

run:
sudo fdisk -l /path/to/img-file

your output will be for example:
Disk hda.img: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd14b0c4f

Device Boot Start End Sectors Size Id Type
hda.img1 2048 3913727 3911680 1,9G 83 Linux
hda.img2 3915774 4192255 276482 135M 5 Extended
hda.img5 3915776 4192255 276480 135M 82 Linux swap / Solaris

To calculate the correct offset value, just do “sector size * Start sector of the linux partition”. The result is the value for your offset value.
In my case, it was 1048576

So, I had to run:
sudo mount -o loop,offset=1048576 hda.img mount