I was trying to use virt-install to install a SLES 12 server GM VM to a DASD on system z, with KVM as hypervisor. However during the YaST2 installation, in the “disk activation” phase, it doesn’t detect the DASD. So no DASD option is proposed. When ignoring this, I could continue till the installation finishes. However, the guest never reboots. Any thoughts about this issue?
Hi levivic,
it doesn’t detect the DASD
anything in the logs of the installation system, probably output on some text console?
When ignoring this, I could continue till the installation finishes. However, the guest never reboots.
Sounds logical - no dasd, no persistent storage, no installation after reboot.
Any thoughts about this issue?
OTOH, if there’s no disk, where was Linux installed to? Especially as I would have expected the installation to fail without disk 
What did your VM report concerning the disks?
Regards,
Jens
Hi Jens,
[QUOTE=jmozdzen;29783]Hi levivic,
it doesn’t detect the DASD
anything in the logs of the installation system, probably output on some text console? [/QUOTE]
Here is the log from the text console during installation:
[HTML][lzh@atszkvm ~]$ sudo virt-install --name sles12_lei_disk --ram 1024 --disk path=/dev/disk/by-path/ccw-0.0.3808-part1 --vcpus 1 --os-type linux --os-variant generic --network bridge=virbr0 --graphics none --location /home/lzh/guest_images/SLE-12-Server-DVD-s390x-GM-DVD1.iso
WARNING No ‘console’ seen in --extra-args, a ‘console=ttyS0’ kernel argument is likely required to see text install output from the guest.
Starting install…
Retrieving file content… | 24 kB 00:00
Retrieving file linux… | 21 MB 00:00
Retrieving file initrd… | 52 MB 00:00
Creating domain… | 0 B 00:00
Connected to domain sles12_lei_disk
Escape character is ^]
Loading compiled-in X.509 certificates
Loaded X.509 cert ‘SUSE Linux Enterprise Secure Boot Signkey: 3fb077b6cebc6ff2522e1c148c57c777c788e3e7’
Loaded X.509 cert ‘SUSE Linux Enterprise Secure Boot Signkey: 3fb077b6cebc6ff2522e1c148c57c777c788e3e7’
registered taskstats version 1
AppArmor: AppArmor sha1 policy hashing enabled
Freeing unused kernel memory: 452K (00000000009d5000 - 0000000000a46000)
Moving into tmpfs… done.
SUSE Linux Enterprise 12 installation program v5.0.26 (c) 1996-2014 SUSE Linux Products GmbH <<<
Starting udev… SCSI subsystem initialized
alua: device handler registered
emc: device handler registered
rdac: device handler registered
udevd[57]: starting version 210
udevd[57]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
scsi0 : Virtio SCSI HBA
scsi 0:0:0:0: CD-ROM QEMU QEMU CD-ROM 2.2. PQ: 0 ANSI: 5
vda: vda1 vda2 vda3
sr0: scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
ok
haveged: haveged starting up
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NET: Registered protocol family 17
Loading basic drivers…sr 0:0:0:0: Attached scsi generic sg0 type 5
FS-Cache: Loaded
FS-Cache: Netfs ‘nfs’ registered for caching
loop: module loaded
8021q: 802.1Q VLAN Support v1.8
ok
Starting hardware detection… ok
(If a driver is not working for you, try booting with brokenmodules=driver_name.)
Virtio Storage 0
drivers: virtio_blk*
Virtio Ethernet Card 0
drivers: virtio_net*
Loading Installation System (1/5) - 100%
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Loading Installation System (2/5) - 100%
Loading Installation System (3/5) - 100%
Loading Installation System (4/5) - 100%
Loading Installation System (5/5) - 100%
starting syslogd (logging to /var/log/messages)… ok
starting klogd… ok
starting nscd… ok
starting yast…
Couldn’t get a file descriptor referring to the console
Couldn’t get a file descriptor referring to the console
Couldn’t get a file descriptor referring to the console
Couldn’t get a file descriptor referring to the console
Probing connected terminal…
Initializing virtual console…
Found a PuTTY terminal on /dev/console (80 columns x 62 lines).
*** Starting YaST2 ***
Couldn’t get a file descriptor referring to the console
umount: /var/lib/nfs/rpc_pipefs: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
reboot: Restarting system
Domain creation completed.
Restarting guest.
Connected to domain sles12_lei_disk
Escape character is ^][/HTML]
And the virt-install log:
[HTML]
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (cli:254) Launched with command line: /usr/share/virt-manager/virt-install --name sles12_lei_disk --ram 1024 --disk path=/dev/disk/by-path/ccw-0.0.3808-part1 --vcpus 1 --os-type linux --os-variant generic --network bridge=virbr0 --graphics none --location /home/lzh/guest_images/SLE-12-Server-DVD-s390x-GM-DVD1.iso
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (cli:264) Requesting libvirt URI default
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (cli:268) Received libvirt URI qemu:///system
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:357) Requesting virt method ‘default’, hv type ‘default’.
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:591) Received virt method ‘kvm’
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:592) Hypervisor name is ‘hvm’
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:269) Distilled --network options: [‘bridge=virbr0’]
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:182) Distilled --disk options: [‘path=/dev/disk/by-path/ccw-0.0.3808-part1’]
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (connection:241) Fetching volume XML failed: Storage volume not found: no storage vol with matching path ‘/home/lzh/virt-install.log’
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (connection:241) Fetching volume XML failed: Storage volume not found: no storage vol with matching path ‘/disk/home/lzh/virt-install.log’
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (guest:238) Setting Guest.os_variant to ‘generic’
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] WARNING (virt-install:528) No ‘console’ seen in --extra-args, a ‘console=ttyS0’ kernel argument is likely required to see text install output from the guest.
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (virt-install:746) Guest.has_install_phase: True
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:53) Using scratchdir=/var/lib/libvirt/boot
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:219) Preparing mount at /var/lib/libvirt/boot/virtinstmnt.NTiKA5
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:229) mount cmd: [‘/bin/mount’, ‘-o’, ‘ro,loop’, ‘/home/lzh/guest_images/SLE-12-Server-DVD-s390x-GM-DVD1.iso’, ‘/var/lib/libvirt/boot/virtinstmnt.NTiKA5’]
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:409) Finding distro store for location=/home/lzh/guest_images/SLE-12-Server-DVD-s390x-GM-DVD1.iso
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:196) local hasFile: Couldn’t find /var/lib/libvirt/boot/virtinstmnt.NTiKA5/.treeinfo
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:101) Fetching URI: /var/lib/libvirt/boot/virtinstmnt.NTiKA5/content
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:112) Saved file to /var/lib/libvirt/boot/virtinst-content.LHrNCN
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:101) Fetching URI: /var/lib/libvirt/boot/virtinstmnt.NTiKA5/boot/s390x/linux
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:112) Saved file to /var/lib/libvirt/boot/virtinst-linux.ZZpXKR
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:101) Fetching URI: /var/lib/libvirt/boot/virtinstmnt.NTiKA5/boot/s390x/initrd
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:112) Saved file to /var/lib/libvirt/boot/virtinst-initrd.ov8uDi
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (distroinstaller:271) Have access to preferred scratchdir so nothing to upload
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (urlfetcher:243) Cleaning up mount at /var/lib/libvirt/boot/virtinstmnt.NTiKA5
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (guest:480) …AFTER PREPARE INSTALL
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (guest:395) Generated install XML:
sles12_lei_disk
45282d45-b93a-4d00-9a84-fb3414e1f8a5
1048576
1048576
1
hvm
/var/lib/libvirt/boot/virtinst-linux.ZZpXKR
/var/lib/libvirt/boot/virtinst-initrd.ov8uDi
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
/usr/bin/qemu-kvm
[Mon, 28 Sep 2015 10:32:18 virt-install 42406] DEBUG (guest:396) Generated boot XML:
sles12_lei_disk
45282d45-b93a-4d00-9a84-fb3414e1f8a5
1048576
1048576
1
hvm
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
/usr/bin/qemu-kvm
[Mon, 28 Sep 2015 10:32:19 virt-install 42406] DEBUG (guest:426) XML fetched from libvirt object:
sles12_lei_disk
45282d45-b93a-4d00-9a84-fb3414e1f8a5
1048576
1048576
1
/machine
hvm
/var/lib/libvirt/boot/virtinst-linux.ZZpXKR
/var/lib/libvirt/boot/virtinst-initrd.ov8uDi
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
/usr/bin/qemu-kvm
system_u:system_r:svirt_t:s0:c647,c991
system_u:object_r:svirt_image_t:s0:c647,c991
[Mon, 28 Sep 2015 10:32:19 virt-install 42406] DEBUG (guest:504) … self.domain
[Mon, 28 Sep 2015 10:32:19 virt-install 42406] DEBUG (guest:507) … no installer.cleanup
[Mon, 28 Sep 2015 10:32:19 virt-install 42406] DEBUG (cli:434) Connecting to text console
[Mon, 28 Sep 2015 10:32:19 virt-install 42406] DEBUG (cli:410) Running: virsh --connect qemu:///system console sles12_lei_disk
[Mon, 28 Sep 2015 10:57:16 virt-install 42406] DEBUG (cli:434) Connecting to text console
[Mon, 28 Sep 2015 10:57:16 virt-install 42406] DEBUG (cli:410) Running: virsh --connect qemu:///system console sles12_lei_disk
[/HTML]
[QUOTE=jmozdzen;29783]
When ignoring this, I could continue till the installation finishes. However, the guest never reboots.
Sounds logical - no dasd, no persistent storage, no installation after reboot.
Any thoughts about this issue?
OTOH, if there’s no disk, where was Linux installed to? Especially as I would have expected the installation to fail without disk
What did your VM report concerning the disks?
Regards,
Jens[/QUOTE]
I think it still detects the disk and installs the vm to the disk, since during the yast2 installation it shows
x * Format partition /dev/vda1 (250.00 MiB) for /boot/zipl with ext2 x
x * Format partition /dev/vda3 (18.92 GiB) with btrfs x
x * Create subvolume @/boot/grub2/s390x-emu on device /dev/vda3 x
According to the partition sizes, I am pretty sure it was the dasd targeted. It only didn’t show the dasd option during the Disk Activation phase, which confused me. And also according to the virt-install log, the vm doesn’t report errors connecting the disk.
I tried to install Fedora guest, it could not reboot either but did complaining missing IPL device. So i am guessing the fail with SUSE may have the same reason. I know there is a tool called zipl, but does SUSE have any support on zipl?
Thanks,
Levi