* [Qemu-devel] qemu-system-s390x command line
@ 2015-08-30 20:11 Richard W.M. Jones
2015-08-30 21:02 ` Alexander Graf
0 siblings, 1 reply; 6+ messages in thread
From: Richard W.M. Jones @ 2015-08-30 20:11 UTC (permalink / raw)
To: Alexander Graf, qemu-devel
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,if=none,id=disk1 -device virtio-blk-ccw,drive=disk1,id=hd1,bootindex=0 -serial stdio
Nothing seems to work at all ...
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] qemu-system-s390x command line
2015-08-30 20:11 [Qemu-devel] qemu-system-s390x command line Richard W.M. Jones
@ 2015-08-30 21:02 ` Alexander Graf
2015-08-30 21:27 ` Richard W.M. Jones
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Graf @ 2015-08-30 21:02 UTC (permalink / raw)
To: Richard W.M. Jones; +Cc: qemu-devel@nongnu.org
> Am 30.08.2015 um 22:11 schrieb Richard W.M. Jones <rjones@redhat.com>:
>
> 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).
Once you get past these points, things should be very self-explanatory. Oh - and -kernel is 0 overhead on s390x, unlike x86.
Alex
> ,if=none,id=disk1 -device virtio-blk-ccw,drive=disk1,id=hd1,bootindex=0 -serial stdio
>
> Nothing seems to work at all ...
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines. Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] qemu-system-s390x command line
2015-08-30 21:02 ` Alexander Graf
@ 2015-08-30 21:27 ` Richard W.M. Jones
2015-08-30 21:33 ` Alexander Graf
2015-08-31 17:09 ` Thomas Huth
0 siblings, 2 replies; 6+ messages in thread
From: Richard W.M. Jones @ 2015-08-30 21:27 UTC (permalink / raw)
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 <rjones@redhat.com>:
> >
> > 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] qemu-system-s390x command line
2015-08-30 21:27 ` Richard W.M. Jones
@ 2015-08-30 21:33 ` Alexander Graf
2015-08-31 17:09 ` Thomas Huth
1 sibling, 0 replies; 6+ messages in thread
From: Alexander Graf @ 2015-08-30 21:33 UTC (permalink / raw)
To: Richard W.M. Jones; +Cc: qemu-devel@nongnu.org
> Am 30.08.2015 um 23:27 schrieb Richard W.M. Jones <rjones@redhat.com>:
>
>> 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 <rjones@redhat.com>:
>>>
>>> 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.
So the guest ran and initiated an exit. Btw, you probably want -nographic.
>
> 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?
Phew, SLES11 SP4 should work. SLES12 has the same problem as RHEL7. I assume Debian may also work, but I haven't tried in quite some time :).
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] qemu-system-s390x command line
2015-08-30 21:27 ` Richard W.M. Jones
2015-08-30 21:33 ` Alexander Graf
@ 2015-08-31 17:09 ` Thomas Huth
2015-08-31 17:50 ` Richard W.M. Jones
1 sibling, 1 reply; 6+ messages in thread
From: Thomas Huth @ 2015-08-31 17:09 UTC (permalink / raw)
To: Richard W.M. Jones, Alexander Graf; +Cc: qemu-devel@nongnu.org
On 30/08/15 23:27, Richard W.M. Jones wrote:
> 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 <rjones@redhat.com>:
>>>
>>> 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?
Either try http://www.qemu-advent-calendar.org/#day-22 or the following:
wget http://ftp.nl.debian.org/debian/dists/Debian8.1/main/installer-s390x/current/images/generic/initrd.debian
wget http://ftp.nl.debian.org/debian/dists/Debian8.1/main/installer-s390x/current/images/generic/kernel.debian
Then:
qemu-system-s390x -M s390-ccw-virtio -kernel kernel.debian -initrd initrd.debian -m 512 -nographic
Hope that helps,
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] qemu-system-s390x command line
2015-08-31 17:09 ` Thomas Huth
@ 2015-08-31 17:50 ` Richard W.M. Jones
0 siblings, 0 replies; 6+ messages in thread
From: Richard W.M. Jones @ 2015-08-31 17:50 UTC (permalink / raw)
To: Thomas Huth; +Cc: Alexander Graf, qemu-devel@nongnu.org
On Mon, Aug 31, 2015 at 07:09:34PM +0200, Thomas Huth wrote:
> On 30/08/15 23:27, Richard W.M. Jones wrote:
> > 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 <rjones@redhat.com>:
> >>>
> >>> 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?
>
> Either try http://www.qemu-advent-calendar.org/#day-22 or the following:
>
> wget http://ftp.nl.debian.org/debian/dists/Debian8.1/main/installer-s390x/current/images/generic/initrd.debian
> wget http://ftp.nl.debian.org/debian/dists/Debian8.1/main/installer-s390x/current/images/generic/kernel.debian
>
> Then:
>
> qemu-system-s390x -M s390-ccw-virtio -kernel kernel.debian -initrd initrd.debian -m 512 -nographic
That works well, thanks!
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-08-31 17:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-30 20:11 [Qemu-devel] qemu-system-s390x command line Richard W.M. Jones
2015-08-30 21:02 ` Alexander Graf
2015-08-30 21:27 ` Richard W.M. Jones
2015-08-30 21:33 ` Alexander Graf
2015-08-31 17:09 ` Thomas Huth
2015-08-31 17:50 ` Richard W.M. Jones
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).