The bug shows on the CRB boards as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
vhost=on
To manage notificati
Just an additional comment, running qemu-kvm with a 3part image (kernel,
initramfs and disk) does not yield a crash on 4.8 kernel, even when
enabling vhost. Similarly, running a guest with AAVMF and no vhost
behaves ok, it's the combination of the two that didn't work no matter
what guest, FW or AA
** Also affects: edk2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
ThunderX: soft lockup on
Launch script showing how to start qemu with AAVMF and vhost on. It
requires an AAVMF vars file, which can be a simple zero filled 64M data
file.
** Attachment added: "launch.sh"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1673564/+attachment/4839059/+files/launch.sh
--
You received
Serial console log, including debug messages from the Firmware and
kernel errors. Could not get dmesg output, I might try again.
** Attachment added: "console.log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1673564/+attachment/4839060/+files/console.log
--
You received this bug noti
Public bug reported:
This is a followup of an earlier thread/bug that we have narrowed down
to an incompatibility/issue with vhost support in qemu-efi. Without
vhost=on qemu seems to be working fine.
I have tested several edk2 firmwares:
- xenial
- zesty
- Fedora:
ftp://195.220.108.108/linux/fed
Hi,
The same bug happened again on a similar board with T27 firmware, but
this time running kernel 4.4.0-45-generic. I'm attaching log with serial
console (with debug info from the FW). I can't attach more because the
kernel hanged.
So far 4.4.0-45-generic was stable on our lab, this happened wit
Just one addition, the log before contains dmesg output too. The task
that hanged was systemd, it might be related with some VMs from the
previous boot record being restarted automatically, but it still doesn't
explain the crash.
Rebooting the node again with 4.4 did not result in kernel crash.
-
You might want to revisit this, I get the indicator for pidgin showing
but not the one for xchat. It looks like a bug to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309589
Title:
System tray