From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWA8a-0006PG-VN for qemu-devel@nongnu.org; Sun, 30 Aug 2015 17:27:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWA8X-0007FN-Q9 for qemu-devel@nongnu.org; Sun, 30 Aug 2015 17:27:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42785) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWA8X-0007F6-Ky for qemu-devel@nongnu.org; Sun, 30 Aug 2015 17:27:37 -0400 Date: Sun, 30 Aug 2015 22:27:34 +0100 From: "Richard W.M. Jones" Message-ID: <20150830212734.GT29283@redhat.com> References: <20150830201133.GC22921@redhat.com> <66805A56-B304-4C4D-87F5-4F93186CD4CD@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <66805A56-B304-4C4D-87F5-4F93186CD4CD@suse.de> Subject: Re: [Qemu-devel] qemu-system-s390x command line List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "qemu-devel@nongnu.org" 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 : > > > > 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