[Bug 1921468] Re: [UBUNTU 20.04] KVM guest fails to find zipl boot menu index

[Bug 1921468] Re: [UBUNTU 20.04] KVM guest fails to find zipl boot menu index

[Frank Heimes]

** Also affects: qemu
   Importance: Undecided
       Status: New

** No longer affects: qemu

** Also affects: ubuntu-z-systems
   Importance: Undecided
       Status: New

** Changed in: ubuntu-z-systems
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: qemu (Ubuntu)
     Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Server Team (canonical-server)

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: qemu (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1921468

Title:
  [UBUNTU 20.04] KVM guest fails to find zipl boot menu index

Status in Ubuntu on IBM z Systems:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  A KVM guest fails to find the zipl boot menu index if the "zIPL" magic value is listed at the end of a disk block. 
   
  ---System Hang---
  System sits in disabled wait, last console display
  LOADPARM=[        ]
  Using virtio-blk.
  Using ECKD scheme (block size  4096), CDL
  VOLSER=[0X0067]
   
   
  ---Steps to Reproduce---
  1. Install Distro KVM guest from ISO on a DASD, e.g. using virt-install, my invocation was 
  $ virt-install --name secguest2 --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.af6a --cdrom /var/lib/libvirt/images/xxxxxx.iso

  2. Select DHCP networking and ASCII console, and accept all defaults
  of the installer

  3. Let the installer reboot after the installation completes

  It is possible to recover by editing the domain XML with an explicit loadparm to select a boot menu entry. E.g. I changed the disk definition to
     <disk type='block' device='disk'>
        <driver name='qemu' type='raw' cache='none' io='native'/>
        <source dev='/dev/disk/by-path/ccw-0.0.af6a'/>
        <target dev='vda' bus='virtio'/>
        <boot order='1' loadparm='1'/>
        <address type='ccw' cssid='0xfe' ssid='0x0' devno='0xaf6a'/>
      </disk>

  The patches are now upstream:
  5f97ba0c74cc ("pc-bios/s390-ccw: fix off-by-one error")
  468184ec9024 ("pc-bios/s390-ccw: break loop if a null block number is reached")

  Current versions of qemu within Ubuntu

  focal (20.04LTS) 1:4.2-3ubuntu6 [ports]: arm64 armhf ppc64el s390x
  focal-updates (metapackages): 1:4.2-3ubuntu6.14: amd64 arm64 armhf ppc64el s390x

  groovy (20.10) (metapackages): 1:5.0-5ubuntu9 [ports]: arm64 armhf ppc64el s390x
  groovy-updates (metapackages): 1:5.0-5ubuntu9.6: amd64 arm64 armhf ppc64el s390x

  hirsute (metapackages): 1:5.2+dfsg-9ubuntu1: amd64 arm64 armhf ppc64el
  s390x

  
  git-commits will apply seamlessley for the requested levels if not already integrated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921468/+subscriptions