From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tv90Y-00009v-MS for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:05:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tv90X-0000Pl-9m for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:05:02 -0500 Received: from mail-ob0-f169.google.com ([209.85.214.169]:48183) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tv90X-0000PA-5x for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:05:01 -0500 Received: by mail-ob0-f169.google.com with SMTP id v19so275226obq.28 for ; Tue, 15 Jan 2013 08:05:00 -0800 (PST) Date: Tue, 15 Jan 2013 10:04:57 -0600 From: Rob Landley In-Reply-To: <2EBDEAE4-3119-40B9-897C-1271DBD4F2E1@suse.de> (from agraf@suse.de on Tue Jan 15 05:45:44 2013) Message-Id: <1358265897.32505.29@driftwood> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Qemu s390x emulation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "Suzuki K. Poulose" , qemu-devel@nongnu.org On 01/15/2013 05:45:44 AM, Alexander Graf wrote: >=20 > On 15.01.2013, at 12:39, Suzuki K. Poulose wrote: >=20 > > On 01/15/2013 04:39 PM, Alexander Graf wrote: > >> > >> On 15.01.2013, at 12:05, Suzuki K. Poulose wrote: > >> > >>> Hi > >>> > >>> I have been trying to setup a qemu session for qemu-system-s390x =20 > (on > >>> x86_64) using a kernel (with initramfs built-in the kernel) =20 > without a > >>> disk image. The kernel was built with s390 defconfig + disabled =20 > loadable > >>> modules (just to keep everything inside the kernel). > >>> > >>> $ qemu-system-s390x -M s390 -kernel vmlinux -m 1024 > >>> > >>> > >>> The session dies in say 2 secs, with an exit code of 0. I =20 > searched for > >>> some hints / success stories, couldn't find any. > >>> > >>> Am I doing something wrong here ? Please let me know the right =20 > procedure > >>> for getting this up and running. > >> > >> S390 boots using an "image" file. Please try -kernel dir>/arch/s390/boot/image. > >> > > Tried that even, but not any better. btw, moved to the upstream git =20 > for qemu. > > > > 0 > > $/data/src/qemu/s390x-softmmu/qemu-system-s390x -m 1024 -kernel =20 > ./image -nographic > > $echo $? > > 0 > > $file ./image > > ./image: Linux S390 > > > > $ cd /data/src/qemu/ ; git log | head -n1 > > commit cf7c3f0cb5a7129f57fa9e69d410d6a05031988c >=20 > Does this one work for you? >=20 > http://ftp.nl.debian.org/debian/dists/stable/main/installer-s390/current/= images/generic/kernel.debian I tried grabbing that and grabbing the initrd image in the same =20 directory, booting them with: qemu-system-s390x -kernel kernel.debian -nographic -m 1024 -initrd =20 initrd.debian \ -append "rdinit=3D/bin/ash" And it booted to a shell prompt... with a broken console. When I did =20 "ls -l" at the resulting prompt it echoed back an ANSI escape sequence, =20 one character at a time, which looks like the response to the ansi =20 screen size probe busybox does (to query the display size of an xterm =20 across a virtual serial console). I.E. qemu is getting deeply confused that what comes from stdin and =20 what you type on the keyboard aren't quite the same thing. Some kind of =20 strange ncurses hackage, looks like? I tried sticking "cat |" in front of the above qemu pipeline and it got =20 REALLY confused. Rob=