* [Qemu-devel] Qemu s390x emulation
@ 2013-01-15 11:05 Suzuki K. Poulose
2013-01-15 11:09 ` Alexander Graf
0 siblings, 1 reply; 6+ messages in thread
From: Suzuki K. Poulose @ 2013-01-15 11:05 UTC (permalink / raw)
To: qemu-devel, Alexander Graf
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.
Thanks
Suzuki
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Qemu s390x emulation
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
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Graf @ 2013-01-15 11:09 UTC (permalink / raw)
To: Suzuki K. Poulose; +Cc: qemu-devel
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.
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Qemu s390x emulation
2013-01-15 11:09 ` Alexander Graf
@ 2013-01-15 11:39 ` Suzuki K. Poulose
2013-01-15 11:45 ` Alexander Graf
0 siblings, 1 reply; 6+ messages in thread
From: Suzuki K. Poulose @ 2013-01-15 11:39 UTC (permalink / raw)
To: Alexander Graf; +Cc: qemu-devel
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
Thanks
Suzuki
>
> Alex
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Qemu s390x emulation
2013-01-15 11:39 ` Suzuki K. Poulose
@ 2013-01-15 11:45 ` Alexander Graf
2013-01-15 16:04 ` Rob Landley
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Graf @ 2013-01-15 11:45 UTC (permalink / raw)
To: Suzuki K. Poulose; +Cc: qemu-devel
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
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Qemu s390x emulation
2013-01-15 11:45 ` Alexander Graf
@ 2013-01-15 16:04 ` Rob Landley
2013-01-17 11:24 ` Jens Freimann
0 siblings, 1 reply; 6+ messages in thread
From: Rob Landley @ 2013-01-15 16:04 UTC (permalink / raw)
To: Alexander Graf; +Cc: Suzuki K. Poulose, qemu-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Qemu s390x emulation
2013-01-15 16:04 ` Rob Landley
@ 2013-01-17 11:24 ` Jens Freimann
0 siblings, 0 replies; 6+ messages in thread
From: Jens Freimann @ 2013-01-17 11:24 UTC (permalink / raw)
To: Rob Landley; +Cc: Suzuki K. Poulose, Alexander Graf, qemu-devel
On Tue, Jan 15, 2013 at 10:04:57AM -0600, Rob Landley wrote:
> 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:
> >
> >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 get the same result with this combination of kernel and initrd. However,
with a more simple ramdisk (built by myself) that only has busybox in it
I could boot into a shell that worked just fine. It seems to me that something
in initrd.debian is not working well with qemu/virtio_console but I haven't
debugged it further.
Jens
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-01-17 11:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2013-01-17 11:24 ` Jens Freimann
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).