Thank you very much for your quick reply.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1754605
Title:
ppc64 migration bad_dest test is failed with failed to connect to
socket
Status in QEMU:
Public bug reported:
On ppc64le machine the following test failed.
# QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 tests/migration-test V=1
/ppc64/migration/deprecated: OK
/ppc64/migration/bad_dest: qemu-system-ppc64: Failed to connect socket:
Connection refused
OK
/ppc64/migration/postcopy/
Thomas thanks for your hint about the configuration option named
"--enable-tcg-interpreter". By removing it the test case started working
fine.
[root@zzfp365-lp1 qemu]# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M
sun4u -prom-env 'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
Some times it's still puzzling, when I got the clean git tree still
seeing crash with correct OpenBIOS file.
[root@zzfp365-lp1 test]# git clone git://git.qemu.org/qemu.git
Cloning into 'qemu'...
remote: Counting objects: 349636, done.
remote: Compressing objects: 100% (66763/66763), done.
remote:
After talking to Mark Cave-Ayland over e-mail, to make sure I have the proper
versions of OpenBIOS binaries - removed the existing git tree and with a fresh
clone not seeing the 'qemu-system-sparc64' related crash.
Before cleanup I was seeing the crash all the times.
Thanks!!
--
You received th
The above problem is getting re-producible only with configure option
"--enable-crypto-afalg" This got introduced in between 2.9.1 and 2.10.0.
I will bisect it and update.
When I tried earlier with 2.9.1 it complained saying "--enable-crypto-afalg"
option is not available so I did with out it and
This test case was working till 2.10.0 and got broken in 2.10.1
I checked with 2.9.1, 2.10.0-rc2, 2.10.0-rc3, 2.10.0-rc4, 2.10.0
Working scenario:
# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M sun4u -prom-env
'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
OpenBIOS for Sparc6
Here is the md5sum of openbios-sparc64
# md5sum ./pc-bios/openbios-sparc64
15418a4c9429d9ee9c637701b94c7ffb ./pc-bios/openbios-sparc64
> Could you please check with the QEMU 2.10 release to see whether this is a
> regression or whether it was already failing there?
Sure, I will update here. Mo
Git head is at 299d1ea9bb56bd9f45f905125489bdd7d543a1aa
latest today
100% re-producible. This is different & working Power9 machine than the
other day.
# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M sun4u -prom-env
'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
OpenBIOS for S
Similar failure seen with the following test too.
# make check-qtest-sparc64 V=1
(cd /home/nasastry/qemu; printf '#define QEMU_PKGVERSION '; if test -n ""; then
printf '""\n'; else if test -d .git; then printf '" ('; git describe --match
'v*' 2>/dev/null | tr -d '\n'; if ! git diff-index --quiet
I could re-produce using the following command,
# MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} gtester -k
--verbose -m=quick tests/test-aio-multithread
TEST: tests/test-aio-multithread... (pid=116074)
/aio/multi/lifecycle:OK
Public bug reported:
git head is at fa73e146250181852c0915aa65df8d54d35485fa
configure with the following
./configure --enable-attr --enable-bsd-user --enable-cap-ng\
--enable-coroutine-pool --enable-crypto-afalg --enable-curl\
--enable-curses --enable-debug --enable-debug-info\
--enable-deb
This try is inspiration from tests/docker/test-full.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1729623
Title:
test-aio-multithread fails with 'Co-routine re-entered recursively'
Status in QEMU
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728661/+attachment/5000235/+files/test.img_1728661.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728661
Title:
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728657/+attachment/5000204/+files/test.img_1728657.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728657
Title:
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy.img
#
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728660/+attachment/5000223/+files/test.img_1728660.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728660
Title:
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728643/+attachment/5000185/+files/test.img_1728643.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728643
Title:
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached files named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# cp test.img copy
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached files named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# mv test.img copy
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728639/+attachment/5000182/+files/test.img.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728639
Title:
qemu-
** Attachment added: "test.img tarred"
https://bugs.launchpad.net/qemu/+bug/1728635/+attachment/5000176/+files/test.img.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728635
Title:
qemu-
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached file named test.img to a directory
2. And customize the following command to point to the above directory and run
the same.
# cp test.img copy.
** Attachment added: "images tar file"
https://bugs.launchpad.net/qemu/+bug/1728615/+attachment/5000141/+files/images.tar.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1728615
Title:
qemu-io
Public bug reported:
git is at HEAD a93ece47fd9edbd4558db24300056c9a57d3bcd4
This is on ppc64le architecture.
Re-production steps:
1. Copy the attached files named backing_img.file and test.img to a directory
2. And customize the following command to point to the above directory and run
the sam
from demsg:
[84831.506917] qemu-io[35971]: unhandled signal 11 at 0004 nip
7fffae20f7d4 lr 102d3ec8 code 30001
[84831.519551] qemu-io[35977]: unhandled signal 11 at 0004 nip
7fff9925f7d4 lr 102d3ec8 code 30001
[84831.634000] qemu-io[35990]: unhandle
Public bug reported:
Head is at 3d7196d43bfe12efe98568cb60057e273652b99b
Steps to re-produce:
1. git clone
./configure --enable-gcov --target-list=ppc64-softmmu
make
cd tests/qemu-iotests
2. export qemu binary, in my environment
export QEMU_PROG=/home/nasastry/qemu_gcov/ppc64-softmmu/qemu-system
qemu-iotest 194 also fails in the similar stack trace.
# ./check -qcow2 194
QEMU -- "/home/nasastry/qemu_gcov/ppc64-softmmu/qemu-system-ppc64"
-nodefaults -machine accel=qtest
QEMU_IMG -- "/home/nasastry/qemu_gcov/qemu-img"
QEMU_IO -- "/home/nasastry/qemu_gcov/qemu-io" --cach
from dmesg:
[81791.481930] qemu-system-ppc[28640]: unhandled signal 11 at 0004
nip 7fff9f82f7d4 lr 10e182fc code 30001
[81791.649081] qemu-system-ppc[28651]: unhandled signal 11 at 0004
nip 7fffbd94f7d4 lr 10e182fc code 30001
[81791.817591] qemu-sys
Public bug reported:
Head is at 3d7196d43bfe12efe98568cb60057e273652b99b
Steps to re-produce:
1. git clone
./configure --enable-gcov --target-list=ppc64-softmmu
make
cd tests/qemu-iotests
2. export qemu binary, in my environment
export QEMU_PROG=/home/nasastry/qemu_gcov/ppc64-softmmu/qemu-system
With the mentioned patch not seeing the Abort.
# ppc64-softmmu/qemu-system-ppc64 -S -machine bamboo,accel=kvm -device
pcie-pci-bridge
gtk initialization failed
warning: KVM does not support watchdog
Thanks!!
--
You received this bug notification because you are a member of qemu-
devel-ml, whic
** Summary changed:
- qemu crashes with signal 6 when tried with -machine bamboo,accel=kvm -device
pcie-pci-bridge
+ qemu crashes with signal 6 with assertion error `!mr->container' failed
** Summary changed:
- qemu crashes with signal 6 with assertion error `!mr->container' failed
+ qemu crash
Public bug reported:
Re-production steps:
git clone today's qemu git tree (4th Oct 2017)
./configure --target-list=ppc64-softmmu && make -j 8
Run the device-crash-test from scripts folder, seeing the following
error
INFO: running test case: machine=powernv binary=ppc64-softmmu/qemu-system-ppc64
Public bug reported:
Re-production steps:
git clone today's qemu git tree (4th Oct 2017)
./configure --target-list=ppc64-softmmu && make -j 8
Run the device-crash-test from scripts folder, seeing the following
error
INFO: running test case: machine=prep binary=ppc64-softmmu/qemu-system-ppc64
de
Public bug reported:
Re-production steps:
git clone today's qemu git tree (4th Oct 2017)
./configure --target-list=ppc64-softmmu && make -j 8
Run the device-crash-test from scripts folder, seeing the following
error
INFO: running test case: machine=bamboo binary=ppc64-softmmu/qemu-system-ppc64
(gdb) bt
#0 0x3fffb24beff0 in raise () at /lib64/libc.so.6
#1 0x3fffb24c136c in abort () at /lib64/libc.so.6
#2 0x3fffb2bcaa04 in g_assertion_message () at /lib64/libglib-2.0.so.0
#3 0x3fffb2bcab0c in g_assertion_message_expr () at /lib64/libglib-2.0.so.0
#4 0x101b85a0
Public bug reported:
Qemu crashes with error "hw/ppc/spapr_drc.c:417:spapr_drc_detach:
assertion failed: (drc->dev)" when memory hotplug and hotunplug was done
continuously.
Steps to re-produce:
1. git clone (today's i.e 19th Sept)
2. Bring up ppc64le guest with memory hotplug capabilities ( I us
On other machine with same OS and gcc level, it's working fine. Not getting
what went wrong in the machine where I can re-produce this issue.
I guess this bug can be closed. Thank you.
/ppc64/prom-env/pseries:
SLOF **
QEMU Sta
# md5sum ./pc-bios/slof.bin
db83598b28052e9c12972d86c37b0c69 ./pc-bios/slof.bin
Same as what you mentioned.
Will try to get a different machine and try. If the problem still
persists, I will check with Nikunj.
Thanks a lot for your time. I have learned many things while interacting
with you.
Strange,
# gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
OS is RHEL based.
# uname -
TEST: tests/prom-env-test... (pid=9915)
/ppc64/prom-env/mac99: OK
/ppc64/prom-env/g3beige: OK
/ppc64/prom-env/pseries: **
ERROR:tests/prom-env-test.c:42:check_
Public bug reported:
After fixing other bug,
https://bugs.launchpad.net/qemu/+bug/1713408
with the proposed patch
http://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg05357.html
When tried smp core and thread as negative numbers seeing the following
similar error. There is a need to fix f
I am using a Power9 machine.
# ppc64-softmmu/qemu-system-ppc64 -nographic -M pseries,accel=tcg
-nodefaults -serial stdio -prom-env 'use-nvramrc?=true' -prom-env
'nvramrc=." Hello World!" cr power-off'
SLOF **
QEMU Starting
Buil
Host was not loaded at that time. And can be re-producable all the times
GTESTER check-qtest-ppc64
**
ERROR:tests/prom-env-test.c:42:check_guest_memory: assertion failed (signature
== MAGIC): (0x7c7f1b78 == 0xcafec0de)
GTester: last random seed: R02S5625099e4ad7700238a4e83dbd6576e0
this is wit
Sure will do the changes and update. Seems one of my colleague did it already
(sent patch to devel list)
https://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg05345.html
I will pass your review comments to her for modification.
Thanks for your review.
--
You received this bug notification
** Patch added: "0001-cpu-don-t-allow-negative-max_cpus.patch"
https://bugs.launchpad.net/qemu/+bug/1713408/+attachment/4940056/+files/0001-cpu-don-t-allow-negative-max_cpus.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
The actual failure was the following
LINKtests/test-hmp
GTESTER check-qtest-ppc64
**
ERROR:tests/prom-env-test.c:42:check_guest_memory: assertion failed (signature
== MAGIC): (0x7c7f1b78 == 0xcafec0de)
GTester: last random seed: R02Sfb567618f7c703a032934c0c11e263c6
make: *** [check-qtest-
Public bug reported:
On ppc64le architecture machine the following test case Aborted and Core
dumped.
# tests/prom-env-test --quiet --keep-going -m=quick --GTestLogFD=6
**
ERROR:tests/libqtest.c:628:qtest_get_arch: assertion failed: (qemu != NULL)
Aborted (core dumped)
Steps to re-produce:
clone
The above I am referring from hw/ppc/spapr.c
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1713408
Title:
qemu crashes with "GLib-ERROR **: gmem.c" error when a negative value
passed to "maxcpus"
Public bug reported:
# ppc64-softmmu/qemu-system-ppc64 --nographic -vga none -machine
pseries,accel=kvm,kvm-type=HV -m size=20g -device virtio-blk-
pci,drive=rootdisk -drive file=/home/nasastry/avocado-fvt-wrapper/data
/avocado-
vt/images/pegas-1.0-ppc64le.qcow2,if=none,cache=none,id=rootdisk,form
3308 static const CPUArchIdList *spapr_possible_cpu_arch_ids(MachineState
*machine)
3309 {
3310 int i;
3311 int spapr_max_cores = max_cpus / smp_threads; << max_cpus is -ve
and spapr_max_cores will also be -ve
...
3321
3322 machine->possible_cpus = g_malloc0(sizeof(CPUArchIdLis
53 matches
Mail list logo
