https://bugzilla.kernel.org/show_bug.cgi?id=203837
Paul Mackerras (pau...@ozlabs.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pau...@ozlabs.org
--- Comment #1 from Paul Mackerras (pau...@ozlabs.org) ---
I have tried but not succeeded in replicating this problem.
I have tried 5.2-rc3 in the host with the config I usually use, plus 5.2-rc3 in
the guest with that same config. That boots just fine.
With 5.2-rc3 in the host and my usual config, and 5.2-rc3 in the guest compiled
with the config attached to this bug, the guest gets a kernel panic due to
being unable to mount root. It looks like it never manages to load virtio-blk
for some reason.
With the config attached to this bug, I did once see the guest stop outputting
messages after the message about bringing up CPUs. The host was still running
just fine, and top in the host showed the qemu-system-ppc64 process using 100%
of a CPU, consistent with the guest being in an infinite loop.
I think we need more details about the machine where the crash is occurring -
host kernel config, details of VM config (qemu command line or libvirt xml),
etc.
--
You are receiving this mail because:
You are watching the assignee of the bug.
