Skip to contentSkip to conversation

host-qemu-system

RFC PATCH New Gustavo Zacarias 5 participants 13 messages Dec 4, 2013 – Dec 9, 2013 Arm/versatile express platform

lore
Share & tools
lore
#0 lore raw

cover host-qemu-system

This patchset provides a new host-qemu-system package intended to solve the problematic "which qemu version works with this config?" dilemma.

Quick test would be a simple "make qemu_xxx_defconfig" with a "make qemu-system-run" - everything should be silk smooth for the user.

TODO:
* Update documentation/readme.txt files to reflect varying alternatives. host-qemu-system is built with the basics provided by buildroot, hence only the basic text & curses interfaces are guaranteed to work.
But if the host provides headers for SDL or other graphic toolkits these can be detected and picked up by the build thus giving alternative rendering methods for the user to use (to emulate a framebuffer for example).
* Cleanup my hacky qemu autotesting script and submit it if there's interest.

Gustavo Zacarias (2):
qemu-system: new host package configs/qemu: update for host-qemu-system goodness

 board/qemu/arm-nuri/readme.txt             |  2 +-
 board/qemu/arm-versatile/readme.txt        |  2 +-
 board/qemu/arm-vexpress/readme.txt         |  2 +-
 board/qemu/microblazebe-mmu/readme.txt     |  2 +-
 board/qemu/microblazeel-mmu/readme.txt     |  2 +-
 board/qemu/mips-malta/readme.txt           |  2 +-
 board/qemu/mips64-malta/readme.txt         |  2 +-
 board/qemu/mips64el-malta/readme.txt       |  2 +-
 board/qemu/mipsel-malta/readme.txt         |  2 +-
 board/qemu/powerpc-g3beige/readme.txt      |  2 +-
 board/qemu/powerpc-mpc8544ds/readme.txt    |  2 +-
 board/qemu/powerpc-virtex-ml507/readme.txt |  2 +-
 board/qemu/sh4-r2d/readme.txt              |  2 +-
 board/qemu/sparc-ss10/readme.txt           |  2 +-
 board/qemu/x86/readme.txt                  |  2 +-
 board/qemu/x86_64/readme.txt               |  2 +-
 configs/qemu_arm_nuri_defconfig            |  4 ++
 configs/qemu_arm_versatile_defconfig       |  4 ++
 configs/qemu_arm_vexpress_defconfig        |  4 ++
 configs/qemu_microblazebe_mmu_defconfig    |  4 ++
 configs/qemu_microblazeel_mmu_defconfig    |  4 ++
 configs/qemu_mips64_malta_defconfig        |  4 ++
 configs/qemu_mips64el_malta_defconfig      |  4 ++
 configs/qemu_mips_malta_defconfig          |  4 ++
 configs/qemu_mipsel_malta_defconfig        |  4 ++
 configs/qemu_ppc_g3beige_defconfig         |  4 ++
 configs/qemu_ppc_mpc8544ds_defconfig       |  4 ++
 configs/qemu_ppc_virtex_ml507_defconfig    |  4 ++
 configs/qemu_sh4_r2d_defconfig             |  4 ++
 configs/qemu_sparc_ss10_defconfig          |  5 +++
 configs/qemu_x86_64_defconfig              |  4 ++
 configs/qemu_x86_defconfig                 |  4 ++
 package/Config.in.host                     |  1 +
 package/qemu-system/Config.in.host         | 30 ++++++++++++++
 package/qemu-system/qemu-system.mk         | 64 ++++++++++++++++++++++++++++++
 35 files changed, 176 insertions(+), 16 deletions(-)
 create mode 100644 package/qemu-system/Config.in.host
 create mode 100644 package/qemu-system/qemu-system.mk
Signature · 1 line
1.8.3.2
#1 lore raw

PATCH 1/2 qemu-system: new host package

---
 package/Config.in.host             |  1 +
 package/qemu-system/Config.in.host | 30 ++++++++++++++++++
 package/qemu-system/qemu-system.mk | 64 ++++++++++++++++++++++++++++++++++++++
 3 files changed, 95 insertions(+)
 create mode 100644 package/qemu-system/Config.in.host
 create mode 100644 package/qemu-system/qemu-system.mk
