Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1832138 - Supermin can't find rootfs
Summary: Supermin can't find rootfs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2020-05-06 07:30 UTC by Jakub Čajka
Modified: 2020-11-24 17:20 UTC (History)
23 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 17:20:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 189032 0 None None None 2020-11-05 12:54:33 UTC

Description Jakub Čajka 2020-05-06 07:30:09 UTC
1. Please describe the problem:
During build of Fedora CoreOS(running qemu/supermin in side a podman container) supermin init will fail due to it not finding rootfs. During one(but not always...) build kernel will complain see bottom of the report.
Consecutive runs will(not always, but most of the time) fail until the host is rebooted without nothing logged by kernel, build that causes the log will succeed.

2. What is the Version-Release number of the kernel:
5.6.8-200.fc31.s390x

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Currently try building FCOS severla times in a row and kernel will log issue and builds will start failing.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
I haven't got around to test this yet.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
I'm not.

May 05 20:32:10 kernel: ------------[ cut here ]------------
May 05 20:32:10 kernel: WARNING: CPU: 0 PID: 12450 at arch/s390/kvm/priv.c:632 handle_pqap+0x1e8/0x200 [kvm]
May 05 20:32:10 kernel: Modules linked in: kvm ip6table_nat ip6_tables xt_conntrack iptable_filter xt_MASQUERADE xt_comment iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 veth bridge stp llc overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache sunrpc ghash_s390 prng aes_s390 des_s390 libdes qeth_l2 qeth qdio ccwgroup vfio_ccw vfio_mdev mdev sha512_s390 vfio_iommu_type1 sha1_s390 vfio ip_tables xfs libcrc32c crc32_vx_s390 sha256_s390 sha_common dasd_eckd_mod dasd_mod pkey zcrypt fuse
May 05 20:32:10 kernel: CPU: 0 PID: 12450 Comm: qemu-system-s39 Not tainted 5.6.8-200.fc31.s390x #1
May 05 20:32:10 kernel: Hardware name: IBM 2964 N96 400 (z/VM 7.1.0)
May 05 20:32:10 kernel: Krnl PSW : 0704d00180000000 000003ff806aa76c (handle_pqap+0x1ec/0x200 [kvm])
May 05 20:32:10 kernel:            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
May 05 20:32:10 kernel: Krnl GPRS: 0000000000000000 0000000121c01000 0000000121c00000 0000000000000000
May 05 20:32:10 kernel:            0000000121c00000 0000000000000000 000003fffffffdfd 000000009479c27f
May 05 20:32:10 kernel:            0000000000000000 000000009479c27e 0000000121c01000 000000009479c240
May 05 20:32:10 kernel:            00000001467f6000 000003ff806b4678 000003e0022cfb98 000003e0022cfb10
May 05 20:32:10 kernel: Krnl Code: 000003ff806aa760: 96301092                oi        146(%r1),48
                                   000003ff806aa764: a7f4ffc0                brc        15,000003ff806aa6e4
                                  #000003ff806aa768: af000000                mc        0,0
                                  >000003ff806aa76c: a7a8ffa1                lhi        %r10,-95
                                   000003ff806aa770: b914002a                lgfr        %r2,%r10
                                   000003ff806aa774: eb9ff0e80004        lmg        %r9,%r15,232(%r15)
                                   000003ff806aa77a: c0f4000048cb        brcl        15,000003ff806b3910
                                   000003ff806aa780: c00400000000        brcl        0,000003ff806aa780
