Changing the status of this bug from 'expired' to 'confirmed', since all
the way up here in Ubuntu 20 land (in 2020), I have found this bug when
development testing my research OS. Random lockups and segfaults, after
which the CPU usage of the qemu-system-x86 process sticks at over 100%.
**
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
I believe I've found the fix for this issue on 3.13.
If you can, please test the kernel posted on comment #1 on this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917
Make sure KSM is enabled; and any workarounds for this bug are disabled.
If this fixes the issue for you, you are
Marking incomplete until requested testing is complete.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: ksm-numa-guest-perf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows guest unstable after random amount of time
To manage notifications about this bug go
Hey guys,
I'm facing the following problem with Trusty:
---
Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD):
https://bugs.launchpad.net/qemu/+bug/1338277
---
Maybe those problems are related to each other?!
Best,
Thiago
--
You received this bug notification
Tested with kernel - Linux 3.15.0-031500rc7-generic
After 24 hours there's no sign of the problem.
After watching numastat for a while I noticed that with the 3.13.0
kernel the allocated memory for qemu does a really sudden drop from 6GB
down to 2GB. QEMU then freezes with 100% CPU until the
Matthew Anderson, the next step would be to fully reverse commit bisect
in order to identify the fix commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
** Tags added: kernel-fixed-upstream-3.15-rc7
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows guest unstable after random amount of time
To manage
** 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
** Changed in: qemu (Ubuntu)
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows guest unstable after random amount of time
To manage
@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
Bugs,
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows guest
** 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
** 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
BIOS has now been updated
# sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
2.1c
04/22/2014
I've been able to reproduce the problem using a fresh Windows 2008R2
server image. The guest functions correctly for a period of time then
starts to 'freeze' for around 10 seconds
** Tags removed: bios-outdated
** Tags added: latest-bios-2.1c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows guest unstable after random amount of time
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322441
Title:
QEMU Windows
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
Matthew Anderson, thank you for reporting this and helping make Ubuntu better.
As per http://www.supermicro.com/products/motherboard/QPI/5500/X8DTT.cfm an
update to your BIOS is available. If you update to this following
https://help.ubuntu.com/community/BiosUpdate does it change anything? If
29 matches
Mail list logo
