The SLOF fix has been merged 1.5 years ago, so I assume this can be
marked as fixed now.
** Changed in: qemu
Status: New => Fix Released
--
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
https://patchwork.ozlabs.org/patch/1180363/ should fix it, a SLOF update for
QEMU is also posted
https://github.com/aik/qemu/tree/qemu-slof-20191022-branch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
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
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
Please provide the entire guest booting output, from slof till it is stuck.
Also please try with -smp 1. Thanks.
--
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
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
Oh... are you using the SLOF (guest firmware) image included in the qemu
tree, or is it coming from a separate package?
If it's from a separate package, that could be the problem - it needs to be
updated before that qemu patch is safe.
--
You received this bug notification because you are a
Ok, I just tried booting a guest with virtio-scsi and ic-mode=xics, and
I wasn't able to reproduce this problem.
Can you try simplifying your command line to see what options are needed
to trigger this?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** 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:
