qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: QEMU-devel Developers <qemu-devel@nongnu.org>
Cc: peter.maydell@linaro.org, Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 00/17] s390x emulation support
Date: Mon, 28 Mar 2011 16:20:04 +0200	[thread overview]
Message-ID: <4D909914.7080108@suse.de> (raw)
In-Reply-To: <1300982333-12802-1-git-send-email-agraf@suse.de>

On 03/24/2011 04:58 PM, Alexander Graf wrote:
> We've had support for running s390x guests with KVM for a
> while now. This patch set also enables support for running
> s390x guests in system as well as linux-user mode in emulation!
>
> Within this scope, I again want to stress that this is _not_
> supposed to replace Hercules - the s390 emulator - in any way.
> The only target supported by qemu is Linux. You can only run
> Linux applications with linux-user emulation and Linux guest OSs
> with the system emulation. All the device logic (and 24 bit mode)
> for running legacy stuff is missing. Use Hercules for those!
>
> I have successfully run the following guest OSs:
>
>    - SUSE Linux Enterprise Server 11 SP1
>    - Debian Lenny
>
> Both of which work just fine on x86_64 and ppc hosts. Other hosts
> should also work. The only thing that did not work for me is network.
> Somehow networking only works with KVM enabled, so there is probably
> some bug involved still.
>
> Either way - rejoice! As with this patch set you can finally fulfill
> your mainframe desires on your local workstation. And - most importantly -
> finally test patches to virtio against s390!
>
> For images, I'm hoping for Aurelien to provide Debian images that run
> in qemu. Other distributions only provide S390x target support in their
> enterprise variants, keeping me from redistributing images :(.
>
> If you're trying to get things rolling yourself, make sure to use a
> recent kernel that has support for the virtio architecture and virtio
> console support - otherwise you won't see output.
>
> The linux user mode emulation part only support 64bit binaries, so
> running Debian binaries with that one is out of question for now. Use
> the system emulation mode if you really need to run Debian binaries.

I forgot the most important piece of information:

   git://repo.or.cz/qemu/agraf.git s390-tcg-v1



Alex

      parent reply	other threads:[~2011-03-28 14:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 15:58 [Qemu-devel] [PATCH 00/17] s390x emulation support Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 01/17] Only build ivshmem when CONFIG_PCI && CONFIG_KVM Alexander Graf
2011-03-24 21:46   ` [Qemu-devel] " Juan Quintela
2011-03-25 11:04     ` Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 02/17] virtio: use generic name when possible Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 03/17] s390x: Enable disassembler for s390x Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 04/17] s390x: Enable nptl " Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 05/17] s390x: enable CPU_QuadU Alexander Graf
2011-03-24 16:52   ` Peter Maydell
2011-03-24 16:54     ` Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 06/17] s390x: s390x-linux-user support Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 07/17] linux-user: define a couple of syscalls for non-uid16 targets Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 08/17] s390x: Enable s390x-softmmu target Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 09/17] s390x: Dispatch interrupts to KVM or the real CPU Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 10/17] s390x: Adjust GDB stub Alexander Graf
2011-03-25 12:07   ` Nathan Froyd
2011-03-25 12:16     ` Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 11/17] s390x: virtio machine storage keys Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 12/17] s390x: Prepare cpu.h for emulation Alexander Graf
2011-03-28 14:54   ` Peter Maydell
2011-03-29 10:14     ` Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 13/17] s390x: helper functions for system emulation Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 14/17] s390x: Implement opcode helpers Alexander Graf
2011-03-24 17:29   ` Peter Maydell
2011-03-24 17:41     ` Richard Henderson
2011-03-24 18:09       ` Alexander Graf
2011-03-24 18:13     ` Alexander Graf
2011-03-28 17:23     ` Alexander Graf
2011-03-28 17:42       ` Richard Henderson
2011-03-28 17:55       ` Peter Maydell
2011-03-29  9:04         ` Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 15/17] s390x: Adjust internal kvm code Alexander Graf
2011-03-24 15:58 ` [Qemu-devel] [PATCH 16/17] s390x: translate engine for s390x CPU Alexander Graf
2011-03-28 15:40   ` Peter Maydell
2011-03-29  8:55     ` Alexander Graf
2011-03-29  9:17       ` Peter Maydell
2011-03-29  9:25         ` Alexander Graf
2011-03-29  9:56           ` Peter Maydell
2011-03-29 10:40             ` Alexander Graf
2011-03-31 10:37       ` Peter Maydell
2011-03-24 15:58 ` [Qemu-devel] [PATCH 17/17] s390x: build s390x by default Alexander Graf
2011-03-28 14:20 ` Alexander Graf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D909914.7080108@suse.de \
    --to=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).