By all means, feel free to provide me instructions on how to debug this
myself, so I can help others in the future, although I understand that
can be more time consuming. If anyone would rather prefer talking on
IRC, just let me know the network and channel. Thanks
--
You received this bug notifi
** Attachment added: "cmdline"
https://bugs.launchpad.net/qemu/+bug/1596579/+attachment/4691252/+files/cmdline
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1596579
Title:
segfault upon reboot
** Attachment added: "core backtrace"
https://bugs.launchpad.net/qemu/+bug/1596579/+attachment/4691251/+files/core_backtrace
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1596579
Title:
segfaul
The VM is fine until I issue a reboot on the guest OS, in this case it
happened right at [315765.858431]. That is, once I boot the host, the
guest starts fine, I am able to use the tape drive fine, but when I
reboot for whatever reason, I guess the segfault.
Is this enough or do you want the full
Running the debuginfo qemu-kvm rpm and attaching with gdb might be
interesting to get a backtrace from that segfault. Otherwise devices
getting stuck in D3 often mean they didn't return from a reset
correctly. Are we to assume that the VM died between the vfio-pci line
and the mptbase line and th
