Would it be possible to get a fixed QEMU version into the Xenial-Ocata
cloud archive?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching ceph volume to
I can confirm that upgrading from Xenial-Ocata to Xenial-Pike (both
Cloud Archive) solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching
@slashd It sounds really strange to me that I should wait til 20-Feb for
a fix for this bug while this is clearly a regression introduced with
the latest kernel upgrade. Is there no way to speed things up to fix
this regression.
Currently we had to downgrade all our xenial systems to linux-
I also posted the same report on the qemu-devel mailinglist. Maybe they have
any comments.
https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg02270.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
If memory statistics are enabled for the memory baloon device in libvirt
like this:
Then qemu exits with "qemu-system-x86_64: Virtqueue size exceeded" after
the VM is migrated or when starting the VM again after a managedsave.
This bug is present since
reopening and adding the requested apport crash log. I'm experienceing
the same bug one brand new ipod.
** Changed in: rhythmbox (Ubuntu)
Status: Invalid = Confirmed
** Attachment added: apport crash log
http://launchpadlibrarian.net/17059291/_usr_bin_rhythmbox.1000.crash
--
On Mon, Aug 25, 2008 at 12:43:30PM -, Pedro Villavicencio wrote:
Please do not attach .crash files to the reports, use the instructions i
said before to send one with apport rather, thanks.
Sorry, but I'm not sure if I understand this correctly. I tried that but
as far as I could see there
