------- Comment From [email protected] 2017-12-25 15:10 EDT------- I'm unable to get this fix applied to artful guest VM thought slof packages are updates. ---------------------------------------------------------------------------------------------------------------------------------- I could able to recreate the issue; Initially added upto 32 boot order disks apart from primary disk(boot order 1), and not able to recreate it.
Applied artful proposed fixes and could able to boot the guest successfully. ------- Comment From [email protected] 2017-12-25 15:13 EDT------- (In reply to comment #25) > I'm unable to get this fix applied to artful guest VM thought slof packages > are updates. > Artful validation: > ----------------------------------------------------------------------------- > ----------------------------------------------------- > I could able to recreate the issue; Initially added upto 32 boot order disks > apart from primary disk(boot order 1), and not able to recreate it. > > ubuntu login: root > Password: > Welcome to Ubuntu 17.10 (GNU/Linux 4.13.0-16-generic ppc64le) > > * Documentation: https://help.ubuntu.com > * Management: https://landscape.canonical.com > * Support: https://ubuntu.com/advantage > > > 46 packages can be updated. > 27 updates are security updates. > > The programs included with the Ubuntu system are free software; > the exact distribution terms for each program are described in the > individual files in /usr/share/doc/*/copyright. > > Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by > applicable law. > > root@ubuntu:~# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sr0 11:0 1 1024M 0 rom > vda 252:0 0 1M 0 disk > vdb 252:16 0 1M 0 disk > vdc 252:32 0 1M 0 disk > vdd 252:48 0 1M 0 disk > vde 252:64 0 1M 0 disk > vdf 252:80 0 1M 0 disk > vdg 252:96 0 1M 0 disk > vdh 252:112 0 1M 0 disk > vdi 252:128 0 1M 0 disk > vdj 252:144 0 1M 0 disk > vdk 252:160 0 1M 0 disk > vdl 252:176 0 1M 0 disk > vdm 252:192 0 1M 0 disk > vdn 252:208 0 1M 0 disk > vdo 252:224 0 1M 0 disk > vdp 252:240 0 1M 0 disk > vdq 252:256 0 1M 0 disk > vdr 252:272 0 1M 0 disk > vds 252:288 0 1M 0 disk > vdt 252:304 0 1M 0 disk > vdu 252:320 0 1M 0 disk > vdv 252:336 0 1M 0 disk > vdw 252:352 0 1M 0 disk > vdx 252:368 0 1M 0 disk > vdy 252:384 0 1M 0 disk > vdz 252:400 0 1M 0 disk > vdaa 252:416 0 50G 0 disk > ??vdaa1 252:417 0 7M 0 part > ??vdaa2 252:418 0 50G 0 part / > vdab 252:432 0 1M 0 disk > vdac 252:448 0 1M 0 disk > vdad 252:464 0 1M 0 disk > vdae 252:480 0 1M 0 disk > vdaf 252:496 0 1M 0 disk > vdag 252:512 0 1M 0 disk > > Added one more addition one, 34th boot order disk, could able to recreate it. > > [root@lep8a artful]# vi disk.xml > > [root@lep8a artful]# virsh edit kal-artful_vm1 > Domain kal-artful_vm1 XML configuration edited. > > [root@lep8a artful]# virsh destroy kal-artful_vm1 > Domain kal-artful_vm1 destroyed > > [root@lep8a artful]# virsh start --console kal-artful_vm1 > Domain kal-artful_vm1 started > Connected to domain kal-artful_vm1 > Escape character is ^] > SLOF ********************************************************************** > QEMU Starting > Build Date = May 19 2017 07:43:48 > FW Version = mockbuild@ release 20170303 > Press "s" to enter Open Firmware. > > Populating /vdevice methods > Populating /vdevice/v-scsi@2000 > SCSI: Looking for devices > 8000000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.5+" > Populating /vdevice/vty@30000000 > Populating /vdevice/nvram@71000000 > Populating /pci@800000020000000 > 00 f800 (D) : 1af4 1001 virtio [ block ] > 00 f000 (D) : 1af4 1001 virtio [ block ] > 00 e800 (D) : 1af4 1001 virtio [ block ] > 00 e000 (D) : 1af4 1001 virtio [ block ] > 00 d800 (D) : 1af4 1001 virtio [ block ] > 00 d000 (D) : 1af4 1001 virtio [ block ] > 00 c800 (D) : 1af4 1001 virtio [ block ] > 00 c000 (D) : 1af4 1001 virtio [ block ] > 00 b800 (D) : 1af4 1001 virtio [ block ] > 00 b000 (D) : 1af4 1001 virtio [ block ] > 00 a800 (D) : 1af4 1001 virtio [ block ] > 00 a000 (D) : 1af4 1001 virtio [ block ] > 00 9800 (D) : 1af4 1001 virtio [ block ] > 00 9000 (D) : 1af4 1001 virtio [ block ] > 00 8800 (D) : 1af4 1001 virtio [ block ] > 00 8000 (D) : 1af4 1001 virtio [ block ] > 00 7800 (D) : 1af4 1001 virtio [ block ] > 00 7000 (D) : 1af4 1001 virtio [ block ] > 00 6800 (D) : 1af4 1001 virtio [ block ] > 00 6000 (D) : 1af4 1001 virtio [ block ] > 00 5800 (D) : 1af4 1001 virtio [ block ] > 00 5000 (D) : 1af4 1001 virtio [ block ] > 00 4800 (D) : 1af4 1001 virtio [ block ] > 00 4000 (D) : 1af4 1001 virtio [ block ] > 00 3800 (D) : 1af4 1001 virtio [ block ] > 00 3000 (D) : 1af4 1001 virtio [ block ] > 00 2800 (B) : 1b36 0001 pci* > 01 3800 (D) : 1af4 1001 virtio [ block ] > 01 3000 (D) : 1af4 1001 virtio [ block ] > 01 2800 (D) : 1af4 1001 virtio [ block ] > 01 2000 (D) : 1af4 1001 virtio [ block ] > 01 1800 (D) : 1af4 1001 virtio [ block ] > 01 1000 (D) : 1af4 1001 virtio [ block ] > 01 0800 (D) : 1af4 1001 virtio [ block ] > 00 2000 (D) : 1af4 1002 unknown-legacy-device* > 00 1800 (D) : 1af4 1001 virtio [ block ] > 00 1000 (D) : 1033 0194 serial bus [ usb-xhci ] > 00 0800 (D) : 1af4 1000 virtio [ net ] > No NVRAM common partition, re-initializing... > Scanning USB > XHCI: Initializing > Using default console: /vdevice/vty@30000000 > > Welcome to Open Firmware > > Copyright (c) 2004, 2017 IBM Corporation All rights reserved. > This program and the accompanying materials are made available > under the terms of the BSD License available at > http://www.opensource.org/licenses/bsd-license.php > > > > ( 400 ) Instruction Storage Exception [ c0 ] > > > R0 .. R7 R8 .. R15 R16 .. R23 R24 .. R31 > 000000007dbe2ff4 000000007dc5e228 0000000000000000 000000007dc08540 > 000000007e666000 63692d6272696467 0000000000000000 0000000000000006 > 000000007dc0df00 000000007e7a5c38 0000000000000000 000000007dc04900 > 000000007e45df00 000000007e45df00 000000007dbe0e38 000000007dc08370 > 000000007dc4a018 0000000000040000 0000000000000045 0000000000000003 > 00000000000000c0 0000000000000000 000000007e7a5c23 ffffffffffffffff > 000000007dc4a040 0000000000000000 000000007e7a018c 000000007e462010 > 0000000000000000 0000000000000000 0000000000000000 000000007e706df0 > > CR / XER LR / CTR SRR0 / SRR1 DAR / DSISR > 84000042 000000007dbe5330 63692d6272696464 0000000000000000 > 0000000020000000 63692d6272696467 8000000040001000 00000000 > > > 7 > > > Removed 34 boot order disk: > <disk type='file' device='disk'> > <driver name='qemu' type='qcow2'/> > <source > file='/var/lib/libvirt/images/data/kal/base/artful/kal-artful-kb9.qcow'/> > <target dev='vdbk' bus='virtio'/> > <boot order='34'/> > <address type='pci' domain='0x0000' bus='0x01' slot='0x07' > function='0x0'/> > </disk> > > Booted the VM successfully. > > Applied artful proposed fixes and could able to boot the guest successfully. > > root@ubuntu:~# apt-get install qemu-slof/artful-proposed > Reading package lists... Done > Building dependency tree > Reading state information... Done > Selected version '20170724+dfsg-1ubuntu0.1' (Ubuntu:17.10/artful-proposed > [all]) for 'qemu-slof' > Suggested packages: > qemu > The following packages will be upgraded: > qemu-slof > 1 upgraded, 0 newly installed, 0 to remove and 42 not upgraded. > Need to get 172 kB of archives. > After this operation, 1,024 B of additional disk space will be used. > Get:1 http://ports.ubuntu.com/ubuntu-ports artful-proposed/main ppc64el > qemu-slof all 20170724+dfsg-1ubuntu0.1 [172 kB] > Fetched 172 kB in 0s (240 kB/s) > (Reading database ... 62634 files and directories currently installed.) > Preparing to unpack .../qemu-slof_20170724+dfsg-1ubuntu0.1_all.deb ... > Unpacking qemu-slof (20170724+dfsg-1ubuntu0.1) over (20170724+dfsg-1) ... > Setting up qemu-slof (20170724+dfsg-1ubuntu0.1) ... > root@ubuntu:~# > > root@ubuntu:~# apt-get install qemu-slof/artful-proposed > Reading package lists... Done > Building dependency tree > Reading state information... Done > qemu-slof is already the newest version (20170724+dfsg-1ubuntu0.1). > Selected version '20170724+dfsg-1ubuntu0.1' (Ubuntu:17.10/artful-proposed > [all]) for 'qemu-slof' > 0 upgraded, 0 newly installed, 0 to remove and 42 not upgraded. Sorry one correction: > Booted the VM successfully. > > Applied artful proposed fixes and could able to boot the guest successfully. > I could NOT able to apply slof fixes from artful-proposed and still see the issue on artuful guest. Please help on how to apply the fix from artful-proposed to validate the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734856 Title: Can't boot VM with more than 16 disks (slof buffer issue) To manage notifications about this bug go to: https://bugs.launchpad.net/slof/+bug/1734856/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
