qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Alexander Graf <agraf@suse.de>
Cc: "Suzuki K. Poulose" <suzuki@in.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu s390x emulation
Date: Tue, 15 Jan 2013 10:04:57 -0600	[thread overview]
Message-ID: <1358265897.32505.29@driftwood> (raw)
In-Reply-To: <2EBDEAE4-3119-40B9-897C-1271DBD4F2E1@suse.de> (from agraf@suse.de on Tue Jan 15 05:45:44 2013)

On 01/15/2013 05:45:44 AM, Alexander Graf wrote:
> 
> On 15.01.2013, at 12:39, Suzuki K. Poulose wrote:
> 
> > 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  
> (on
> >>> x86_64) using a kernel (with initramfs built-in the kernel)  
> without a
> >>> disk image. The kernel was built with s390 defconfig + disabled  
> 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  
> searched for
> >>> some hints / success stories, couldn't find any.
> >>>
> >>> Am I doing something wrong here ? Please let me know the right  
> procedure
> >>> for getting this up and running.
> >>
> >> S390 boots using an "image" file. Please try -kernel <kernel  
> dir>/arch/s390/boot/image.
> >>
> > Tried that even, but not any better. btw, moved to the upstream git  
> for qemu.
> >
> > 0
> > $/data/src/qemu/s390x-softmmu/qemu-system-s390x  -m 1024 -kernel  
> ./image -nographic
> > $echo $?
> > 0
> > $file ./image
> > ./image: Linux S390
> >
> > $ cd /data/src/qemu/ ; git log | head -n1
> > commit cf7c3f0cb5a7129f57fa9e69d410d6a05031988c
> 
> Does this one work for you?
> 
> 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  
directory, booting them with:

qemu-system-s390x -kernel kernel.debian -nographic -m 1024 -initrd  
initrd.debian \
  -append "rdinit=/bin/ash"

And it booted to a shell prompt... with a broken console. When I did  
"ls -l" at the resulting prompt it echoed back an ANSI escape sequence,  
one character at a time, which looks like the response to the ansi  
screen size probe busybox does (to query the display size of an xterm  
across a virtual serial console).

I.E. qemu is getting deeply confused that what comes from stdin and  
what you type on the keyboard aren't quite the same thing. Some kind of  
strange ncurses hackage, looks like?

I tried sticking "cat |" in front of the above qemu pipeline and it got  
REALLY confused.

Rob

  reply	other threads:[~2013-01-15 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 11:05 [Qemu-devel] Qemu s390x emulation Suzuki K. Poulose
2013-01-15 11:09 ` Alexander Graf
2013-01-15 11:39   ` Suzuki K. Poulose
2013-01-15 11:45     ` Alexander Graf
2013-01-15 16:04       ` Rob Landley [this message]
2013-01-17 11:24         ` Jens Freimann

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=1358265897.32505.29@driftwood \
    --to=rob@landley.net \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=suzuki@in.ibm.com \
    /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).