From: Ivan Warren via Qemu-devel <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: Ivan Warren <ivan@vmfacility.fr>
Subject: [Qemu-devel] [Bug 1829576] Re: QEMU-SYSTEM-PPC64 Regression QEMU-4.0.0
Date: Sun, 19 May 2019 15:52:23 -0000 [thread overview]
Message-ID: <155828114316.15638.7357231494953184129.malone@wampee.canonical.com> (raw)
In-Reply-To: 155812687142.26079.4364411221525864419.malonedeb@soybean.canonical.com
Same thing here using https://github.com/dgibson/qemu/commits/ppc-
for-4.1 ... It might be a completely different problem (athough it looks
like a MMU problem).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829576
Title:
QEMU-SYSTEM-PPC64 Regression QEMU-4.0.0
Status in QEMU:
New
Bug description:
I have been using QEMU-SYSTEM-PPC64 v3.1.0 to run CentOS7 PPC emulated
system. It stopped working when I upgraded to QEMU-4.0.0 . I
downgraded back to QEMU-3.1.0 and it started working again. The
problem is that my CentOS7 image will not boot up udner QEMU-4.0.0,
but works fine under QEMU-3.1.0.
I have an QCOW2 image available at
https://www.mediafire.com/file/d8dda05ro85whn1/linux-
centos7-ppc64.qcow2/file . NOTE: It is 15GB. Kind of large.
I run it as follows:
qemu-system-ppc64 \
-name "CENTOS7-PPC64" \
-cpu POWER7 -machine pseries \
-m 4096 \
-netdev bridge,id=netbr0,br=br0 \
-device e1000,netdev=netbr0,mac=52:54:3c:13:21:33 \
-hda "./linux-centos7-ppc64.qcow2" \
-monitor stdio
HOST: I am using Manjaro Linux on an Intel i7 machine with the QEMU
packages installed via the package manager of the distribution.
[jsantiago@jlsws0 ~]$ uname -a
Linux jlsws0.haivision.com 4.19.42-1-MANJARO #1 SMP PREEMPT Fri May 10 20:52:43 UTC 2019 x86_64 GNU/Linux
jsantiago@jlsws0 ~]$ cpuinfo
Intel(R) processor family information utility, Version 2019 Update 3 Build 20190214 (id: b645a4a54)
Copyright (C) 2005-2019 Intel Corporation. All rights reserved.
===== Processor composition =====
Processor name : Intel(R) Core(TM) i7-6700K
Packages(sockets) : 1
Cores : 4
Processors(CPUs) : 8
Cores per package : 4
Threads per core : 2
===== Processor identification =====
Processor Thread Id. Core Id. Package Id.
0 0 0 0
1 0 1 0
2 0 2 0
3 0 3 0
4 1 0 0
5 1 1 0
6 1 2 0
7 1 3 0
===== Placement on packages =====
Package Id. Core Id. Processors
0 0,1,2,3 (0,4)(1,5)(2,6)(3,7)
===== Cache sharing =====
Cache Size Processors
L1 32 KB (0,4)(1,5)(2,6)(3,7)
L2 256 KB (0,4)(1,5)(2,6)(3,7)
L3 8 MB (0,1,2,3,4,5,6,7)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1829576/+subscriptions
next prev parent reply other threads:[~2019-05-19 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 21:01 [Qemu-devel] [Bug 1829576] [NEW] PPC64 Regression QEMU-4.0.0 Jose Santiago
2019-05-17 21:13 ` [Qemu-devel] [Bug 1829576] Re: QEMU-SYSTEM-PPC64 " Jose Santiago
2019-05-17 21:20 ` Jose Santiago
2019-05-18 8:11 ` Mark Cave-Ayland
2019-05-18 20:20 ` Jose Santiago
2019-05-19 12:24 ` Ivan Warren via Qemu-devel
2019-05-19 14:06 ` Mark Cave-Ayland
2019-05-19 15:52 ` Ivan Warren via Qemu-devel [this message]
2019-07-17 15:04 ` Alex Bennée
2019-10-21 14:20 ` Jose Santiago
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=155828114316.15638.7357231494953184129.malone@wampee.canonical.com \
--to=qemu-devel@nongnu.org \
--cc=1829576@bugs.launchpad.net \
--cc=ivan@vmfacility.fr \
/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).