Still a problem on 3.13.0-17-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status i
** Also affects: linux (Ubuntu Trusty)
Importance: Medium
Assignee: Stefan Bader (smb)
Status: Confirmed
** Also affects: qemu-kvm (Ubuntu Trusty)
Importance: Medium
Status: Confirmed
** Changed in: qemu-kvm (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You rec
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux”
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “lin
This bug was fixed in the package linux - 3.13.0-22.44
---
linux (3.13.0-22.44) trusty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1301562
[ dann frazier ]
* [Config] enable linux-tools on arm64
https://lists.ubuntu.com/archives/kernel-team/2014-April
See CurrentDmesg.txt for lots of errors such as:
[ 1688.474887] Call Trace:
[ 1688.474914] [] kvm_vcpu_ioctl+0x433/0x4d0 [kvm]
[ 1688.474924] [] ? wake_up_state+0xf/0x20
[ 1688.474931] [] ? wake_futex+0x65/0x90
[ 1688.474937] [] ? futex_wake+0x13d/0x160
[ 1688.474942] [] ? do_futex+0xeb/0x660
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 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 t
Alas, same issue using kernel 3.13.0-031300rc8-generic.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package i
Same problem with 3.13.0-4-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status in
Same problem with 3.13.0-4-generic. Any progress on this? kvm is
unusable due to this issue.
** Attachment added: "dmesg-3.13.0-4-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3952909/+files/dmesg-3.13.0-4-generic.txt
--
You received this bug notificat
dmesg from 3.13.0-5-generic kernel.
** Attachment added: "dmesg.3.13.0-5-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3954151/+files/dmesg.3.13.0-5-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Still a problem on 3.13.0-5-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Status in “linux” package in Ubuntu:
Confirmed
Status in
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a regre
I've had a number of lockups in the last 2 days since upgrading to
Trusty and trying to run a VM under kvm which look to match this issue.
System appears to become unresponsive/hang with what looks like some
kind of I/O lockup, cannot ls in a terminal etc before eventually
display freezes. syslog
@Gareth,
I suspect yours is a different bug, so it would be best if you file a
new bug (so that people trying to debug *this* bug don't mix up symptoms
in their minds, which can wrongly make them rule out a proper cause for
the other bug) against both qemu and linux.
In that bug, please let us kn
Serge has just identified that the trigger for this bug is running kvm
with '-net user': without this option, no issues.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Latest series of oopses running on a fully updated trusty system.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Same problem running with -vnc :7
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
To be clear, my host system is a 64-bit capable first-gen i7, but is
actually running fully 32-bit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running
Latest trusty desktop image (dated 24 Jan) results in the oops when
running with kvm as:
$ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
On my AMD laptop (x130e thinkpad) with a uptodate trusty amd64 install,
I cannot reproduce this. After installing a 32-bit trusty image, I can
in fact reproduce it:
Jan 27 13:07:05 serge-ThinkPad-X130e kernel: [ 725.593411] kvm: zapping shadow
pages for mmio generation wraparound
Jan 27 13:07:1
I wonder whether this could be remotely related to bug #1265841. I don'T have
any proof there. Just stumbled over some used_math check (followed by potential
init_fpu) right at the beginning of kvm_arch_vcpu_ioctl_run. There was a longer
thread on LKML about that ("[PATCH] Make math_state_restor
OK, its not related to the eager fpu stuff. Just reproduced the same lockup
with a test kernel that contained some potential fixes from upstream. The
interesting part of the backtraces is that the EIP is changing and often not in
a function that should be able to block.
So something seems to cau
I think the switch to 3.13 may have borked kvm for me. I'll try to
confirm that tomorrow...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running kvm
Sta
This looks to be drilling down to a problem which seems to only affect
i386 for some reason. But basically the kvm/qemu process gets into a
situation where the thread_info says "you have to reschedule" but the
per-cpu counterpart prevents that. Now the kvm/qemu process runs wildly
around between tr
26 matches
Mail list logo