SDK/Docs/1.1/Configuring QEMU runtimes

Revision as of 18:17, 22 November 2010

QEMU is a component of the MeeGo SDK. It can run handset or netbook images under an emulator, so you can test your applications on a MeeGo operating system, even if you don't have a MeeGo device.

If you haven't already installed the SDK, see:

• Installing the SDK on Linux

For QEMU, it is important to check your graphics capability. See this page about graphics acceleration for details. Please read this page carefully and follow the instructions on it if you are having issues starting runtimes under QEMU.

It is also possible to build and install QEMU manually: see the QEMU tools page for details.

The best and simplest way to use a MeeGo OS image with QEMU is to use mad-admin to download a runtime, and mad to run it. See the instructions below for how to do this.

Install a MeeGo Runtime

You can get a list of available runtimes for your version of MADDE with:

$ mad-admin list runtimes
qemu-n900-pr12                                              (installable)
rx48-diablo                                                 (installable)
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime       (installable)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime       (installable)

Run the command below. Replace <runtime> with one of

• meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime: Run the MeeGo OS with handset UI.
• meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime: Run the MeeGo OS with netbook UI.

$ sudo mad-admin create -f -e <runtime>

This will download the runtime (a ~650+ MB .bz2 file) into MADDE's cache directory and decompress it in the runtimes directory. On Linux, the default MADDE location is /usr/lib/madde/linux-i686/. If network/proxy issues prevent the image from downloading, the url for the runtime can be extracted from the MADDE's cache/madde.conf.d/<runtime>.conf file, downloaded manually, and copied into the cache directory. Rerunning the above command will now bypass the download and directly decompress the runtime.

After installing, you can check that the runtime is installed by running mad-admin list again.

$ mad-admin list runtimes
qemu-n900-pr12                                              (installable)
rx48-diablo                                                 (installable)
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime       (installed)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime       (installable)

Note that installed above indicates that the handset runtime was successfully downloaded and configured for QEMU.

Using a runtime

To start an installed runtime, use the mad command to boot the image inside QEMU.

To start the IA32 handset runtime:

$ mad remote -r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron

If nothing is happening make sure that the qemu-kvm package is installed (ubuntu).

Here's what the handset image looks like (this is the Applications zone):

To start the IA32 netbook runtime:

$ mad remote -r meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime poweron

Here's what the netbook image looks like (this is Myzone):

You can now use this running image as a deployment target for Qt Creator, or log into it manually over SSH (see below).

When you've finished, use the power off icon in the emulator to switch it off (if available); or from the command line, do:

$ mad remote -r meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime poweroff

Using a runtime without graphics

If you are having issues with running QEMU, you can try running the image without graphics to help isolate the problem. To do this, set QEMU_NOGRAPHIC=yes in the environment before running the emulator. For example:

$ QEMU_NOGRAPHIC=yes mad remote -r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron

If you are then able to ssh into the running image, you can be fairly certain that your issues are graphics-related, rather than anything to do with the image itself.

SSH into QEMU Image

Any time MeeGo is running in QEMU, you can use SSH to connect to the image from a command-line terminal on the host system.

When MADDE starts QEMU, it sets up a redirect from port 6666 on the host to the SSH port (port 22) on the guest (MeeGo on QEMU). So you can log into the running QEMU image with:

$ ssh meego@127.0.0.1 -p 6666

Two user accounts are available:

1. User: meego, password: meego
2. User: root, password: meego

Configuring access to an emulated device in Qt Creator

To configure access to an emulated device:

1. Open Tools > Options > Projects > MeeGo Device Configurations.
2. In the dialog box, create a new Device Configuration by clicking on Add.
3. Give the new Device Configuration a name in the Configuration Name text field, and add the following settings in the other test fields:
   • Device type: choose MeeGo emulator
   • Authentication type: Password
   • Host name: 127.0.0.1
   • Ports, SSH: 6666

     Note that the emulator is setup with a redirect from port 6666 on localhost to the SSH port (22) of the emulated device.

   • Ports, Gdb Server: 13219 (the default)

   Note: If this port is not free, you can select another one.

   • Connection Timeout: 30
   • User Name: root
   • Password: meego
4. Click Apply.
5. To test the settings, ensure that the emulated device is running, then click Test.

   If successful, you'll see a dialog box with the message "Device configuration successful".

   If the message "Could not connect to host" is displayed, check your setting selections and make sure that the network is connected.

6. Click Close and OK.