I could recreate and can confirm the same for groovy.
If the installation was started with:
sudo virt-install --name groovy --memory 2048 --disk 
path=/dev/disk/by-path/ccw-0.0.1601 --cdrom ./groovy-live-server-s390x.iso
the installer uses /dev/vda that is usually an indicator for virtio device 
rather than a DASD disk (the size of 6.877G is the correct net size of the used 
DASD Mod9 disk):

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  Guided storage configuration                                        [ Help ]
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
  Configure a guided storage layout, or create a custom one:                  
                                                                              
  (X)  Use an entire disk                                                     
                                                                              
       [ /dev/vda local disk 6.877G ▾ ]                                       
                                                                              
       [X]  Set up this disk as an LVM group                                  
                                                                              
            [ ]  Encrypt the LVM group with LUKS                              
                                                                              
                         Passphrase:                                          
                                                                              
                                                                              
                 Confirm passphrase:                                          
                                                                              
                                                                              
  ( )  Custom storage layout                                                  
                                                                              
                                 [ Done       ]                               
                                 [ Back       ]                               

I've added /var/logs and /var/crash.

** Attachment added: "02092020.tgz"
   
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5406927/+files/02092020.tgz

** Changed in: subiquity (Ubuntu)
     Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical 
Foundations Team (canonical-foundations)

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

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

** Changed in: ubuntu-z-systems
       Status: New => Triaged

** Also affects: subiquity (Ubuntu Groovy)
   Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
       Status: New

** Also affects: subiquity (Ubuntu Focal)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775

Title:
  [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on
  DASD

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to