Public bug reported: == Comment: #0 - DAVID A. DUBETSKY <[email protected]> - 2015-08-12 14:03:09 == ---Problem Description--- I'm having a time difficult getting an Ubuntu 14.04.3 VM to build on a Firestone 8335/GCA running PKVM 3.1 using the Kimchi interface to build the Ubuntu VM.
Server FW - Linux AMI70E284140125 2.6.28.10-ami #1 Mon Jul 6 12:29:15 EDT 2015 1527a Power KVM Version - Linux 3.18.17-340.el7_1.pkvm3_1_0.2400.1.ppc64le Ubuntu Server ppc64el version - I've tried both the latest daily build from http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/ and the latest 14.04.3 LTS from http://cdimage.ubuntu.com/releases/14.04.3/release/ The problem I'm having is what looks like a hang during the initial iso boot at the point shown in the attached .jpg. I'm not convinced it's hanging but maybe redirecting the console? I'll supply any additional information that may be needed and I appreciate any help. Thanks. Contact Information = David Dubetsky/[email protected] Brian Croswell/[email protected] ---uname output--- Linux p215n133 3.18.17-340.el7_1.pkvm3_1_0.2400.1.ppc64le #1 SMP Tue Jul 21 11:25:45 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335/GCA - Firestone ---boot type--- CDROM / ISO image ---Install repository type--- /var/lib/libvirt/images ---Point of failure--- Other failure during installation (stage 1) == Comment: #1 - DAVID A. DUBETSKY <[email protected]> - 2015-08-12 14:05:31 == == Comment: #4 - Chandan Kumar <[email protected]> - 2015-08-14 13:09:09 == Fails with Kimchi but installation is successful with console. So the issue is specific to Kimchi. Looking at qemu log I could find that VM you tried to create was "p215vm152trusty", So I tried to boot. The installation started once I connected to guest console. Installation completed successfully. ================================ [root@p215n133 ~]# virsh list --all Id Name State ---------------------------------------------------- - p215vm152 shut off - p215vm152trusty shut off - p215vm152ub shut off - p215vm152ub02 shut off [root@p215n133 ~]# virsh start --console p215vm152trusty Domain p215vm152trusty started Connected to domain p215vm152trusty Escape character is ^] SLOF ********************************************************************** QEMU Starting Build Date = Jul 17 2015 09:38:50 FW Version = mockbuild@ release 20150716 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/v-scsi@2000 SCSI: Looking for devices 8002000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." Populating /vdevice/vty@30001000 Populating /vdevice/nvram@71000000 Populating /pci@800000020000000 00 7800 (D) : 1033 0194 serial bus [ usb-xhci ] 00 2000 (D) : 1234 1111 qemu vga 00 1800 (D) : 1af4 1002 unknown-legacy-device* 00 1000 (D) : 1af4 1001 virtio [ block ] 00 0800 (D) : 1af4 1000 virtio [ net ] No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB XHCI: Initializing No console specified using hvterm Welcome to Open Firmware Copyright (c) 2004, 2011 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 Trying to load: from: /pci@800000020000000/scsi@2 ... E3404: Not a bootable device! Trying to load: from: /vdevice/v-scsi@2000/disk@8002000000000000 ... Successfully loaded GNU GRUB version 2.02~beta2-9ubuntu1.3 +----------------------------------------------------------------------------+ |*Install | | Rescue mode | | | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. ????????????????????????? [!!] Select a language ?????????????????????????? ? ? ? Choose the language to be used for the installation process. The ? ? selected language will also be the default language for the installed ? ? system. ? ? ? ? Language: ? ? ? ? C ? ? English ? ? ? ? <Go Back> ? ? ? ??????????????????????????????????????????????????????????????????????????? <Tab> moves; <Space> selects; <Enter> activates buttons ====== ====== ====== ==== ??????????????????????? Finishing the installation ???????????????????????? ? ? ? 96% ? ? ? The system is going down NOW!ystem... ? Sent SIGTERM to all processes ? Sent SIGKILL to all processes???????????????????????????????????????????????? Requesting system reboot [ 1097.954184] reboot: Restarting system SLOF ********************************************************************** QEMU Starting Build Date = Jul 17 2015 09:38:50 FW Version = mockbuild@ release 20150716 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/v-scsi@2000 SCSI: Looking for devices 8002000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." Populating /vdevice/vty@30001000 Populating /vdevice/nvram@71000000 Populating /pci@800000020000000 00 7800 (D) : 1033 0194 serial bus [ usb-xhci ] 00 2000 (D) : 1234 1111 qemu vga 00 1800 (D) : 1af4 1002 unknown-legacy-device* 00 1000 (D) : 1af4 1001 virtio [ block ] 00 0800 (D) : 1af4 1000 virtio [ net ] Installing QEMU fb Scanning USB XHCI: Initializing No console specified using hvterm Welcome to Open Firmware Copyright (c) 2004, 2011 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 Trying to load: from: /pci@800000020000000/scsi@2 ... Successfully loaded error: no suitable video mode found. error: failure writing sector 0x2468fa8 to `ieee1275/disk'. Press any key to continue... OF stdout device is: /vdevice/vty@30001000 Preparing to boot Linux version 3.19.0-25-generic (buildd@fisher03) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #26~14.04.1-Ubuntu SMP Fri Jul 24 21:17:43 UTC 2015 (Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2) Detected machine type: 0000000000000101 Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-25-generic root=UUID=ed815f5b-1518-4385-83bf-36146ac38774 ro splash quiet vt.handoff=7 memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000004d00000 Ubuntu 14.04.3 LTS ubuntu hvc0 ubuntu login: ubuntu Password: Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.19.0-25-generic ppc64le) * Documentation: https://help.ubuntu.com/ 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. ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ ls / bin dev home lib64 media opt root sbin sys usr boot etc lib lost+found mnt proc run srv tmp var ubuntu@ubuntu:~$ pwd /home/ubuntu ubuntu@ubuntu:~$ ============================== [root@p215n133 ~]# ps -ef | grep qemu-system qemu 61359 1 16 02:22 ? 00:06:05 /usr/bin/qemu-system-ppc64 -name p215vm152trusty -S -machine pseries-2.4,accel=kvm,usb=off -m 123648 -realtime mlock=off -smp 160,sockets=1,cores=20,threads=8 -numa node,nodeid=0,cpus=0-159,mem=123648 -uuid 07b316eb-f68f-4b76-abb5-bceab097aecc -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/p215vm152trusty.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=/var/lib/libvirt/images/07b316eb-f68f-4b76-abb5-bceab097aecc-0.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/trusty-server-ppc64el.iso,if=none,id=drive-scsi0-0-0-2,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun= 2,drive=drive-scsi0-0-0-2,id=scsi0-0-0-2,bootindex=2 -netdev tap,fd=28,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:2e:45:23,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x30001000 -device usb-mouse,id=input0 -device usb-kbd,id=input1 -device usb-tablet,id=input2 -vnc 127.0.0.1:0 -device VGA,id=video0,vgamem_mb=16,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -msg timestamp=on root 62071 61320 0 02:58 pts/0 00:00:00 grep --color=auto qemu-system [root@p215n133 ~]# == Comment: #5 - Chandan Kumar <[email protected]> - 2015-08-14 13:16:17 == == Comment: #6 - Chandan Kumar <[email protected]> - 2015-08-14 13:16:56 == == Comment: #8 - Leonardo Augusto Guimaraes Garcia <[email protected]> - 2015-10-04 22:33:17 == >From what I am reading here, I don't think it is a Kimchi issue. Ubuntu is redirecting the console output to the serial console, even though Kimchi correctly setup the VGA console through VNC. >From dmesg, I got the following kernel command line: [ 0.000000] Kernel command line: root=/dev/mapper/ibmpkvm_vg_root- ibmpkvm_lv_system ro console=tty0 console=hvc0 crashkernel=1024M rd.retry=720 rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_swap rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_var rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_system rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_data Notice that we have two console entries: console=tty0 console=hvc0 The first one is the graphical console. The last one is the serial console. The kernel enables all the consoles pointed through the kernel command line. However, only the last one will receive input/output during kernel boot. All the other consoles will be enabled after the boot. During the installation process, however, the distro installer usually only shows output on the last console specified on the kernel command line, as this is the one where users would usually be expecting to interact with the installation process. When Ubuntu detects a graphical adapter on Power, it should enable the graphical installer. If the graphical installer works on Power, it should be enabled if you exchange the position of the two console parameters on the kernel command line: console=hvc0 console=tty0 == Comment: #11 - Chandan Kumar <[email protected]> - 2015-11-04 06:32:37 == (In reply to comment #8) > From what I am reading here, I don't think it is a Kimchi issue. > > Ubuntu is redirecting the console output to the serial console, even though > Kimchi correctly setup the VGA console through VNC. > > From dmesg, I got the following kernel command line: > > [ 0.000000] Kernel command line: > root=/dev/mapper/ibmpkvm_vg_root-ibmpkvm_lv_system ro console=tty0 > console=hvc0 crashkernel=1024M rd.retry=720 > rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_swap > rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_var > rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_system > rd.lvm.lv=ibmpkvm_vg_root/ibmpkvm_lv_data > > Notice that we have two console entries: > > console=tty0 console=hvc0 > > The first one is the graphical console. The last one is the serial console. > The kernel enables all the consoles pointed through the kernel command line. > However, only the last one will receive input/output during kernel boot. All > the other consoles will be enabled after the boot. During the installation > process, however, the distro installer usually only shows output on the last > console specified on the kernel command line, as this is the one where users > would usually be expecting to interact with the installation process. > > When Ubuntu detects a graphical adapter on Power, it should enable the > graphical installer. If the graphical installer works on Power, it should be > enabled if you exchange the position of the two console parameters on the > kernel command line: > > > console=hvc0 console=tty0 Leonardo, As suggested I tested adding kernel params 'console=hvc0 console=tty0' in the guest kernel param (these params were missing in distro provided grub.cfg), and then the guest could be accessed using serial console as well as kimchi graphical console, however on removing params 'console=hvc0 console=tty0' in the guest kernel only serial console works while the graphical console is stuck as shown in the attached screenshot. So, this does not look like kimchi issue instead kernel parameters should be taken care by the installer. Let me know if bug can be raised with ubuntu to get it the console params included in installer. Thanks, ** Affects: debian-installer (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64 bugnameltc-128947 severity-medium targetmilestone-inin--- ** Tags added: architecture-ppc64 bugnameltc-128947 severity-medium targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513108 Title: Ubuntu 14.04.3 VM fails to install using Kimchi from PowerKVM 3.1 on Firestone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1513108/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
