Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!

Difference between revisions of "Testing with QEMU"

From Openembedded.org
Jump to: navigation, search
(good to know)
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
QEMU is great for testing images and apps.  There is no need to flash or install images back and forth on real hardware.  Here are a few things that may help you testing OE stuff with QEMU.
+
QEMU is great for testing images and apps.  There is no need to flash or install images back and forth on real hardware.  Here are a few things that may help you testing OE stuff with QEMU. The qemu machines are available with the qemu prefix, currently qemumips, qemuarm, qemuppc, qemux86 and qemux86-64 are available.
  
= Do's and Dont's =
+
You can boot images within QEMU using the runqemu command. It can boot disk images and also NFS images. NFS support uses the unfs user mode server and does not require root access. Sudo access is required for network device setup but there is a script that can create the tap/tun device in advance removing the need for root privledges.
  
* use at least version 0.9x of qemu, earlier versions are unreliable
+
The qemu targets support automatic testing of images so that they are booted after image creation. Please see local.conf.sample for details on how to enable this.
* if possible use the poky-qemu and poky-scripts, they are more widely tested than stock qemu
+
  
= good to know =
+
= Useful keyboard shortcuts =
  
* [http://www.qemu.org/qemu-doc.html official documentation]
 
 
* Ctrl+Alt+1: guest OS
 
* Ctrl+Alt+1: guest OS
 
* Ctrl+Alt+2: qemu monitor (supports tab-completion, hint: sendkey)
 
* Ctrl+Alt+2: qemu monitor (supports tab-completion, hint: sendkey)
 
* Ctrl+Alt+3: serial console
 
* Ctrl+Alt+3: serial console
 
* Ctrl+Alt+4: parallel console (?)
 
* Ctrl+Alt+4: parallel console (?)
* logfile at ???
 
  
 +
= Other links =
 +
 +
* [http://www.qemu.org/qemu-doc.html official documentation]
 +
* some [http://www.linuxtogo.org/gowiki/AngstromAndQemu more info in the Angstrom wiki]
  
 
[[Category:Machine]]
 
[[Category:Machine]]
[[Category:Dev]]
+
[[Category:FAQ]]
 +
[[Category:User]]

Latest revision as of 14:13, 7 November 2012

QEMU is great for testing images and apps. There is no need to flash or install images back and forth on real hardware. Here are a few things that may help you testing OE stuff with QEMU. The qemu machines are available with the qemu prefix, currently qemumips, qemuarm, qemuppc, qemux86 and qemux86-64 are available.

You can boot images within QEMU using the runqemu command. It can boot disk images and also NFS images. NFS support uses the unfs user mode server and does not require root access. Sudo access is required for network device setup but there is a script that can create the tap/tun device in advance removing the need for root privledges.

The qemu targets support automatic testing of images so that they are booted after image creation. Please see local.conf.sample for details on how to enable this.

[edit] Useful keyboard shortcuts

  • Ctrl+Alt+1: guest OS
  • Ctrl+Alt+2: qemu monitor (supports tab-completion, hint: sendkey)
  • Ctrl+Alt+3: serial console
  • Ctrl+Alt+4: parallel console (?)

[edit] Other links

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox