qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Qemu s390x emulation


From: Rob Landley
Subject: Re: [Qemu-devel] Qemu s390x emulation
Date: Tue, 15 Jan 2013 10:04:57 -0600

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 via email to

[Prev in Thread] Current Thread [Next in Thread]