May 05 20:32:10 kernel: Call Trace:
May 05 20:32:10 kernel:  [<000003ff806aa76c>] handle_pqap+0x1ec/0x200 [kvm]
May 05 20:32:10 kernel:  [<000003ff806ac0f6>] kvm_s390_handle_b2+0x116/0x508 [kvm]
May 05 20:32:10 kernel:  [<000003ff8069f64c>] kvm_handle_sie_intercept+0x954/0xc28 [kvm]
May 05 20:32:10 kernel:  [<000003ff8069caf0>] kvm_arch_vcpu_ioctl_run+0x958/0x13f0 [kvm]
May 05 20:32:10 kernel:  [<000003ff8068915c>] kvm_vcpu_ioctl+0x284/0x7b0 [kvm]
May 05 20:32:10 kernel:  [<00000001d14bc05a>] ksys_ioctl+0xb2/0xe8
May 05 20:32:10 kernel:  [<00000001d14bc0fa>] __s390x_sys_ioctl+0x2a/0x38
May 05 20:32:10 kernel:  [<00000001d1ad0050>] system_call+0xdc/0x2c8
May 05 20:32:10 kernel: Last Breaking-Event-Address:
May 05 20:32:10 kernel:  [<000003ff806aa5d8>] handle_pqap+0x58/0x200 [kvm]
May 05 20:32:10 kernel: ---[ end trace 4140ae87c28b499f ]---

Comment 1 Jakub Čajka 2020-05-06 07:34:21 UTC
Few older occurrences.
May 04 16:34:13 kernel: ------------[ cut here ]------------
May 04 16:34:13 kernel: WARNING: CPU: 0 PID: 127407 at arch/s390/kvm/priv.c:632 handle_pqap+0x1e8/0x200 [kvm]
May 04 16:34:13 kernel: Modules linked in: kvm ip6table_nat ip6_tables xt_conntrack iptable_filter xt_MASQUERADE xt_comment iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 veth bridge stp llc overla>
May 04 16:34:13 kernel: CPU: 0 PID: 127407 Comm: qemu-system-s39 Not tainted 5.6.7-200.fc31.s390x #1
May 04 16:34:13 kernel: Hardware name: IBM 2964 N96 400 (z/VM 7.1.0)
May 04 16:34:13 kernel: Krnl PSW : 0704d00180000000 000003ff806c46dc (handle_pqap+0x1ec/0x200 [kvm])
May 04 16:34:13 kernel:            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
May 04 16:34:13 kernel: Krnl GPRS: 0000000000000000 00000000c1039000 000000017c569000 0000000000000000
May 04 16:34:13 kernel:            000000017c569000 0000000000000000 000003fffffffdfd 000000009278639f
May 04 16:34:13 kernel:            0000000000000000 000000009278639e 00000000c1039000 0000000092786360
May 04 16:34:13 kernel:            0000000095e64000 000003ff806ce678 000003e0062a7b98 000003e0062a7b10
May 04 16:34:13 kernel: Krnl Code: 000003ff806c46d0: 96301092                oi        146(%r1),48
                                   000003ff806c46d4: a7f4ffc0                brc        15,000003ff806c4654
                                  #000003ff806c46d8: af000000                mc        0,0
                                  >000003ff806c46dc: a7a8ffa1                lhi        %r10,-95
                                   000003ff806c46e0: b914002a                lgfr        %r2,%r10
                                   000003ff806c46e4: eb9ff0e80004        lmg        %r9,%r15,232(%r15)
                                   000003ff806c46ea: c0f4000048cb        brcl        15,000003ff806cd880
                                   000003ff806c46f0: c00400000000        brcl        0,000003ff806c46f0
