qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Bug 1563887 <1563887@bugs.launchpad.net>,
	Mike Rushton <mike.rushton@canonical.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Date: Tue, 05 Apr 2016 18:10:51 -0500	[thread overview]
Message-ID: <20160405231051.589.41803@loki> (raw)
In-Reply-To: <20160405222224.19027.87452.malone@soybean.canonical.com>

Quoting Mike Rushton (2016-04-05 17:22:24)
> Sorry, I copied the wrong thing:
> 
> sudo qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::2222-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio
> ioctl(KVM_CREATE_VM) failed: 22 Invalid argument
> failed to initialize KVM: Invalid argument

Can you post the output of this from the host?

  cat /proc/cpuinfo | grep platform

If it reports "PowerNV" then things should be working, so the error
needs investigation.

If it reports "pSeries", then that's not a normally supported scenario
for running KVM (since your host is already running as virtualized
pSeries partition running on top of the pHyp hypervisor rather than
KVM). You *might* have KVM support via 'PR' mode as opposed to the normal
'HV' mode, but that's generally used to do nested virtualization on top
of a KVM HV guest. To do it on top of a pHyp guest partition is probably
not something that's been actively tested.

I'd assume you're using PowerNV host, but you mentioned "PowerVM"
earlier which is synonymous with pHyp, so it warrants confirming.

> 
> -- 
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1563887
> 
> Title:
>   qemu-system-ppc64 freezes on starting image on ppc64le
> 
> Status in QEMU:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
> Status in livecd-rootfs package in Ubuntu:
>   New
> Status in qemu package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an
>   image as part of the certification process. This on an IBM ppc64le in
>   PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There
>   is no error output.
> 
>   ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::2222-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio
>   WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
>            Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
>            Specify the 'raw' format explicitly to remove the restrictions.
> 
>   SLOF **********************************************************************
>   QEMU Starting
>    Build Date = Jan 29 2016 18:58:37
>    FW Version = buildd@ release 20151103
>    Press "s" to enter Open Firmware.
> 
>   Populating /vdevice methods
>   Populating /vdevice/vty@71000000
>   Populating /vdevice/nvram@71000001
>   Populating /vdevice/l-lan@71000002
>   Populating /vdevice/v-scsi@71000003
>          SCSI: Looking for devices
>             8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.5+"
>   Populating /pci@800000020000000
>                        00 1800 (D) : 1af4 1001    virtio [ block ]
>                        00 1000 (D) : 1af4 1001    virtio [ block ]
>                        00 0800 (D) : 106b 003f    serial bus [ usb-ohci ]
>                        00 0000 (D) : 1234 1111    qemu vga
>   No NVRAM common partition, re-initializing...
>   Installing QEMU fb
> 
>   Scanning USB
>     OHCI: initializing
>       USB Keyboard
>       USB mouse
>   No console specified using screen & keyboard
> 
>     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@3 ...
>   E3404: Not a bootable device!
>   Trying to load:  from: /pci@800000020000000/scsi@2 ...   Successfully loaded
>   Linux ppc64le
>   #31-Ubuntu SMP F
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6
>   ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
>   Uname: Linux 4.4.0-16-generic ppc64le
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: ppc64el
>   Date: Wed Mar 30 14:10:01 2016
>   KvmCmdLine:
>    COMMAND         STAT  EUID  RUID   PID  PPID %CPU COMMAND
>    kvm-irqfd-clean S<       0     0  1172     2  0.0 [kvm-irqfd-clean]
>    qemu-nbd        Ssl      0     0 13467     1  0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img
>    qemu-system-ppc Sl+   1000  1000 18973 18896  101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::2222-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio
>   Lsusb: Error: command ['lsusb'] failed with exit code 1:
>   ProcEnviron:
>    TERM=xterm
>    PATH=(custom, no user)
>    LANG=en_US.UTF-8
>    SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro
>   ProcLoadAvg: 1.08 0.94 0.58 2/616 19571
>   ProcLocks:
>    1: POSIX  ADVISORY  WRITE 886 00:13:381 0 EOF
>    2: POSIX  ADVISORY  WRITE 1339 00:13:528 0 EOF
>    3: FLOCK  ADVISORY  WRITE 1284 00:13:522 0 EOF
>    4: POSIX  ADVISORY  WRITE 2281 00:13:563 0 EOF
>    5: POSIX  ADVISORY  WRITE 1331 00:13:536 0 EOF
>   ProcSwaps:
>    Filename                             Type            Size    Used    Priority
>    /swap.img                               file         8388544 0       -1
>   ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016
>   SourcePackage: qemu
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   bootlist:
>    /pci@800000020000011/pci1014,034A@0/sas/disk@4068402c40
>    /pci@800000020000018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
>    /pci@800000020000018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
>    /pci@800000020000018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
>    /pci@800000020000018/ethernet@0,3:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
>   cpu_cores: Number of cores present = 8
>   cpu_coreson: Number of cores online = 8
>   cpu_smt: SMT=8
>   lscfg_vp: Error: [Errno 2] No such file or directory: 'lscfg'
>   lsmcode: Error: [Errno 2] No such file or directory: 'lsmcode'
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions
> 

  reply	other threads:[~2016-04-05 23:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160330141641.3353.24299.malonedeb@chaenomeles.canonical.com>
2016-03-31 18:12 ` [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le Serge Hallyn
2016-03-31 19:36 ` Mike Rushton
2016-04-01  0:42   ` Serge Hallyn
2016-04-01  4:48 ` Serge Hallyn
2016-04-01  4:58 ` Serge Hallyn
2016-04-01 15:30 ` Serge Hallyn
2016-04-01 16:56 ` Serge Hallyn
2016-04-02 14:33   ` Michael Roth
2016-04-03  5:14 ` Serge Hallyn
2016-04-03  5:43 ` Serge Hallyn
2016-04-03  6:00 ` [Qemu-devel] [Bug 1563887] Status changed to Confirmed Brad Figg
2016-04-04  5:21 ` [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le Serge Hallyn
2016-04-04 14:49 ` Mike Rushton
2016-04-04 17:12   ` Michael Roth
2016-04-04 16:34 ` Serge Hallyn
2016-04-04 16:40 ` Serge Hallyn
2016-04-05 18:10 ` Mike Rushton
2016-04-05 19:34   ` Serge Hallyn
2016-04-05 19:40   ` Michael Roth
2016-04-05 21:44 ` Mike Rushton
2016-04-05 21:47 ` Mike Rushton
2016-04-05 22:18   ` Michael Roth
2016-04-05 22:22 ` Mike Rushton
2016-04-05 23:10   ` Michael Roth [this message]
2016-04-06  3:46 ` Mike Rushton
2016-04-06 20:10 ` Serge Hallyn
2016-04-06 20:20 ` Scott Moser
2016-04-06 20:40 ` Mike Rushton
2016-04-06 20:43 ` Mike Rushton
2016-04-06 21:10 ` Scott Moser
2016-04-06 21:12 ` Scott Moser
2016-04-06 23:13 ` Serge Hallyn
2016-04-07 22:20 ` Jon Grimm
2016-04-08 19:16 ` Alberto Salvia Novella
2016-04-13  1:22 ` Ryan Harper
2016-04-13 14:38 ` Ryan Harper
2016-04-13 15:43 ` Michael Hohnbaum
2016-04-13 16:59 ` Jon Grimm
2016-04-13 17:45 ` Ryan Harper
2017-11-10 23:22 ` Robin H. Johnson
2017-11-13 13:08 ` ChristianEhrhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160405231051.589.41803@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=1563887@bugs.launchpad.net \
    --cc=mike.rushton@canonical.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).