Difference between revisions of "QEMU"

From ArmadeusWiki
Jump to: navigation, search
(Apf27 support)
(→‎Get/generate simulation images (Linux & rootfs))
 
(24 intermediate revisions by 5 users not shown)
Line 11: Line 11:
 
==Installation==
 
==Installation==
 
* on Debian, *Ubuntu just do a:
 
* on Debian, *Ubuntu just do a:
−
  [armadeus]$ sudo apt-get install qemu bridge-utils ?vde?
+
  [armadeus]$ sudo apt-get install qemu bridge-utils vde
 +
* on Kubuntu 9.10 do:
 +
[armadeus]$ sudo apt-get install qemu bridge-utils qemu-kvm-extras vde
 +
* on Ubuntu 20.04:
 +
<pre>
 +
$ sudo apt-get install qemu qemu-system-arm
 +
</pre>
  
 
==Configuration==
 
==Configuration==
Line 20: Line 26:
  
 
<br>
 
<br>
−
{{Note|For a first try you can skip following part and go directly [[QEMU#Get.2Fgenerate_simulation_images|here.]]}}
+
{{Note|For a first try you can skip following part and go directly [[QEMU#Get.2Fgenerate_simulation_images_.28Linux_.26_rootfs.29|here.]]}}
 
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
 
As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode".
 
This mode require some configuration on your Host:
 
This mode require some configuration on your Host:
Line 63: Line 69:
 
</pre>
 
</pre>
  
−
==Get/generate simulation images==
+
==Get/generate simulation images (Linux & rootfs)==
−
* In our tests we used the QEMU Versatile PB emulated hardware. To get a compatible Linux kernel for this board then:
+
 
−
<pre class="host">
+
{| border="1" cellpadding="10" cellspacing="0" summary="" class="wikitable"
−
$ cd your_armadeus_view/
+
|- style="background:#efefef;" align="center"
−
$ wget http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.26-2-versatile
+
! APF27 !! APF6
−
</pre>
+
|-
 +
| * As QEMU doesn't support (yet) the APF, we will use the Versatile PB emulated hardware. To get a compatible Linux kernel for this board do:
 +
<pre class="host">$ cd your_armadeus_view/
 +
$ wget ftp://ftp2.armadeus.com/armadeusw/download/qemu/vmlinuz-2.6.29.6-versatile-armadeus</pre>
 +
one wanting to rebuild this image itself will find the corresponding config file in the same dir. (after compiling, take ''arch/arm/boot/zImage'')
 +
|| * As QEMU doesn't support (yet) the APF6, we will use the SabreLite emulated hardware.
 +
|}
 +
 
 
* get some useful environment variables:
 
* get some useful environment variables:
 
<pre class="host">
 
<pre class="host">
Line 74: Line 87:
 
  $ source armadeus_env.sh
 
  $ source armadeus_env.sh
 
</pre>
 
</pre>
−
* in ''$ARMADEUS_ROOTFS_DIR/etc/inittab'', comment following line:
+
* deactivate login on serial port:
−
<pre class="host">
+
** in Buildroot menuconfig:
−
  ttySMX0::respawn:/sbin/getty -L ttySMX0 115200,57600,38400 vt100
+
<pre class="config">
 +
System configuration --->
 +
    () Port to run a getty (login prompt) on
 
</pre>
 
</pre>
−
* Generate your Armadeus Rootfs as an EXT2 image:
+
: * and in ''$ARMADEUS_ROOTFS_DIR/etc/inittab'', comment following lines:
 
<pre class="host">
 
<pre class="host">
−
$ make menuconfig
+
# Put a getty on the serial port
−
</pre>
+
ttymxcX::respawn:/sbin/getty -L ttymxcX 115200 vt100 # GENERIC_SERIAL
−
<pre class="config">
+
 
−
Target filesystem options  --->
+
This can be achieved with sed :
−
    [*] ext2 root filesystem
+
sed --in-place -e "s/^ttymcX/#ttymcX/" $ARMADEUS_ROOTFS_DIR/etc/inittab
−
    ... (keep all default options)
+
 
</pre>
 
</pre>
 +
* Re-generate your Armadeus rootfs:
 
<pre class="host">
 
<pre class="host">
 
  $ make
 
  $ make
 
</pre>
 
</pre>
−
* be sure that your rootfs image is less than 16Mbytes (Ramdisk limit)
+
{| border="1" cellpadding="10" cellspacing="0" summary="" class="wikitable"
 +
|- style="background:#efefef;" align="center"
 +
! APF27 !! APF6
 +
|-
 +
|* check the size of your rootfs image
 
<pre class="host">
 
<pre class="host">
−
$ ls -al $ARMADEUS_BINARIES/*.ext2
+
$ ls -al $ARMADEUS_ROOTFS_TAR
 
</pre>
 
</pre>
−
* and zip it (we will use it as Ramdisk first):
+
* generate a dummy image larger than your rootfs; here 60 MBytes for a 45 MBytes tared rootfs:
 
<pre class="host">
 
<pre class="host">
−
$ gzip -9 $ARMADEUS_BINARIES/apfxx-rootfs.arm.ext2
+
$ dd if=/dev/zero of=armadeus-qemu.img bs=1MB count=60
 +
$ sudo mke2fs -F -m 0 -b 1024 armadeus-qemu.img
 
</pre>
 
</pre>
−
* Create a fake QEMU Hard disk image
+
* mount it and copy it your rootfs:
 
<pre class="host">
 
<pre class="host">
−
$ qemu-img create -f qcow rootfs.arm_nofpu2.img 20M
+
$ mkdir qemu_mnt
 +
$ sudo mount -t ext2 -o loop armadeus-qemu.img qemu_mnt/
 +
$ sudo tar xf $ARMADEUS_ROOTFS_TAR -C qemu_mnt/
 +
$ sudo umount qemu_mnt/
 
</pre>
 
</pre>
 +
|* APF6 has already EXT4 generated rootfs images
 +
|}
 +
* now you have all you need to launch Qemu
  
 
==Launch it==
 
==Launch it==
−
* At first boot, you have to launch the system as a Ramdisk:
+
===APF9328/27/51/28===
−
[armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
+
* Example with 64 MBytes of RAM:
−
    -initrd apf9328-rootfs.arm.ext2.gz -append "root=/dev/ram" -hda ./apf9328-rootfs.arm_nofpu2.img
+
<pre class="host">
 +
$ qemu-system-arm -M versatilepb -kernel ./vmlinuz-2.6.29.6-versatile-armadeus -hda armadeus-qemu.img -m 64 \
 +
                                -append "root=/dev/sda mem=64M ro"      (rw for read/write works, too instead of tw two last characters ro)
 +
</pre>
 +
option ''-cpu arm926'' can be added on APF27 <br>
 +
 
 +
===APF6===
 +
* here we use i.MX6 sabrelite board emulation and APF6 generated kernel. One may modify his APF6 Linux configuration to increase Ramdisk max size if needed (64 Mbytes by default).
 +
<pre clas="host">
 +
$ qemu-system-arm -M sabrelite -smp 4 -m 1G -display none -serial null -serial stdio \
 +
    -kernel buildroot/output/images/zImage \
 +
    -dtb buildroot/output/build/linux-4.19.227/arch/arm/boot/dts/imx6q-sabrelite.dtb \
 +
    -initrd buildroot/output/images/rootfs.ext4 -append "root=/dev/ram"
 +
</pre>
  
 
[[Image:qemu_apf_ramdisk.png]]
 
[[Image:qemu_apf_ramdisk.png]]
  
−
* When system has booted, we will create the "hard disk" image. But first, if you are French, do:
+
===Common tips===
 +
* When system has booted, if you are French, load a usable keymap:
 
<pre class="apf">
 
<pre class="apf">
 
  # loadkmap < /etc/i18n/fr.kmap
 
  # loadkmap < /etc/i18n/fr.kmap
 
</pre>
 
</pre>
−
* then:
+
<pre class="host">
−
<pre class="apf">
+
    =>   loqdk,qp < !etc!i&_n!fr:k,qp    on your PC keyboard
−
# mkdir /tmp/dev
+
−
# mknod /tmp/dev/sda b 8 0
+
−
# mknod /tmp/dev/sda1 b 8 1
+
−
# fdisk /tmp/dev/sda
+
−
   n p 1 <enter> <enter> w
+
−
# mkfs.ext2 /tmp/dev/sda1
+
 
</pre>
 
</pre>
−
* Now we can mount our brand new file system:
+
Another solution is to generate the command one wants to lanch on your PC, with a normal keyboard layout
−
<pre class="apf">
+
 
−
# mkdir /mnt/root
+
<pre class="host">
−
# mount /tmp/dev/sda1 /mnt/root
+
$echo "loadkmap</etc/i18n/fr.kmap" > kfr
 
</pre>
 
</pre>
−
{{Note|Following steps need you already configured [[Communicate | tftp]] on your host and networking up and running}}
 
  
−
* And now we can populate it:
+
or
−
<pre class="apf">
+
<pre class="host">
−
# cd /mnt/root
+
$echo "loadkmap</etc/i18n/de.kmap" > kde
−
# tftp -g -r apf27-rootfs.arm.tar -l rootfs.arm.tar [HOST IP]
+
 
−
# tar -xvf rootfs.arm.tar
+
chmod +x k*
 
</pre>
 
</pre>
  
−
* Finally halt the emulated system and, next boot, we can omit the initrd image:
+
and to copy it on the virtual image, before it is unmounted and qemu is launched
−
  [armadeus]$ qemu-system-arm -m 32 -M versatilepb -kernel vmlinuz-2.6.18-6-versatile \
+
<pre class="host">
−
    -append "root=/dev/sda1" -hda ./apf9328-rootfs.arm_nofpu2.img
+
$cp -uv k* $IMAGE/usr/local/bin/. # it will be in the guest PATH
 +
</pre>
 +
 
 +
Once qemu has been launched, and one is connected, just type kfr (or kde) to get a keyboard layout one is accustomed to (these letters are layout agnostic, and they can be directly executed).
 +
 
 +
A bash script to avoid typing all these lines can be found here, and might make things simpler, if adapted.
 +
[[http://www.armadeus.com/wiki/index.php?title=User:DenisB]]
 +
 
 +
==To Be Continued... ;-) ==
  
 
==Links==
 
==Links==
Line 149: Line 190:
 
* [http://gumstix.net/wiki/index.php?title=Running_qemu Gumstix's way of using QEmu]
 
* [http://gumstix.net/wiki/index.php?title=Running_qemu Gumstix's way of using QEmu]
 
* [http://gumstix.net/wiki/index.php?title=Making_qemu_images Gumstix's way of generating QEmu's images]
 
* [http://gumstix.net/wiki/index.php?title=Making_qemu_images Gumstix's way of generating QEmu's images]
 +
* [https://wiki.ubuntu.com/ARM/RootfsFromScratch Generating Ubuntu for ARM with QEMU]
 +
* [http://balau82.wordpress.com/2010/03/22/compiling-linux-kernel-for-qemu-arm-emulator/ compiling-linux-kernel-for-qemu-arm-emulator]
  
  
 
[[Category:Emulation]]
 
[[Category:Emulation]]

Latest revision as of 12:14, 13 January 2023

Page under construction... Construction.png Informations on this page are not guaranteed !!

Well, you don't have enough money to buy an Armadeus board and just want to be part of the "Software" side of the project ? Then QEMU can be a good choice for you !!

Warning Warning:

Just be aware that currently Armadeus hardware is not emulated under QEMU, we are just using an other board hardware emulation (ARM Versatile) and Linux kernel to launch our rootfs and test our software which is not hardware related (ie User interface, Network, etc...)


In order to build a hardware matching machine for Armadeus boards under Qemu, follow this link and add devices you are interested to see emulated in Qemu: Qemu machine development

Installation

  • on Debian, *Ubuntu just do a:
[armadeus]$ sudo apt-get install qemu bridge-utils vde
  • on Kubuntu 9.10 do:
[armadeus]$ sudo apt-get install qemu bridge-utils qemu-kvm-extras vde
  • on Ubuntu 20.04:
 $ sudo apt-get install qemu qemu-system-arm

Configuration

QEMU has several ways of emulating the network:

  • user mode (by default): you can access Internet from your emulated target or an internal Samba/TFTP server but your are not directly accessible
  • bridge mode: you can communicate directly with the Host


Note Note: For a first try you can skip following part and go directly here.

As we want to mimic the devt environment with a real target (that has its own IP adress and is eccesible from the host) we will use "bridged mode". This mode require some configuration on your Host:

  • Install bridge_utils package
  • Activate IPv4 forwarding, for example on Ubuntu, uncomment the following line in /etc/sysctl.conf:
 $ sudo vim /etc/sysctl.conf
 
   # Uncomment the next line to enable packet forwarding for IPv4
   #net/ipv4/ip_forward=1
  • In /etc/network/interface comment the line referring to your current Ethernet card and replace them with:
auto br0
iface br0 inet dhcp
 bridge_ports eth0
 bridge_fd 9
 bridge_hello 2
 bridge_maxage 12
 bridge_stp off 

#auto eth0
#iface eth0 inet dhcp
Note Note: If you are using a modern linux distribution like Ubuntu, also be sure NetworkManager is disabled/not configured. Otherwise conflict occur and network does not work at all.


  • Create a script /etc/qemu-ifup that will be executed upon the start of QEMU:
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2
  • Now you can append the following options to the qemu command line:
-net nic,vlan=0,macaddr=00:16:3e:00:00:01 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup

You don't need to give a MAC address if you are emulating only one machine, as QEMU will use a default one. However if you have more than one emulated machine (don't forget QEMU can also emulate other architectures than ARM), you will have to specify a unique MAC address for each machine.

  • Once booted, on your guest you can configure the network simply as follows:
 # udhcpc -i eth0

Get/generate simulation images (Linux & rootfs)

APF27 APF6
* As QEMU doesn't support (yet) the APF, we will use the Versatile PB emulated hardware. To get a compatible Linux kernel for this board do: 
$ cd your_armadeus_view/
$ wget ftp://ftp2.armadeus.com/armadeusw/download/qemu/vmlinuz-2.6.29.6-versatile-armadeus

one wanting to rebuild this image itself will find the corresponding config file in the same dir. (after compiling, take arch/arm/boot/zImage)

* As QEMU doesn't support (yet) the APF6, we will use the SabreLite emulated hardware.
  • get some useful environment variables:
 $ make shell_env
 $ source armadeus_env.sh
  • deactivate login on serial port:
    • in Buildroot menuconfig:
System configuration  --->
    () Port to run a getty (login prompt) on
* and in $ARMADEUS_ROOTFS_DIR/etc/inittab, comment following lines:
# Put a getty on the serial port
ttymxcX::respawn:/sbin/getty -L ttymxcX 115200 vt100 # GENERIC_SERIAL

This can be achieved with sed :
sed --in-place -e "s/^ttymcX/#ttymcX/" $ARMADEUS_ROOTFS_DIR/etc/inittab
  • Re-generate your Armadeus rootfs:
 $ make
APF27 APF6
* check the size of your rootfs image 
$ ls -al $ARMADEUS_ROOTFS_TAR
  • generate a dummy image larger than your rootfs; here 60 MBytes for a 45 MBytes tared rootfs:
$ dd if=/dev/zero of=armadeus-qemu.img bs=1MB count=60
$ sudo mke2fs -F -m 0 -b 1024 armadeus-qemu.img
  • mount it and copy it your rootfs:
$ mkdir qemu_mnt
$ sudo mount -t ext2 -o loop armadeus-qemu.img qemu_mnt/
$ sudo tar xf $ARMADEUS_ROOTFS_TAR -C qemu_mnt/
$ sudo umount qemu_mnt/
* APF6 has already EXT4 generated rootfs images
  • now you have all you need to launch Qemu

Launch it

APF9328/27/51/28

  • Example with 64 MBytes of RAM:
$ qemu-system-arm -M versatilepb -kernel ./vmlinuz-2.6.29.6-versatile-armadeus -hda armadeus-qemu.img -m 64 \
                                -append "root=/dev/sda mem=64M ro"       (rw for read/write works, too instead of tw two last characters ro)

option -cpu arm926 can be added on APF27

APF6

  • here we use i.MX6 sabrelite board emulation and APF6 generated kernel. One may modify his APF6 Linux configuration to increase Ramdisk max size if needed (64 Mbytes by default).
$ qemu-system-arm -M sabrelite -smp 4 -m 1G -display none -serial null -serial stdio \
    -kernel buildroot/output/images/zImage \
    -dtb buildroot/output/build/linux-4.19.227/arch/arm/boot/dts/imx6q-sabrelite.dtb \
    -initrd buildroot/output/images/rootfs.ext4 -append "root=/dev/ram"

Qemu apf ramdisk.png

Common tips

  • When system has booted, if you are French, load a usable keymap:
 # loadkmap < /etc/i18n/fr.kmap

    =>    loqdk,qp < !etc!i&_n!fr:k,qp    on your PC keyboard

Another solution is to generate the command one wants to lanch on your PC, with a normal keyboard layout 

$echo "loadkmap</etc/i18n/fr.kmap" > kfr

or 

$echo "loadkmap</etc/i18n/de.kmap" > kde

chmod +x k*

and to copy it on the virtual image, before it is unmounted and qemu is launched 

$cp -uv k* $IMAGE/usr/local/bin/. # it will be in the guest PATH

Once qemu has been launched, and one is connected, just type kfr (or kde) to get a keyboard layout one is accustomed to (these letters are layout agnostic, and they can be directly executed).

A bash script to avoid typing all these lines can be found here, and might make things simpler, if adapted. [[1]]

To Be Continued... ;-)

Links

Retrieved from "http://armadeus.org/wiki/index.php?title=QEMU&oldid=15112"