Differences between revisions 5 and 7 (spanning 2 versions)
Revision 5 as of 2006-02-16 23:07:43
Size: 1754
Editor: ?DavideViti
Comment: Initial version.
Revision 7 as of 2006-02-16 23:22:21
Size: 1690
Editor: ?DavideViti
Comment: Removed "eject" command. I remember using "change" to do that
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
= Intro =
Line 24: Line 24:
= Basic setup =
Line 36: Line 37:
$ qemu -cdrom mini.iso -hda hd_image.img -boot d $ qemu -user-net -cdrom mini.iso -hda hd_image.img -boot d
Line 39: Line 40:
= Qemu monitor =
Line 45: Line 46:

 * "eject" is useful when you want to (virtually) change disk
  (for example you want to use another iso image)


[http://fabrice.bellard.free.fr/qemu/ Official page]

#qemu IRC channel on irc.freenode.net


Qemu can be used to simulate various hardware configurations and to easily test the debian installer in various conditions; it's great for testing "delicate" things like a partitioner, since disk devices are usually represented by files.

It can be used also to emulate other architectures: I tested amd64 and powerpc versions on the installer on my i386 host machine. At the moment (qemu-0.8.0) sparc and ARM are being worked on and have some basic support.

Here some possible d-i boot configurations:

  • floppy installs
  • installs from USB (??)
  • lowmem installs

Basic setup

First of all, you need to create a file which will acts as an hard disk for the virtual machine:

$ qemu-img create hd_img.img 500M

You can then download an iso image of the installer, or create one yourself; you can then run a g-i session by running the following command:

$ qemu -user-net -cdrom mini.iso -hda hd_image.img -boot d

Qemu monitor

Qemu has a "monitor" (ctrl-alt-2) which can be used to access various funcionalities such as:

  • "screendump" which can be used to take a screenshot of
    • the VM screen
  • "sendkey" is very useful when you want to switch to VT2 during
    • a g-i vession ("sendkey ctrl-alt-f2)
  • "gdbserver" is useful for attaching gdb to a process running inside
    • the VM
  • "loadmem/savemem" used to save/restore the state of the VM, saves you alot
    • of time when you have performed all the steps needed to reproduce a bug