Testing with QEMU: Difference between revisions
Jump to navigation
Jump to search
m (→good to know: update link to AngstromAndQemu wiki page) |
PaulEggleton (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Outdated}} | |||
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. | ||
Revision as of 16:49, 3 November 2012
| NOTE: This page has been identified as having content that is significantly out-of-date, usually because it refers to OpenEmbedded-Classic - for new projects, you should use OpenEmbedded-Core.
See OpenEmbedded Wiki Update Project for more details. |
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.
Do's and Dont's
- use at least version 0.9x of qemu, earlier versions are unreliable
- if possible use the poky-qemu and poky-scripts, they are more widely tested than stock qemu
good to know
- official documentation
- 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 (?)
- logfile at ???
- some more info in the Angstrom wiki