Tested with latest upstream and found the issue is fixed,
# git log -1
commit dd3d2340c4076d1735cd0f7cb61f4d8622b9562d (HEAD -> master, tag:
v5.2.0-rc3, origin/master, origin/HEAD)
Author: Peter Maydell
Date: Tue Nov 24 22:13:30 2020 +
Update version for v5.2.0-rc3 release
Did a git bisect and the bad commit is
acbdb9956fe93f4669141f103cb543d3025775db is the first bad commit
commit acbdb9956fe93f4669141f103cb543d3025775db
Author: Cédric Le Goater
Date: Thu Aug 20 15:45:46 2020 +0200
spapr/xive: Allocate IPIs independently from the other sources
The
Public bug reported:
Env:
Host: Power9 HW ppc64le
# lscpu
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 24-31,40-159
Thread(s) per core: 4
Core(s) per socket:
@Greg,
Thanks for the patch, I see it already got applied into 5.2, tested and
works fine,
# git log -2 --oneline
1972794 (HEAD -> master) spapr: Clarify error and documentation for broken KVM
XICS
e1d322c (grafted, tag: v5.1.0-rc3, origin/master, origin/HEAD) Update version
for v5.1.0-rc3 rele
this section of table in particular,
https://www.qemu.org/docs/master/specs/ppc-spapr-xive.html#no-xive-
support-in-kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890290
Title:
PowerPC L2(neste
As per this the table https://www.qemu.org/docs/master/specs/ppc-spapr-
xive.html#kvm-negotiation
reported qemu error msg "KVM is too old to support
ic-mode=dual,kernel-irqchip=on" indicates the
guest os is legacy, but that's not the case here, whereas kernel levels are
near upstream which has s
Public bug reported:
Env:
HW: Power 9 DD2.3
Host L0: 5.8.0-rc5-g8ba4ffcd8
Qemu: 5.0.50 (v5.0.0-533-gdebe78ce14)
Libvirt: 6.4.0
L1: 5.8.0-rc5-ge9919e11e
qemu_version': '5.0.50 (v5.1.0-rc2-dirty)
libvirt_version': '6.4.0'
L2: 5.8.0-rc7-g6ba1b005f
1. boot a L2 KVM guest with `ic-mode=dual,kernel-ir
Documentation describing the current qemu behaviour is captured here,
https://www.mail-archive.com/qemu-devel@nongnu.org/msg726442.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821771
Title:
Thanks! Murilo, am able to boot with current master, tested with(commit
53ef8a92eb04ee19640f5aad3bff36cd4a36c250).
Regards,
-Satheesh
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866962
Title:
[
Any updates?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866962
Title:
[Regression]Powerpc kvm guest unable to start with hugepage backed
memory
Status in QEMU:
New
Bug description:
Curr
** Summary changed:
- Powerpc kvm guest unable to start with hugepage backed memory
+ [Regression]Powerpc kvm guest unable to start with hugepage backed memory
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
Public bug reported:
Current upstream qemu master does not boot a powerpc kvm guest backed by
hugepage.
HW: Power9 (DD2.3)
Host Kernel: 5.6.0-rc5
Guest Kernel: 5.6.0-rc5
Qemu: ba29883206d92a29ad5a466e679ccfc2ee6132ef
Steps to reproduce:
1. Allocate enough hugepage to boot a KVM guest
# cat /proc
Domain vm1 started
Connected to domain vm1
Escape character is ^]
Populating /vdevice methods
Populating /vdevice/vty@3000
Populating /vdevice/nvram@7100
Populating /pci@8002000
00 0800 (D) : 1af4 1000virtio [ net ]
00 1000 (D) : 1af4 10
Same observation with smp 1 even.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1847440
Title:
ppc64le: KVM guest fails to boot with an error `virtio_scsi: probe of
virtio1 failed with error -22`
Did try with the slof bin(-bios /usr/local/share/qemu/slof.bin) complied
with qemu tree also, same issue persists,
/home/sath/qemu/ppc64-softmmu/qemu-system-ppc64 \
-name guest=vm1,debug-threads=on \
-S \
-object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-vm1/master-key.
** Description changed:
PowerPC KVM Guest fails to boot on current qemu master, bad commit:
e68cd0cb5cf49d334abe17231a1d2c28b846afa2
Env:
- HW: IBM Power8
+ HW: IBM Power9
Host Kernel: 5.4.0-rc2-00038-ge3280b54afed
Guest Kernel: 4.13.9-300.fc27.ppc64le
Qemu: https://github.com/qemu/
Public bug reported:
PowerPC KVM Guest fails to boot on current qemu master, bad commit:
e68cd0cb5cf49d334abe17231a1d2c28b846afa2
Env:
HW: IBM Power8
Host Kernel: 5.4.0-rc2-00038-ge3280b54afed
Guest Kernel: 4.13.9-300.fc27.ppc64le
Qemu: https://github.com/qemu/qemu.git (master)
Libvirt: 5.4.0
Gu
- Forwarded message from Satheesh Rajendran
-
Date: Mon, 29 Jul 2019 11:22:50 +0530
From: Satheesh Rajendran
To: Greg Kurz
Cc: sathn...@linux.vnet.ibm.com, qemu-...@nongnu.org, qemu-devel@nongnu.org,
c...@kaod.org
Subject: Re: [Qemu-ppc] [Qemu-devel][PATCH 1/2
On Fri, Jul 26, 2019 at 01:49:00PM +0200, Greg Kurz wrote:
> On Fri, 26 Jul 2019 12:48:09 +0530
> sathn...@linux.vnet.ibm.com wrote:
>
> > From: Satheesh Rajendran
> >
> > Current acceptance test will not run in powerpc Little endian
> > environment due the
On Fri, Jul 26, 2019 at 10:40:44AM +0200, Cédric Le Goater wrote:
> On 26/07/2019 09:18, sathn...@linux.vnet.ibm.com wrote:
> > From: Satheesh Rajendran
> >
> > Add pseries linux boot console test
> >
> > $avocado --show=console run -t arch:ppc64le boot_l
On Fri, Jul 26, 2019 at 10:37:35AM +0200, Cédric Le Goater wrote:
> On 26/07/2019 09:17, sathn...@linux.vnet.ibm.com wrote:
> > From: Satheesh Rajendran
> >
> > This series attempt to add support for avocado acceptance
> > test for powerpc and adds linux console boot
++
> MAINTAINERS | 1 +
> 5 files changed, 388 insertions(+)
> create mode 100644 docs/specs/index.rst
> create mode 100644 docs/specs/ppc-spapr-xive.rst
> create mode 100644 docs/specs/ppc-xive.rst
Reviewed-by: Satheesh Rajendran
>
> diff --git
On Thu, May 16, 2019 at 10:32:15AM +0200, Greg Kurz wrote:
> On Thu, 16 May 2019 10:22:26 +0200
> Cédric Le Goater wrote:
>
> > On 5/16/19 9:45 AM, Satheesh Rajendran wrote:
> > > On Thu, May 16, 2019 at 09:36:57AM +0200, Greg Kurz wrote:
> > >> Let's s
On Thu, May 16, 2019 at 09:36:57AM +0200, Greg Kurz wrote:
> Let's suggest to the user how the machine should be configured to allow
> the guest to boot successfully.
>
> Suggested-by: Satheesh Rajendran
> Signed-off-by: Greg Kurz
> ---
> hw/ppc/spapr_hcall.c |4
t; not seem right to let the guest go on without a precise idea of the
> interrupt mode it asked for.
>
> Handle these cases as well.
>
> Reported-by: Satheesh Rajendran
> Signed-off-by: Greg Kurz
> ---
> hw/ppc/spapr_hcall.c | 24
&
On Tue, May 14, 2019 at 08:46:27AM +0200, Cédric Le Goater wrote:
> This documents the overall XIVE architecture and gives an overview of
> the QEMU models. It also provides documentation on the 'info pic'
> command.
>
> Signed-off-by: Cédric Le Goater
> ---
> docs/index.rst | 1 +
> docs/
** Tags added: compilation gcc9
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824528
Title:
qemu fails to compile on gcc 9 `error: taking address of packed member
of ‘struct ’ may result in an u
Sure, Thanks, using the workaround to proceed.
Good if each commit goes through a automated build test across different
platforms vs gcc versions.
Regards,
-Satheesh.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.laun
Public bug reported:
Qemu compilation fails with below error on ppc64le host with gcc 9(9.0.1
20190328)
repo: https://github.com/qemu/qemu.git
branch: master
commit e1be98540ee672ef93292b65a986055512237c35
CC net/dump.o
hw/usb/dev-mtp.c: In function ‘usb_mtp_write_metadata’:
hw/usb/dev-m
Tried to patch as below and it compiles fine, not sure if this is right
fix though,
# git diff
diff --git a/hw/usb/dev-mtp.c b/hw/usb/dev-mtp.c
index ebf210f..7d512e5 100644
--- a/hw/usb/dev-mtp.c
+++ b/hw/usb/dev-mtp.c
@@ -231,7 +231,7 @@ typedef struct {
char date_modified[0]; /*unused*/
Public bug reported:
KVM guest does not reflect numa distances configured through qemu
Env:
Host/Guest Kernel: 5.1.0-rc1-g72999bbdc
qemu : 3.1.90 (v2.8.0-rc0-18614-g278aebafa0-dirty) [repo:
https://github.com/dgibson/qemu; branch:ppc-for-4.1 ]
# git log -1
commit 278aebafa02f699857ca082d966bcbc0
Public bug reported:
Issue:
Qemu compilation fails with below error on ppc64le host with gcc 9,
repo(https://github.com/dgibson/qemu.git), branch(ppc-for-4.0), Commit
(0483e90393bac8546a1fbc95ab912a1e78e92b00)
CHK version_gen.h
CC block/nvme.o
block/nvme.c: In function ‘nvme_create_queu
Applied to ppc-for-3.1.
https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg01317.html
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
This commit https://lists.gnu.org/archive/html/qemu-
devel/2018-08/msg01281.html from ~bharata-rao, fixes the issue.
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Last good commit I could find, 2309832afdaf8d6451ebc2e81bace8eb8ea41293
where both vcpu hotplug and managed save sequence worked fine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1785972
Title:
v
Bisect result:
v3.0.0-rc0: vcpu hotplug crashes the domain -
https://bugs.launchpad.net/qemu/+bug/1780928, this commit fixes that
issue, b585395b655a6c1f9d9ebf1f0890e76d0708eed6 ppc/xics: fix ICP reset
path
v3.0.0-rc1- v3.0.0-rc4: hotplug crash bug fixed, but now we are hitting this
one.
--
Y
Public bug reported:
VM fails to start after vcpu hot un-plug, managedsave sequence
Host info:
Kernel: 4.18.0-rc8-2-g1236568ee3cb
qemu: commit 6ad90805383e6d04b3ff49681b8519a48c9f4410 (HEAD -> master, tag:
v3.0.0-rc4)
QEMU emulator version 2.12.94 (v3.0.0-rc4-dirty)
libvirt: commit 087de2f
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1780928
Title:
v2.12.0-2321-gb34181056c: vcpu hotplug crashes qemu-kvm with segfault
Status in QEM
Public bug reported:
vcpu hotplug crashes upstream qemu(v2.12.0-2321-gb34181056c), vcpu
hotplug works fine in v2.12.0-rc4.
Host: Power8, kernel: 4.18.0-rc2-00037-g6f0d349d922b
Guest: Power8, kernel: 4.18.0-rc3-00183-gc42c12a90545 (base image: fedora27
ppc64le)
/usr/share/avocado-plugins-vt/buil
libvirt compiled against 105bcdde76bc8c64f2d9aca9db684186a5e96e63
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1773753
Title:
virsh start, after virsh managed save hangs and vm goes to paused
st
Yes, tested again with below levels and not issue is not reproducible.
Issue is fixed!
qemu: 2.12.50 (v2.12.0-949-g392fba9f58-dirty)
host/guest kernel: 4.17.0-rc7-00045-g0512e0134582
libvirt:
Compiled against library: libvirt 4.4.0
Using library: libvirt 4.4.0
Using API: QEMU 4.4.0
Running hype
** Description changed:
PowerPC KVM guest does not emulate L2 and L2 caches for vCPU, it would
- be good to have them enabled if not any known issues/limitation already
- with PowerPC.
+ be good to have them emulated to guest if not any known
+ issues/limitation already with PowerPC.
Host E
Guest xml(cpu portion):
...
32
/machine
hvm
/home/kvmci/linux/vmlinux
root=/dev/sda2 rw console=tty0 console=ttyS0,115200
init=/sbin/init initcall_debug
...
Host lscpu:
# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s
Public bug reported:
PowerPC KVM guest does not emulate L2 and L2 caches for vCPU, it would
be good to have them enabled if not any known issues/limitation already
with PowerPC.
Host Env:
kernel: 4.17.0-rc7-00045-g0512e0134582
qemu: v2.12.0-923-gc181ddaa17-dirty
#libvirtd -V
libvirtd (libvirt) 4.
** Summary changed:
- virsh managed save fails with qemu version v2.12.0-813-g5a5c383b13-dirty on
powerpc
+ virsh start after virsh managed save hangs and vm goes to paused state with
qemu version v2.12.0-813-g5a5c383b13-dirty on powerpc
** Summary changed:
- virsh start after virsh managed sa
followed by further attempts saves the domains as reported but issue
still same.
#virsh managedsave avocado-vt-vm1
Domain avocado-vt-vm1 state saved by libvirt
# virsh start avocado-vt-vm1 hung
# virsh list --all
IdName State
--
with above patch compiled on top of latest upstream fails with below
error:
# virsh managedsave avocado-vt-vm1
error: Failed to save domain avocado-vt-vm1 state
error: internal error: guest unexpectedly quit
rest of the behaviour same..
# virsh start avocado-vt-vm1 gets hung
---crtl+c --> t
To recover from the failed state it requires below steps to be run.
# virsh destroy avocado-vt-vm1
Domain avocado-vt-vm1 destroyed
# virsh undefine --managed-save avocado-vt-vm1
Domain avocado-vt-vm1 has been undefined
--
You received this bug notification because you are a member of qemu-
deve
Public bug reported:
Host Env:
IBM Power8 with Fedora28 base with compiled upstream kernel, qemu, libvirt.
Host Kernel: 4.17.0-rc5-00069-g3acf4e395260
qemu-kvm(5a5c383b1373aeb6c87a0d6060f6c3dc7c53082b):
v2.12.0-813-g5a5c383b13-dirty
libvirt(4804a4db33a37f828d033733bc47f6eff5d262c3):
Guest Kern
18 at 06:46:19PM +0530, satheesh rajendran wrote:
> > On Tue, Mar 27, 2018 at 01:40:00PM +0100, Daniel P. Berrangé wrote:
> > > On Tue, Mar 27, 2018 at 06:08:00PM +0530, sathn...@linux.vnet.ibm.com
> > > wrote:
> > > > From: Satheesh Rajendran
> > &
On Tue, Mar 27, 2018 at 01:40:00PM +0100, Daniel P. Berrangé wrote:
> On Tue, Mar 27, 2018 at 06:08:00PM +0530, sathn...@linux.vnet.ibm.com wrote:
> > From: Satheesh Rajendran
> >
> > This commit 137b5cb6ab565cb3781d5337591e155932b4230e
> > refactors info cpus outpu
Upstream patch from David Gibson @ https://lists.nongnu.org/archive/html
/qemu-devel/2018-01/msg00587.html
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
ockets=1,maxcpus=2 \
-m 2048 -nographic -enable-kvm
/home/sath/images/hostos-ppc64le.qcow2 \
-monitor stdio -serial /dev/pts/7
QEMU 2.11.50 monitor - type 'help' for more information
(qemu) device_add host-spapr-cpu-core,id=core1,core-id=1
(qemu)
inside
Public bug reported:
./ppc64-softmmu/qemu-system-ppc64 -version
QEMU emulator version 2.11.50 (v2.11.0-254-gaf35267)
1. Boot a power8 compat mode guest power9 HW.
./ppc64-softmmu/qemu-system-ppc64 -machine
pseries,accel=kvm,max-cpu-compat=power8 -m 4096 /home/sath/images/guest.qcow2
-smp 1,maxc
On Mon, Dec 18, 2017 at 12:01:44PM +, Daniel P. Berrange wrote:
> On Mon, Dec 18, 2017 at 09:55:55AM -0200, Daniel Henrique Barboza wrote:
> >
> >
> > On 12/18/2017 08:59 AM, Daniel P. Berrange wrote:
> > > On Mon, Dec 18, 2017 at 08:53:18AM -0200, Daniel Henrique Barboza wrote:
> > > > qmp_c
Public bug reported:
Help content missing for newly added machine properties, it would be needed by
libvirt and other management layers to query to add support, Thanks.
max-cpu-compat,vsmt,modern-hotplug-events,resize-hpt
Steps:
1. Compile qemu @below commit
2. ./ppc64-softmmu/qemu-system-ppc6
56 matches
Mail list logo