package/Config.in.host +1 -0
index 5fd2570..0f69402 100644
@@ -10,6 +10,7 @@ source "package/lpc3250loader/Config.in.host"
 source "package/mtools/Config.in.host"
 source "package/omap-u-boot-utils/Config.in.host"
 source "package/openocd/Config.in.host"
+source "package/qemu-system/Config.in.host"
 source "package/sam-ba/Config.in.host"
 source "package/sunxi-tools/Config.in.host"
 source "package/uboot-tools/Config.in.host"
package/qemu-system/Config.in.host new file +30 -0
new file mode 100644
index 0000000..16d1a11
@@ -0,0 +1,30 @@
+config BR2_PACKAGE_HOST_QEMU_SYSTEM
+	bool "host qemu-system"
+	# Supported system target architectures
+	depends on BR2_arm || BR2_i386 || BR2_microblaze || BR2_mips \
+		|| BR2_mips64 || BR2_mips64el || BR2_mipsel || BR2_powerpc \
+		|| BR2_sh4 || BR2_sh4eb || BR2_sparc || BR2_x86_64
+	help
+	  QEMU is a generic and open source machine emulator and virtualizer.
+
+	  This option builds a system emulator for your selected architecture.
+
+	  http://www.qemu.org
+
+if BR2_PACKAGE_HOST_QEMU_SYSTEM
+
+config BR2_PACKAGE_HOST_QEMU_SYSTEM_VERSION
+	string "qemu version"
+	default "1.7.0"
+	help
+	  QEMU version to use.
+	  Sometimes the latest version is broken for some specific
+	  architecture or target machine.
+
+config BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS
+	string "qemu-system command arguments"
+	help
+	  Arguments to be used for your target host-qemu-system to run
+	  via "make qemu-system-run".
+
+endif
package/qemu-system/qemu-system.mk new file +64 -0

64 lines not on this page · raw message

Signature · 1 line
1.8.3.2
#2 lore raw

PATCH 1/2 qemu-system: new host package

Dear Gustavo Zacarias,

Quoted 8 lines · Gustavo Zacarias
---
 package/Config.in.host             |  1 +
 package/qemu-system/Config.in.host | 30 ++++++++++++++++++
 package/qemu-system/qemu-system.mk | 64 ++++++++++++++++++++++++++++++++++++++
 3 files changed, 95 insertions(+)
 create mode 100644 package/qemu-system/Config.in.host
 create mode 100644 package/qemu-system/qemu-system.mk

The first question that comes to mind is why we have a separate "qemu-system" package for this, instead of improving the existing "qemu" package, which already builds Qemu for the host, but only builds the user emulation mode?

Best regards,

Thomas Petazzoni

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#3 lore raw

PATCH 1/2 qemu-system: new host package

Quoted 4 lines · Thomas Petazzoni

The first question that comes to mind is why we have a separate "qemu-system" package for this, instead of improving the existing "qemu" package, which already builds Qemu for the host, but only builds the user emulation mode?

