** Changed in: qemu (Ubuntu)
Importance: High = Medium
--
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/1322441
Title:
QEMU Windows guest unstable after random amount of time
To
@penalvch, I'd suggest that since booting with the old 3.2 kernel
prevented this bug, this bug should still be marked as affecting the
kernel.
Lowering priority to medium since there is a workaround (technically 2)
--
You received this bug notification because you are a member of Ubuntu
Server
** Package changed: qemu (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
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/1322441
Title:
QEMU
** Description changed:
Ubuntu 14.04, all updates done as of 23/5/2014
Kernel : Linux 3.13.0-24-generic
Qemu : 1.7.1 and 2.0.0 tested
Tested using both Xeon 5620 and 5520 processors, 48GB RAM.
- Anywhere from 20 minutes for 3+ hours after booting Windows guests become
unstable. Guest
Matthew Anderson, did this problem not occur in a release prior to
Trusty?
** Package changed: linux (Ubuntu) = qemu (Ubuntu)
--
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/1322441
Not this exact problem but one with similar symptoms. From kernel 3.5
onwards there was a problem with guests not receiving RTC ticks which
was reported here - http://lists.gnu.org/archive/html/qemu-
devel/2013-02/msg03827.html
The 3.2 kernel from 12.04.1 never had any issues but the 3.5 kernel
** Changed in: qemu (Ubuntu)
Importance: Medium = High
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
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/1322441
Title:
Based on the fact that flush_tlb_page() appears to be taking up most of
the CPU time when QEMU is 'frozen' I started playing with memory
settings. Disabling automatic NUMA balancing appears to have solved the
problem. echo 0 /proc/sys/kernel/numa_balancing
The guest has been running 4+ hours now