May 04 16:34:13 kernel: Call Trace:
May 04 16:34:13 kernel:  [<000003ff806c46dc>] handle_pqap+0x1ec/0x200 [kvm] 
May 04 16:34:13 kernel:  [<000003ff806c6066>] kvm_s390_handle_b2+0x116/0x508 [kvm] 
May 04 16:34:13 kernel:  [<000003ff806b95bc>] kvm_handle_sie_intercept+0x954/0xc28 [kvm] 
May 04 16:34:13 kernel:  [<000003ff806b6a60>] kvm_arch_vcpu_ioctl_run+0x958/0x13f0 [kvm] 
May 04 16:34:13 kernel:  [<000003ff806a313c>] kvm_vcpu_ioctl+0x284/0x7b0 [kvm] 
May 04 16:34:13 kernel:  [<0000000116e67fca>] ksys_ioctl+0xb2/0xe8 
May 04 16:34:13 kernel:  [<0000000116e6806a>] __s390x_sys_ioctl+0x2a/0x38 
May 04 16:34:13 kernel:  [<000000011747be28>] system_call+0xdc/0x2c8 
May 04 16:34:13 kernel: Last Breaking-Event-Address:
May 04 16:34:13 kernel:  [<000003ff806c4548>] handle_pqap+0x58/0x200 [kvm]
May 04 16:34:13 kernel: ---[ end trace deffe63a79760784 ]---

May 05 15:41:11 kernel: WARNING: CPU: 0 PID: 13657 at arch/s390/kvm/priv.c:632 handle_pqap+0x1e8/0x200 [kvm]
May 05 15:41:11 kernel: Modules linked in: kvm ip6table_nat ip6_tables xt_conntrack iptable_filter xt_MASQUERADE xt_comment iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 veth bridge stp llc overla>
May 05 15:41:11 kernel: CPU: 0 PID: 13657 Comm: qemu-system-s39 Not tainted 5.6.8-200.fc31.s390x #1
May 05 15:41:11 kernel: Hardware name: IBM 2964 N96 400 (z/VM 7.1.0)
May 05 15:41:11 kernel: Krnl PSW : 0704d00180000000 000003ff806c076c (handle_pqap+0x1ec/0x200 [kvm])
May 05 15:41:11 kernel:            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
May 05 15:41:11 kernel: Krnl GPRS: 0000000000000000 00000001bccf4000 00000001c26f9000 0000000000000000
May 05 15:41:11 kernel:            00000001c26f9000 0000000000000000 000003fffffffdfd 000000012050427f
May 05 15:41:11 kernel:            0000000100000000 000000012050427e 00000001bccf4000 0000000120504240
May 05 15:41:11 kernel:            00000001b53aa000 000003ff806ca678 000003e0073c7b98 000003e0073c7b10
May 05 15:41:11 kernel: Krnl Code: 000003ff806c0760: 96301092                oi        146(%r1),48
                                   000003ff806c0764: a7f4ffc0                brc        15,000003ff806c06e4
                                  #000003ff806c0768: af000000                mc        0,0
                                  >000003ff806c076c: a7a8ffa1                lhi        %r10,-95
                                   000003ff806c0770: b914002a                lgfr        %r2,%r10
                                   000003ff806c0774: eb9ff0e80004        lmg        %r9,%r15,232(%r15)
                                   000003ff806c077a: c0f4000048cb        brcl        15,000003ff806c9910
                                   000003ff806c0780: c00400000000        brcl        0,000003ff806c0780
May 05 15:41:11 kernel: Call Trace:
May 05 15:41:11 kernel:  [<000003ff806c076c>] handle_pqap+0x1ec/0x200 [kvm] 
May 05 15:41:11 kernel:  [<000003ff806c20f6>] kvm_s390_handle_b2+0x116/0x508 [kvm] 
May 05 15:41:11 kernel:  [<000003ff806b564c>] kvm_handle_sie_intercept+0x954/0xc28 [kvm] 
May 05 15:41:11 kernel:  [<000003ff806b2af0>] kvm_arch_vcpu_ioctl_run+0x958/0x13f0 [kvm] 
May 05 15:41:11 kernel:  [<000003ff8069f15c>] kvm_vcpu_ioctl+0x284/0x7b0 [kvm] 
May 05 15:41:11 kernel:  [<0000000151fb005a>] ksys_ioctl+0xb2/0xe8 
May 05 15:41:11 kernel:  [<0000000151fb00fa>] __s390x_sys_ioctl+0x2a/0x38 
May 05 15:41:11 kernel:  [<00000001525c4050>] system_call+0xdc/0x2c8 
May 05 15:41:11 kernel: Last Breaking-Event-Address:
May 05 15:41:11 kernel:  [<000003ff806c05d8>] handle_pqap+0x58/0x200 [kvm]
May 05 15:41:11 kernel: ---[ end trace 95d38430b60bd564 ]---