Version freedom to begin with, for the system emulation you sometimes need a special version (example: sparc won't work with 1.7.0) that might not be the latest. You might also want this freedom for user emulation, but then nobody guarantees you'll match system for a given architecture. Then i also don't know what to do with the user variant, if it's going to be used for anything or what (it's an orphan now) - maybe killing user is an option and replace it by system?
Regards.

#4 lore raw

PATCH 1/2 qemu-system: new host package

Dear Gustavo Zacarias,

Quoted 7 lines · Gustavo Zacarias

Version freedom to begin with, for the system emulation you sometimes need a special version (example: sparc won't work with 1.7.0) that might not be the latest. You might also want this freedom for user emulation, but then nobody guarantees you'll match system for a given architecture. Then i also don't know what to do with the user variant, if it's going to be used for anything or what (it's an orphan now) - maybe killing user is an option and replace it by system?

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

And even if we want to keep the user mode emulation, I think there should be one single package. Nothing prevents from having sub-options to enable either the user mode or system mode emulation, or both, or to have a version selection.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#5 lore raw

PATCH 1/2 qemu-system: new host package

Quoted 9 lines · Thomas Petazzoni

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

And even if we want to keep the user mode emulation, I think there should be one single package. Nothing prevents from having sub-options to enable either the user mode or system mode emulation, or both, or to have a version selection.

A single package prevents different versions of -user and -system (at least in a nice way).
Sometimes the latest version of qemu doesn't play nice with some kernel versions because of newer OpenBIOS/other BIOSes versions breaking with newer kernels - it's a common scenario for non-x86/x86_64.
And there may be some particular need for -user to be a newer or different version than system, though i can't come up with any idea of why. At the moment i don't think -user is useful for anything in particular because of the limitations you wrote.
Problem is building two different versions in a single package wouldn't be all that great, for all intents and purposes they would be two packages anyway.
Regards.

#6 lore raw

PATCH 1/2 qemu-system: new host package

Quoted 6 lines · Gustavo Zacarias
Quoted 4 lines · Thomas Petazzoni

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

It's not possible to do it in Config.in, but it's easy to do during the
build: compare /usr/include/linux/version.h with $(STAGING_DIR)/usr/include/linux/version.h

Or am I missing something? I admit, it assumes that the distro installs
kernel headers corresponding to the running kernel (but a distro that doesn't do that is pretty broken), and it assumes that you'll run qemu on the build machine.

Quoted 7 lines
Quoted 4 lines

And even if we want to keep the user mode emulation, I think there should be one single package. Nothing prevents from having sub-options to enable either the user mode or system mode emulation, or both, or to have a version selection.

A single package prevents different versions of -user and -system (at least in a nice way).

We do it for gcc, binutils, ... and it doesn't look that ugly to me.
It's mostly the Config.in part that looks ugly.

Quoted 10 lines

Sometimes the latest version of qemu doesn't play nice with some kernel versions because of newer OpenBIOS/other BIOSes versions breaking with newer kernels - it's a common scenario for non-x86/x86_64.
And there may be some particular need for -user to be a newer or different version than system, though i can't come up with any idea of why. At the moment i don't think -user is useful for anything in particular because of the limitations you wrote.
Problem is building two different versions in a single package wouldn't be all that great, for all intents and purposes they would be two packages anyway.

The two packages would be 90% identical (except for needless
divergences, like one using generic-package and the other using autotools-package). So I don't agree they would be two packages. The host and the target build of e.g. python differ more than these two.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#7 lore raw

PATCH 1/2 qemu-system: new host package

Dear Arnout Vandecappelle,

Quoted 8 lines · Arnout Vandecappelle
Quoted 4 lines
Quoted 4 lines

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

It's not possible to do it in Config.in, but it's easy to do during the
build: compare /usr/include/linux/version.h with $(STAGING_DIR)/usr/include/linux/version.h

And then you fail the build if $(STAGING_DIR)/usr/include/linux/version.h gives a newer version of /usr/include/linux/version.h ? Could be possible, even if not really nice. But Fran?ois is proposing to remove cpanminus, which was the only reason to have qemu-user support. So do we care?

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#8 lore raw

PATCH 1/2 qemu-system: new host package

Quoted 13 lines · Thomas Petazzoni

Dear Arnout Vandecappelle,

Quoted 8 lines · Arnout Vandecappelle
Quoted 4 lines
Quoted 4 lines

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

It's not possible to do it in Config.in, but it's easy to do during the
build: compare /usr/include/linux/version.h with $(STAGING_DIR)/usr/include/linux/version.h

Quoted 5 lines

And then you fail the build if $(STAGING_DIR)/usr/include/linux/version.h gives a newer version of /usr/include/linux/version.h ? Could be possible, even if not really nice. But Fran?ois is proposing to remove cpanminus, which was the only reason to have qemu-user support. So do we care?

I care a little (for as much as that counts), but not enough to argue for keeping it if it is becoming a pain. We use qemu-user in a post-build step to run a battery of regression tests on algorithmic code. It has been convenient since the regression test data is too large to run in one pass on the target hardware. It's also faster to run on our PCs. I don't think that the regression tests exercise any of the issues above.

Frank

#9 lore raw

PATCH 1/2 qemu-system: new host package

Quoted 21 lines · Frank Hunleth
Quoted 13 lines · Thomas Petazzoni

Dear Arnout Vandecappelle,

Quoted 8 lines · Arnout Vandecappelle
Quoted 4 lines
Quoted 4 lines

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

It's not possible to do it in Config.in, but it's easy to do during the
build: compare /usr/include/linux/version.h with $(STAGING_DIR)/usr/include/linux/version.h

Quoted 5 lines

And then you fail the build if $(STAGING_DIR)/usr/include/linux/version.h gives a newer version of /usr/include/linux/version.h ? Could be possible, even if not really nice. But Fran?ois is proposing to remove cpanminus, which was the only reason to have qemu-user support. So do we care?

Quoted 7 lines

I care a little (for as much as that counts), but not enough to argue for keeping it if it is becoming a pain. We use qemu-user in a post-build step to run a battery of regression tests on algorithmic code. It has been convenient since the regression test data is too large to run in one pass on the target hardware. It's also faster to run on our PCs. I don't think that the regression tests exercise any of the issues above.

That seems to me like a valuable use case. But you would need a
Config.in.host for it so it actually becomes visible, right? Care to contribute that?

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#10 lore raw

PATCH 1/2 qemu-system: new host package

Hi Arnout,

Quoted 10 lines · Arnout Vandecappelle
Quoted 7 lines · Frank Hunleth

I care a little (for as much as that counts), but not enough to argue for keeping it if it is becoming a pain. We use qemu-user in a post-build step to run a battery of regression tests on algorithmic code. It has been convenient since the regression test data is too large to run in one pass on the target hardware. It's also faster to run on our PCs. I don't think that the regression tests exercise any of the issues above.

Quoted 3 lines

That seems to me like a valuable use case. But you would need a
Config.in.host for it so it actually becomes visible, right? Care to contribute that?

You're right. I had completely forgotten that I had made that change for that project. I'll submit the patch that I'm using shortly.

Also, I'll need some help on any caveats that are desired. I see the caveat in cpanminus, but submitting a patch that depends on BR2_BROKEN feels wrong.

Frank

#11 lore raw

[Buildroot] [UNSURE]Re: [PATCH 1/2] qemu-system: new host package

In reply to Arnout Vandecappelle

2013/12/6 Arnout Vandecappelle <[email protected]>:

Quoted 37 lines · Frank Hunleth
Quoted 27 lines
Quoted 17 lines · Thomas Petazzoni

Dear Arnout Vandecappelle,

Quoted 10 lines · Arnout Vandecappelle
Quoted 4 lines
Quoted 4 lines

Yes, I agree, the user mode emulation should probably be removed. It simply cannot work properly, because we have no way of guaranteeing that the kernel headers used for the target toolchain are older than the kernel running on the system.

It's not possible to do it in Config.in, but it's easy to do during
the
build: compare /usr/include/linux/version.h with $(STAGING_DIR)/usr/include/linux/version.h

Quoted 5 lines

And then you fail the build if $(STAGING_DIR)/usr/include/linux/version.h gives a newer version of /usr/include/linux/version.h ? Could be possible, even if not really nice. But Fran?ois is proposing to remove cpanminus, which was the only reason to have qemu-user support. So do we care?

Quoted 7 lines

I care a little (for as much as that counts), but not enough to argue for keeping it if it is becoming a pain. We use qemu-user in a post-build step to run a battery of regression tests on algorithmic code. It has been convenient since the regression test data is too large to run in one pass on the target hardware. It's also faster to run on our PCs. I don't think that the regression tests exercise any of the issues above.

Quoted 4 lines

That seems to me like a valuable use case. But you would need a
Config.in.host for it so it actually becomes visible, right? Care to contribute that?

I did it with http://patchwork.ozlabs.org/patch/293643/

Fran?ois

Quoted 16 lines

Regards,
Arnout

--

Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

#12 lore raw

PATCH 2/2 configs/qemu: update for host-qemu-system goodness

In reply to Gustavo Zacarias
---
 board/qemu/arm-nuri/readme.txt             | 2 +-
 board/qemu/arm-versatile/readme.txt        | 2 +-
 board/qemu/arm-vexpress/readme.txt         | 2 +-
 board/qemu/microblazebe-mmu/readme.txt     | 2 +-
 board/qemu/microblazeel-mmu/readme.txt     | 2 +-
 board/qemu/mips-malta/readme.txt           | 2 +-
 board/qemu/mips64-malta/readme.txt         | 2 +-
 board/qemu/mips64el-malta/readme.txt       | 2 +-
 board/qemu/mipsel-malta/readme.txt         | 2 +-
 board/qemu/powerpc-g3beige/readme.txt      | 2 +-
 board/qemu/powerpc-mpc8544ds/readme.txt    | 2 +-
 board/qemu/powerpc-virtex-ml507/readme.txt | 2 +-
 board/qemu/sh4-r2d/readme.txt              | 2 +-
 board/qemu/sparc-ss10/readme.txt           | 2 +-
 board/qemu/x86/readme.txt                  | 2 +-
 board/qemu/x86_64/readme.txt               | 2 +-
 configs/qemu_arm_nuri_defconfig            | 4 ++++
 configs/qemu_arm_versatile_defconfig       | 4 ++++
 configs/qemu_arm_vexpress_defconfig        | 4 ++++
 configs/qemu_microblazebe_mmu_defconfig    | 4 ++++
 configs/qemu_microblazeel_mmu_defconfig    | 4 ++++
 configs/qemu_mips64_malta_defconfig        | 4 ++++
 configs/qemu_mips64el_malta_defconfig      | 4 ++++
 configs/qemu_mips_malta_defconfig          | 4 ++++
 configs/qemu_mipsel_malta_defconfig        | 4 ++++
 configs/qemu_ppc_g3beige_defconfig         | 4 ++++
 configs/qemu_ppc_mpc8544ds_defconfig       | 4 ++++
 configs/qemu_ppc_virtex_ml507_defconfig    | 4 ++++
 configs/qemu_sh4_r2d_defconfig             | 4 ++++
 configs/qemu_sparc_ss10_defconfig          | 5 +++++
 configs/qemu_x86_64_defconfig              | 4 ++++
 configs/qemu_x86_defconfig                 | 4 ++++
 32 files changed, 81 insertions(+), 16 deletions(-)
board/qemu/arm-nuri/readme.txt +1 -1
index 6fdba81..0cf8d0b 100644
@@ -7,4 +7,4 @@ graphical window is the framebuffer.
 
 Startup time is slow because of the SMP CPU emulation so be patient.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/arm-versatile/readme.txt +1 -1
index 7d0745f..2c02e26 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/arm-vexpress/readme.txt +1 -1
index 9a4694d..50dd563 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/microblazebe-mmu/readme.txt +1 -1
index 8ade434..3c7e10c 100644
@@ -4,4 +4,4 @@ Run the emulation with:
 
 The login prompt will appear in the terminal that started Qemu.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/microblazeel-mmu/readme.txt +1 -1
index 9ac55db..d402d13 100644
@@ -4,4 +4,4 @@ Run the emulation with:
 
 The login prompt will appear in the terminal that started Qemu.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/mips-malta/readme.txt +1 -1
index b367927..719a624 100644
@@ -6,4 +6,4 @@ The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer. No keyboard support has been
 enabled.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/mips64-malta/readme.txt +1 -1
index 7999b78..3ce3c62 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/mips64el-malta/readme.txt +1 -1
index dba33d3..48bae37 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/mipsel-malta/readme.txt +1 -1
index b77cc84..dd290c4 100644
@@ -6,4 +6,4 @@ The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer. No keyboard support has been
 enabled.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/powerpc-g3beige/readme.txt +1 -1
index 07cb660..2711350 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu. The
 graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/powerpc-mpc8544ds/readme.txt +1 -1
index cd56ddd..27b3bee 100644
@@ -4,4 +4,4 @@ Run the emulation with:
 
 The login prompt will appear in the terminal that started Qemu.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/powerpc-virtex-ml507/readme.txt +1 -1
index a9a6378..0547987 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 
 The login prompt will appear in the terminal that started Qemu.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/sh4-r2d/readme.txt +1 -1
index 2a963eb..73dce14 100644
@@ -5,4 +5,4 @@ Run the emulation with:
 The login prompt will appear in the terminal that started Qemu.
 The graphical window is the framebuffer.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/sparc-ss10/readme.txt +1 -1
index 725ab30..a126a55 100644
@@ -1,6 +1,6 @@
 Run the emulation with:
 
-  qemu-system-sparc -M SS-10 -kernel output/images/zImage -drive file=output/images/rootfs.ext2 -append "root=/dev/sda console=ttyS0,115200" -serial stdio -net nic,model=lance -net user
+  qemu-system-sparc -M SS-10 -kernel output/images/zImage -drive file=output/images/rootfs.ext2 -append "root=/dev/sda console=ttyS0,115200" -serial stdio -net nic,model=lance -net user -display none
 
 The login prompt will appear in the terminal that started Qemu.
 The graphical window is the framebuffer.
board/qemu/x86/readme.txt +1 -1
index c07000c..c821255 100644
@@ -4,4 +4,4 @@ Run the emulation with:
 
 The login prompt will appear in the graphical window.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
board/qemu/x86_64/readme.txt +1 -1
index 3c344f9..f350d36 100644
@@ -4,4 +4,4 @@ Run the emulation with:
 
 The login prompt will appear in the graphical window.
 
-Tested with QEMU 1.6.1
+Tested with QEMU 1.7.0
configs/qemu_arm_nuri_defconfig +4 -0
index 8cb1153..a8bacde 100644
@@ -23,3 +23,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.10.21"
 BR2_LINUX_KERNEL_DEFCONFIG="exynos4"
 BR2_LINUX_KERNEL_ZIMAGE=y
+
+# Qemu-system
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M nuri -kernel output/images/zImage -append 'console=ttySAC1,115200' -smp 2 -serial null -serial stdio -display none"
configs/qemu_arm_versatile_defconfig +4 -0
index a26054d..956ba6d 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.11.10"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/arm-versatile/linux-3.11.config"
 BR2_LINUX_KERNEL_ZIMAGE=y
+
+# Qemu-system
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M versatilepb -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=scsi -append 'root=/dev/sda console=ttyAMA0,115200' -serial stdio -net nic,model=smc91c111 -net user -display none"
configs/qemu_arm_vexpress_defconfig +4 -0
index 4a4db1b..fc0c012 100644
@@ -23,3 +23,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.12.2"
 BR2_LINUX_KERNEL_DEFCONFIG="vexpress"
 BR2_LINUX_KERNEL_ZIMAGE=y
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M vexpress-a9 -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=sd -append 'console=ttyAMA0,115200 root=/dev/mmcblk0' -serial stdio -net nic,model=lan9118 -net user -display none"
configs/qemu_microblazebe_mmu_defconfig +4 -0
index c090143..8fb6f54 100644
@@ -25,3 +25,7 @@ BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/microblazebe-mmu/linux-3.12.conf
 BR2_LINUX_KERNEL_LINUX_BIN=y
 BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
 BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/qemu/microblazebe-mmu/system.dts"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M petalogix-s3adsp1800 -kernel output/images/linux.bin -serial stdio -display none"
configs/qemu_microblazeel_mmu_defconfig +4 -0
index 7538d3f..ccf776f 100644
@@ -25,3 +25,7 @@ BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/microblazeel-mmu/linux-3.12.conf
 BR2_LINUX_KERNEL_LINUX_BIN=y
 BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
 BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/qemu/microblazeel-mmu/system.dts"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M petalogix-s3adsp1800 -kernel output/images/linux.bin -serial stdio -display none"
configs/qemu_mips64_malta_defconfig +4 -0
index 2461325..4e840ab 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M malta -kernel output/images/vmlinux -serial stdio -hda output/images/rootfs.ext2 -append 'root=/dev/hda' -display none"
configs/qemu_mips64el_malta_defconfig +4 -0
index 0d780f4..317aec7 100644
@@ -24,3 +24,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M malta -kernel output/images/vmlinux -serial stdio -hda output/images/rootfs.ext2 -append 'root=/dev/hda' -display none"
configs/qemu_mips_malta_defconfig +4 -0
index bc1edd6..62160d4 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M malta -kernel output/images/vmlinux -serial stdio -hda output/images/rootfs.ext2 -append 'root=/dev/hda' -net nic,model=pcnet -net user -display none"
configs/qemu_mipsel_malta_defconfig +4 -0
index c654351..5bb4d15 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M malta -kernel output/images/vmlinux -serial stdio -hda output/images/rootfs.ext2 -append 'root=/dev/hda' -net nic,model=pcnet -net user -display none"
configs/qemu_ppc_g3beige_defconfig +4 -0
index a6ced5e..15a624f 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M g3beige -kernel output/images/vmlinux -hda output/images/rootfs.ext2 -append 'console=ttyS0 root=/dev/hda' -serial stdio -net nic,model=rtl8139 -net user -display none"
configs/qemu_ppc_mpc8544ds_defconfig +4 -0
index 745a3ca..812b589 100644
@@ -20,3 +20,7 @@ BR2_LINUX_KERNEL_VMLINUX=y
 # Serial port config
 BR2_TARGET_GENERIC_GETTY=y
 BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M mpc8544ds -kernel output/images/vmlinux -serial stdio -net nic,model=e1000 -net user -display none"
configs/qemu_ppc_virtex_ml507_defconfig +4 -0
index f79feb5..3787dd6 100644
@@ -21,3 +21,7 @@ BR2_LINUX_KERNEL_DEFCONFIG="44x/virtex5"
 BR2_LINUX_KERNEL_VMLINUX=y
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="virtex440-ml507"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M virtex-ml507 -kernel output/images/vmlinux -m 256 -append 'console=ttyS0' -display none"
configs/qemu_sh4_r2d_defconfig +4 -0
index bcd50dd..17f9b17 100644
@@ -25,3 +25,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.2.53"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/sh4-r2d/linux-3.2.config"
 BR2_LINUX_KERNEL_ZIMAGE=y
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M r2d -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=ide -append 'root=/dev/sda console=ttySC1,115200 noiotrap' -serial null -serial stdio -net nic,model=rtl8139 -net user -display none"
configs/qemu_sparc_ss10_defconfig +5 -0
index 82f5485..3c6aab7 100644
@@ -16,3 +16,8 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.12.2"
 BR2_LINUX_KERNEL_DEFCONFIG="sparc32"
 BR2_LINUX_KERNEL_ZIMAGE=y
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_VERSION="1.6.1"
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M SS-10 -kernel output/images/zImage -drive file=output/images/rootfs.ext2 -append 'root=/dev/sda console=ttyS0,115200' -serial stdio -net nic,model=lance -net user -display none"
configs/qemu_x86_64_defconfig +4 -0
index 811f968..96afc7d 100644
@@ -19,3 +19,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.12.2"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86_64/linux-3.12.config"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=ide -append 'root=/dev/sda' -net nic,model=rtl8139 -net user -display curses"
configs/qemu_x86_defconfig +4 -0
index d642c45..7e5410d 100644
@@ -20,3 +20,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.12.2"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86/linux-3.12.config"
+
+# Qemu
+BR2_PACKAGE_HOST_QEMU_SYSTEM=y
+BR2_PACKAGE_HOST_QEMU_SYSTEM_ARGS="-M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=ide -append 'root=/dev/sda' -net nic,model=rtl8139 -net user -display curses"
Signature · 1 line
1.8.3.2