From: "Richard W.M. Jones" <rjones@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-s390x command line
Date: Sun, 30 Aug 2015 22:27:34 +0100 [thread overview]
Message-ID: <20150830212734.GT29283@redhat.com> (raw)
In-Reply-To: <66805A56-B304-4C4D-87F5-4F93186CD4CD@suse.de>
On Sun, Aug 30, 2015 at 11:02:17PM +0200, Alexander Graf wrote:
>
>
> > Am 30.08.2015 um 22:11 schrieb Richard W.M. Jones <rjones@redhat.com>:
> >
> > Hi Alex,
> >
> > Do you or anyone have a working qemu-system-s390x command line I can
> > use as a starting point to boot a [TCG] guest?
> >
> > So far I have tried variations of:
> >
> > ~/d/qemu/s390x-softmmu/qemu-system-s390x -M s390-ccw-virtio -m 1024 -smp 1 -drive file=s390x.img,if=none,id=disk0 -device virtio-blk-ccw,drive=disk0,id=hd0,bootindex=1 -drive file=Fedora-Server-DVD-s390x-22.iso
>
> Ok, 2 problems here. I'm not sure the iso is bootable - you are
> definitely best off to just use -kernel until you have sonething
> working and then move on to booting without. CD boot is something
> real mainframes don't do very often, so it's a pretty unmaintained
> code path in installation media.
>
> The other one is that we emulate most fancy new user level
> instructions of an ec12, but we only advertise ourselves as a z9 to
> the kernel. So you need to make sure that your kernel is compiled
> with support for old CPUs (RHEL7 for example is not).
Thanks Alex. Stripping this back to the basics:
~/d/qemu/s390x-softmmu/qemu-system-s390x -M s390-ccw-virtio -m 1024 -smp 1 -kernel kernel.img
with the kernel.img downloaded from
http://mirrors.nic.cz/fedora-secondary/releases/22/Server/s390x/os/images/
just opens a window for a fraction of a second and then qemu exits.
I'm not married to that particular kernel, nor even to Fedora. I just
want to get something that works as a starting point. Is there a SUSE
or Debian kernel which boots?
> Once you get past these points, things should be very
> self-explanatory. Oh - and -kernel is 0 overhead on s390x, unlike
> x86.
Heh heh :-)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2015-08-30 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 20:11 [Qemu-devel] qemu-system-s390x command line Richard W.M. Jones
2015-08-30 21:02 ` Alexander Graf
2015-08-30 21:27 ` Richard W.M. Jones [this message]
2015-08-30 21:33 ` Alexander Graf
2015-08-31 17:09 ` Thomas Huth
2015-08-31 17:50 ` Richard W.M. Jones
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=20150830212734.GT29283@redhat.com \
--to=rjones@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
/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).