Comment 2 Dan Horák 2020-05-06 08:13:26 UTC
adding s390x virt people to CC ...

Comment 3 Cornelia Huck 2020-05-06 08:18:09 UTC
This looks like the issue fixed by https://lore.kernel.org/kvm/20200505083515.2720-1-borntraeger@de.ibm.com/

Comment 4 Christian Borntraeger 2020-05-06 09:46:27 UTC
Yes, that patch should avoid this.
I still want to look more into this. 
Can you paste me the output of /proc/cpuinfo of the host
and also the output of QEMU (e.g. libvirt log file)?

Comment 5 Jakub Čajka 2020-05-06 11:05:36 UTC
I'm looking in to building kernel with that small patch for the host. BTW is it just disabling the logged message?

cat /proc/cpuinfo
vendor_id       : IBM/S390
# processors    : 2
bogomips per cpu: 3033.00
max thread id   : 0
features	: esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te vx sie 
facilities      : 0 1 2 3 4 6 7 8 9 10 12 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 35 36 37 40 41 42 43 44 45 46 47 48 49 50 51 52 53 55 57 73 74 75 76 77 80 81 82 128 129 131
cache0          : level=1 type=Data scope=Private size=128K line_size=256 associativity=8
cache1          : level=1 type=Instruction scope=Private size=96K line_size=256 associativity=6
cache2          : level=2 type=Data scope=Private size=2048K line_size=256 associativity=8
cache3          : level=2 type=Instruction scope=Private size=2048K line_size=256 associativity=8
cache4          : level=3 type=Unified scope=Shared size=65536K line_size=256 associativity=16
cache5          : level=4 type=Unified scope=Shared size=491520K line_size=256 associativity=30
processor 0: version = FF,  identification = 2633E8,  machine = 2964
processor 1: version = FF,  identification = 2633E8,  machine = 2964

cpu number      : 0
cpu MHz dynamic : 5000
cpu MHz static  : 5000

cpu number      : 1
cpu MHz dynamic : 5000
cpu MHz static  : 5000

What do you meen by QEMU output? Afaik libvirt shouldn't be involved, all virt should be run directly via qemu invocation inside podman F31 conatainer(it gets /dev/kvm, /dev/fuse), run on f31 host.
Atually since I have filled this bug and rebooted that host I can't reproduce it, for better or worse...(blocked me, consistently for ~4 days prior, has been rulling out possible changes) 
Older failed FCOS build(supermin applience invocation) log snippet, AFAIK it shouldn't contain anything really useful, at least to me( most note worthy rootfs is xfs, not ext4).

