Thanks. I'm afraid the status for "cannot be reproduced" is "invalid".
If you see this happening again, please do re-open this bug.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Changed in: qemu (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: qemu (Ubun
Apologies for the delay. I can't even seem to reproduce the original
issue on the affected hardware before upgrading, so I can't confirm the
fix in vivid or wily.
I'd be fine with closing this "can (no longer) reproduce"—maybe my
recollection is playing funny tricks on me.
--
You received this
Ping - can you confirm whether this is an issue still in vivid or wily?
** Changed in: qemu (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1
Could you confirm that this is still an issue in vivid?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1398718
Title:
Live migration locks up Linux 3.2-based guests
To manage notifica
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed
