qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Ehrhardt " <1920784@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
Date: Tue, 23 Mar 2021 11:03:40 -0000	[thread overview]
Message-ID: <161649742102.1059.4589614275751872648.malone@soybean.canonical.com> (raw)
In-Reply-To: 161642496871.32717.8520198452991245606.malonedeb@soybean.canonical.com

Since this seems to be broken on all Distributions as soon as the triggering
combination of kernel/glibc is present I think we'd want to open that up to
upstream qemu for a wider discussion and to also hit the ppc64 architecture
experts.

Furthermore I'm not entirely sure if this needs to be fixed in qemu, it
might instead be the case that instead a fix is needed in glibc.

Therefore I'm adding a qemu (upstream) bug task for now to have the bug
reported there as well (might be worth for awareness anyway) - but
chances are that after some debugging it will turn out to become a glibc
issue instead.

If only I could break this test out of kvm ioctl into something simpler,
then we could then properly file against glibc ....

** Also affects: glibc (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: qemu
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1920784

Title:
  qemu-system-ppc64le fails with kvm acceleration

Status in QEMU:
  New
Status in The Ubuntu-power-systems project:
  New
Status in glibc package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  (Suspected glibc issue!)

  qemu-system-ppc64(le) fails when invoked with kvm acceleration with
  error "illegal instruction"

  > qemu-system-ppc64(le) -M pseries,accel=kvm

  Illegal instruction (core dumped)

  In dmesg:

  Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c,
  MSR=900000000280f033

  
  Version-Release number of selected component (if applicable):
  qemu 5.2.0 
  Linux kernel 5.11
  glibc 2.33
  all latest updates as of submitting the bug report

  How reproducible:
  Always

  Steps to Reproduce:
  1. Run qemu with kvm acceleration

  Actual results:
  Illegal instruction

  Expected results:
  Normal VM execution

  Additional info:
  The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also observed on a Raptor Blackbird with the same processor.

  This was also observed on Fedora 34 beta, which uses glibc 2.33
  Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with glibc 2.33
  Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: qemu-system 1:5.2+dfsg-6ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic ppc64le
  .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog'
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: ppc64el
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 22 14:48:39 2021
  InstallationDate: Installed on 2021-03-22 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el (20210321)
  KvmCmdLine: COMMAND         STAT  EUID  RUID     PID    PPID %CPU COMMAND
  ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro
  ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071
  ProcSwaps:
   Filename				Type		Size		Used		Priority
   /swap.img                               file		8388544		0		-2
  ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc (Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  acpidump:
   
  cpu_cores: Number of cores present = 8
  cpu_coreson: Number of cores online = 8
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions


       reply	other threads:[~2021-03-23 11:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <161642496871.32717.8520198452991245606.malonedeb@soybean.canonical.com>
2021-03-23 11:03 ` Christian Ehrhardt  [this message]
2021-03-23 11:04 ` [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration Christian Ehrhardt 
2021-03-23 11:05 ` Christian Ehrhardt 
2021-03-23 11:06 ` Christian Ehrhardt 
2021-03-23 11:14 ` Frank Heimes
2021-03-23 11:23 ` Christian Ehrhardt 
2021-03-23 14:37 ` Christian Ehrhardt 
2021-03-23 16:52 ` Laurent Vivier
2021-03-23 17:17 ` Laurent Vivier
2021-03-23 17:30 ` [Bug 1920784] Status changed to Confirmed Ubuntu Kernel Bot
2021-03-23 20:43 ` [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration Frank Heimes
2021-03-23 23:30 ` sadoon albader
2021-03-24  6:41 ` Christian Ehrhardt 
2021-03-24  6:44 ` Christian Ehrhardt 
2021-03-24 14:40 ` Frank Heimes
2021-03-24 15:32 ` Tim Gardner
2021-03-29  5:42 ` Thomas Huth

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=161649742102.1059.4589614275751872648.malone@soybean.canonical.com \
    --to=1920784@bugs.launchpad.net \
    --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).