summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/architecture/1892441
blob: 68da7c03a37cb4bcd87221be790b2d5d6671ca23 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
architecture: 0.889
graphic: 0.778
boot: 0.744
ppc: 0.735
device: 0.729
user-level: 0.724
performance: 0.715
peripherals: 0.702
virtual: 0.677
PID: 0.665
assembly: 0.657
x86: 0.644
vnc: 0.621
semantic: 0.592
files: 0.579
permissions: 0.579
VMM: 0.575
kernel: 0.564
mistranslation: 0.553
hypervisor: 0.514
register: 0.498
socket: 0.490
debug: 0.487
network: 0.482
TCG: 0.440
risc-v: 0.427
arm: 0.379
i386: 0.316
KVM: 0.284
--------------------
virtual: 0.952
user-level: 0.878
hypervisor: 0.121
architecture: 0.106
boot: 0.091
TCG: 0.081
files: 0.056
register: 0.056
debug: 0.053
VMM: 0.053
PID: 0.034
network: 0.026
kernel: 0.022
socket: 0.020
device: 0.019
semantic: 0.017
permissions: 0.004
performance: 0.004
risc-v: 0.004
graphic: 0.004
peripherals: 0.003
assembly: 0.003
KVM: 0.003
vnc: 0.002
mistranslation: 0.001
ppc: 0.001
x86: 0.001
i386: 0.000
arm: 0.000

"No zIPL section in IPL2 record" error when emulating Debian 10.5.0 on s390x

Hi,

I want to emulate Debian 10.5.0 for the s390x architecture. 
The Debian image is downloaded from the following link:
https://cdimage.debian.org/debian-cd/current/s390x/iso-cd/debian-10.5.0-s390x-netinst.iso 

Using the latest QEMU version 5.1.0, running the debian image using the given command:
qemu-system-s390x -boot d -m 4096 -hda debian.qcow -cdrom debian-10.5.0-s390x-netinst.iso -nographic

causes the error output below:

LOADPARM=[        ]
Using virtio-blk.
Using guessed DASD geometry.
Using ECKD scheme (block size  4096), CDL

! No zIPL section in IPL2 record. !

As far as I know, the Debian CD ISO images are not bootable on s390x (they do not contain boot information according to the El-Torrito standard). Please open a bug against Debian instead if you want to have that changed. So far, you have to boot here manually instead (see http://people.redhat.com/~thuth/blog/qemu/2017/12/19/install-fedora.html for some more information).


Yes. For booting Debian images using QEMU (<= 5.0.0) I use this recipe:

machine_args="-M s390-ccw-virtio -m 512"
disk_args="-drive file=debian86.img,if=none,format=raw,id=hd0 -device virtio-blk-ccw,drive=hd0"
net_args=""
display_args="-display gtk -monitor stdio"
common_args="$machine_args $disk_args $net_args $display_args"

Pull kernel and initrd from the ftp server:
mkdir boot-for-install
(cd boot-for-install
 wget ftp://ftp.de.debian.org/pub/debian/dists/jessie/main/installer-s390x/current/images/generic/kernel.debian
 wget ftp://ftp.de.debian.org/pub/debian/dists/jessie/main/installer-s390x/current/images/generic/initrd.debian)

Then, for running the installer:
qemu-system-s390x $common_args -kernel boot-for-install/kernel.debian -initrd boot-for-install/initrd.debian

For booting from disk:
qemu-system-s390x $common_args -kernel boot/vmlinuz -initrd boot/initrd.img -append "root=/dev/vda2"