+ kola qemuexec -m 2048 --auto-cpus -U --workdir none -- -no-reboot -nodefaults -serial file:/srv/tmp/runvm-console.txt -kernel /srv/tmp/supermin.build/kernel -initrd /srv/tmp/supermin.build/initrd -device virtio-serial -device virtserialport,chardev=virtioserial0,name=cosa-cmdout -chardev stdio,id=virtioserial0 -drive if=none,id=root,format=raw,snapshot=on,file=/srv/tmp/supermin.build/root,index=1 -device virtio-blk,drive=root -virtfs local,id=workdir,path=/srv,security_model=none,mount_tag=workdir -append 'root=/dev/vda console=ttysclp0 selinux=1 enforcing=0 autorelabel=1' -drive if=none,id=target,format=qcow2,file=/srv/tmp/build/fedora-coreos-31.20200505.dev.0-qemu.s390x.qcow2.tmp,cache=unsafe -device virtio-blk,serial=target,drive=target
+ '[' '!' -f /srv/tmp/rc ']'
+ cat /srv/tmp/runvm-console.txt
[    0.327441] Linux version 5.6.8-200.fc31.s390x (mockbuild.fedoraproject.org) (gcc version 9.3.1 20200408 (Red Hat 9.3.1-2) (GCC)) #1 SMP Wed Apr 29 17:53:49 UTC 2020
[    0.327469] setup: Linux is running under KVM in 64-bit mode
[    0.327538] setup: The maximum memory size is 2048MB
[    0.327725] numa: NUMA mode: plain
[    0.328184] cpu: 2 configured CPUs, 0 standby CPUs
[    0.328456] Write protected kernel read-only data: 11948k
[    0.720843] Zone ranges:
[    0.720894]   DMA      [mem 0x0000000000000000-0x000000007fffffff]
[    0.720901]   Normal   empty
[    0.720903] Movable zone start for each node
[    0.720904] Early memory node ranges
[    0.720907]   node   0: [mem 0x0000000000000000-0x000000007fffffff]
[    0.720930] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[    1.000106] percpu: Embedded 32 pages/cpu s90880 r8192 d32000 u131072
[    1.000251] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    1.000256] Policy zone: DMA
[    1.000274] Kernel command line: root=/dev/vda console=ttysclp0 selinux=1 enforcing=0 autorelabel=1
[    1.005818] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    1.006491] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    1.006604] mem auto-init: stack:off, heap alloc:off, heap free:off
[    1.192959] Memory: 2038596K/2097152K available (9056K kernel code, 4352K rwdata, 2892K rodata, 3820K init, 764K bss, 58556K reserved, 0K cma-reserved)
[    1.193026] random: get_random_u64 called from __kmem_cache_create+0x42/0x5f0 with crng_init=0
[    1.193249] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    1.193280] ftrace: allocating 30013 entries in 118 pages
[    1.211694] ftrace: allocated 118 pages with 5 groups
[    1.213828] rcu: Hierarchical RCU implementation.
[    1.213834] rcu: 	RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=2.
[    1.213837] 	Tasks RCU enabled.
[    1.213840] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    1.213841] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    1.221104] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3
[    1.233419] clocksource: tod: mask: 0xffffffffffffffff max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
[    1.233655] Console: colour dummy device 80x25
[    1.233987] printk: console [ttyS1] enabled
[    1.234207] pid_max: default: 32768 minimum: 301
[    1.234304] LSM: Security Framework initializing
[    1.234343] Yama: becoming mindful.
[    1.234367] SELinux:  Initializing.
[    1.234409] *** VALIDATE selinux ***
[    1.234458] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    1.234479] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    1.234541] *** VALIDATE tmpfs ***
[    1.234933] *** VALIDATE proc ***
[    1.235100] *** VALIDATE cgroup ***
[    1.235107] *** VALIDATE cgroup2 ***
[    1.235790] rcu: Hierarchical SRCU implementation.
[    1.236619] smp: Bringing up secondary CPUs ...
[    1.241420] smp: Brought up 1 node, 2 CPUs
[    1.275108] devtmpfs: initialized
[    1.278357] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    1.278363] futex hash table entries: 512 (order: 5, 131072 bytes, linear)
[    1.278905] NET: Registered protocol family 16
[    1.285373] audit: initializing netlink subsys (disabled)
[    1.285713] Spectre V2 mitigation: execute trampolines
[    1.286322] audit: type=2000 audit(1588672737.317:1): state=initialized audit_enabled=0 res=1
[    1.354630] HugeTLB registered 1.00 MiB page size, pre-allocated 0 pages
[    2.802559] random: fast init done
[    2.806990] alg: No test for 842 (842-generic)
[    2.807340] alg: No test for 842 (842-scomp)
[    2.823381] iommu: Default domain type: Translated 
[    2.823611] SCSI subsystem initialized
[    2.823831] pps_core: LinuxPPS API ver. 1 registered
[    2.823833] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti>
[    2.823836] PTP clock support registered
[    2.903575] NetLabel: Initializing
[    2.903611] NetLabel:  domain hash size = 128
[    2.903613] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    2.903725] NetLabel:  unlabeled traffic allowed by default
[    2.940554] PCI host bridge to bus 0001:00
[    2.940583] pci_bus 0001:00: root bus resource [mem 0x8000000000000000-0x800000000000003f]
[    2.940585] pci_bus 0001:00: root bus resource [mem 0x8001000000000000-0x8001000000000fff]
[    2.940587] pci_bus 0001:00: root bus resource [mem 0x8002000000000000-0x8002000000003fff]
[    2.940589] pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
[    2.940748] pci 0001:00:00.0: [1af4:1009] type 00 class 0x000200
[    2.940950] pci 0001:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
[    2.941002] pci 0001:00:00.0: reg 0x14: [mem 0x00000000-0x00000fff]
[    2.941202] pci 0001:00:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref]
[    2.942069] pci 0001:00:00.0: Adding to iommu group 0
[    2.942093] pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 00
[    3.008118] *** VALIDATE bpf ***
[    3.009396] VFS: Disk quotas dquot_6.6.0
[    3.009441] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    3.009549] *** VALIDATE ramfs ***
[    3.009556] *** VALIDATE hugetlbfs ***
[    3.037374] NET: Registered protocol family 2
[    3.038000] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    3.038020] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    3.038161] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    3.038415] TCP: Hash tables configured (established 16384 bind 16384)
[    3.038571] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    3.038607] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    3.038696] NET: Registered protocol family 1
[    3.038714] NET: Registered protocol family 44
[    3.038797] Trying to unpack rootfs image as initramfs...
[    3.040447] Freeing initrd memory: 764K
[    3.042429] hypfs: The hardware system does not support hypfs
[    3.042531] hypfs: Initialization of hypfs failed with rc=-61
[    3.043540] Initialise system trusted keyrings
[    3.043577] Key type blacklist registered
[    3.048208] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[    3.050770] zbud: loaded
[    3.084211] NET: Registered protocol family 38
[    3.084287] Key type asymmetric registered
[    3.084296] Asymmetric key parser 'x509' registered
[    3.084448] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    3.085029] io scheduler mq-deadline registered
[    3.085036] io scheduler kyber registered
[    3.085189] io scheduler bfq registered
[    3.085461] atomic64_test: passed
[    3.085740] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    3.086595] virtio-pci 0001:00:00.0: enabling device (0000 -> 0002)
[    3.088901] hvc_iucv: The z/VM IUCV HVC device driver cannot be used without z/VM
[    3.090725] libphy: Fixed MDIO Bus: probed
[    3.090893] device-mapper: uevent: version 1.0.3
[    3.091036] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel
[    3.093863] cio: Channel measurement facility initialized using format extended (mode autodetected)
[    3.094307] sclp_sd: Store Data request failed (eq=2, di=3, response=0x40f0, flags=0x00, status=0, rc=-5)
[    3.098510] ap: The hardware system does not support AP instructions
[    3.098733] drop_monitor: Initializing network drop monitor service
[    3.098894] Initializing XFRM netlink socket
[    3.099103] NET: Registered protocol family 10
[    3.259424] random: crng init done
[    3.362641] Segment Routing with IPv6
[    3.362830] mip6: Mobile IPv6
[    3.362851] NET: Registered protocol family 17
[    3.457377] registered taskstats version 1
[    3.457544] Loading compiled-in X.509 certificates
[    3.874884] Loaded X.509 cert 'Fedora kernel signing key: e8f3e5e1c427fc47e89e9af4c33a1c77a6c86a23'
[    3.875175] zswap: loaded using pool lzo/zbud
[    3.905102] Key type ._fscrypt registered
[    3.905122] Key type .fscrypt registered
[    3.905125] Key type fscrypt-provisioning registered
[    3.907656] Key type big_key registered
[    3.908752] Key type encrypted registered
[    3.908786] ima: No TPM chip found, activating TPM-bypass!
[    3.908793] ima: Allocated hash algorithm: sha256
[    3.908827] ima: No architecture policies found
[    3.912539] Freeing unused kernel memory: 3820K
[    3.953798] Write protected read-only-after-init data: 72k
[    3.953866] rodata_test: all tests were successful
[    3.953874] Run /init as init process
supermin: mounting /proc
supermin: ext2 mini initrd starting up: 5.2.0 dietlibc
supermin: cmdline: root=/dev/vda console=ttysclp0 selinux=1 enforcing=0 autorelabel=1
supermin: uptime: 3.95 1.68
supermin: mounting /sys
supermin: internal insmod crc32-vx_s390.ko
[    3.957669] alg: No test for crc32be (crc32be-vx)
supermin: internal insmod crc32_generic.ko
supermin: internal insmod virtio_blk.ko
[    3.980689] virtio_blk virtio3: [vda] 16777216 512-byte logical blocks (8.59 GB/8.00 GiB)
[    4.050965] virtio_blk virtio5: [vdb] 10485760 512-byte logical blocks (5.37 GB/5.00 GiB)
supermin: internal insmod crypto_engine.ko
supermin: internal insmod virtio_crypto.ko
supermin: internal insmod failover.ko
supermin: internal insmod net_failover.ko
supermin: internal insmod virtio_net.ko
supermin: internal insmod rpmsg_core.ko
supermin: internal insmod virtio_rpmsg_bus.ko
supermin: internal insmod virtio_scsi.ko
supermin: internal insmod virtio_balloon.ko
supermin: internal insmod virtio_input.ko
supermin: internal insmod virtio_mmio.ko
supermin: internal insmod fuse.ko
[    4.260268] fuse: init (API version 7.31)
[    4.260364] *** VALIDATE fuseblk ***
[    4.260420] *** VALIDATE fuse ***
supermin: internal insmod virtiofs.ko
supermin: internal insmod crc-itu-t.ko
supermin: internal insmod crc4.ko
supermin: internal insmod crc64.ko
supermin: internal insmod crc8.ko
supermin: internal insmod libcrc32c.ko
supermin: picked /sys/block/vda/dev (252:0) as root device
supermin: creating /dev/root as block special 252:0
supermin: mounting new root on /root
[    4.270801] EXT4-fs (vda): VFS: Can't find ext4 filesystem
mount: /root: Invalid argument
[    4.271064] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[    4.271074] CPU: 1 PID: 1 Comm: /init Not tainted 5.6.8-200.fc31.s390x #1
[    4.271075] Hardware name: IBM 2964 N96 400 (KVM/Linux)
[    4.271080] Call Trace:
[    4.271115]  [<000000004e9182da>] show_stack+0x8a/0xd0 
[    4.271130]  [<000000004f1b64c2>] dump_stack+0x8a/0xb8 
[    4.271135]  [<000000004e94b9e2>] panic+0x112/0x308 
[    4.271139]  [<000000004e951abc>] do_exit+0xb94/0xc00 
[    4.271141]  [<000000004e951bb0>] do_group_exit+0x0/0xe0 
[    4.271149]  [<000000004f1d8050>] system_call+0xdc/0x2c8

Comment 6 Ben Cotton 2020-11-03 16:40:50 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Christian Borntraeger 2020-11-04 06:54:08 UTC
the host crash should be fixed inf32 and f33.
Regsarding the guest not booting, is this still happening?
You do have 2 virtio-blk disks. Maybe /dev/vda is the wrong one and /dev/disk/by-id/... or whatever would be better?

Comment 8 Ben Cotton 2020-11-24 17:20:00 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.