** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in “linux” package in Ubuntu:
Confirmed
Status in “qemu”
dup of #1332409?
seems to be a 3.13 only bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in QEMU:
New
Status in “linux” packag
I need to amend comment #39, moving from 3.13.0-30 to 3.13.0-27 did not
eliminate the problem. It would seem that it takes a couple of hours
following a reboot for the symptoms to manifest with 3.13.0-27.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Quoting Ondergetekende (1307...@bugs.launchpad.net):
> We've resolved our issues by disabling KSM on the affected nodes. All of
> the non-affected nodes didn't have KSM enabled (due to a packaging bug
> elsewhere). After disabling KSM, our problems went away gradually in ~3
> days.
>
> This means
We've resolved our issues by disabling KSM on the affected nodes. All of
the non-affected nodes didn't have KSM enabled (due to a packaging bug
elsewhere). After disabling KSM, our problems went away gradually in ~3
days.
This means we're no longer affected by this issue (and given the other
repor
I can confirm that rolling back to 3.13.0-27 from 3.13.0-30 alleviated
my symptoms.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in
I believe I have the same problem, place a guest under any amount of
load, let's say 'yum upgrade' and the network stack goes out to lunch
for 1-5 seconds. Here is a sample of the ping statistics (host to
guest) from doing such an operation on a 3.13.0-30.55 kernel:
213 packets transmitted, 213 r
Ondergetekende: Physically is there *anything* different between the nodes in
your #33 that exhibited no errors and those that exhibited a lot? CPU
model/vendor, number of sockets, system vendor etc?
(I'm wondering about a synchronised/unsynchronised tsc type issue).
--
You received this bug
We haven't been able to reproduce the issues under lab conditions, and
I'm not willing to use our production setup as a guinypig anymore. These
issues have cost me too much credibility already.
We believe #1326367 is causing this, as we've bisected this issue to be
between 3.13.0-27.50 and 3.13.0-
I'm not confident yet we're seeing the exact same problem, but it is
pretty close. We're running a somewhat wide range of hyperisor kernels,
these are our observations so far.
node-1-1 3.13.0-24-generic is affected for 0% of vms
node-1-3 3.13.0-24-generic is affected for 0% of vms
node-1-5 3.
Note that my list of affected nodes also include migrated VMs, so there
are some false positives (VMs that came from an affected node). The
affected VMs on node 1-8 all seem to be migrated from another node.
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Ondergetekende, can you provide further details to why you believe Bug
#1326367 is causing this? Would you be willing to test a
3.11.0-24-generic kernel (reported stable) + the futex fix, or a chosen
stable version of the 3.13 or 3.15 kernel with just the futex fix. To
verify that the futex fix is
Thanks, that's great to know!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in QEMU:
New
Status in “linux” package in Ubuntu:
Co
I can confirm that it's more kernel issue than qemu. I run kernel
3.11.0-24-generic which is left after upgrade from Saucy and have no
issues for at least two days. Before that with current 3.13.0-30-generic
kernel my Windows guests crashed every 3-4 hours.
--
You received this bug notification b
After installing kernel 3.15.1-031501-generic from kernel-ppa, both
machines work without issues from 2014-06-25. Seems it's kernel issue
that have already been solved upstream.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
Status in QEMU:
New
St
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 июня 30 18:31 seq
crw-rw 1 root audio 116, 33 июня 30 18:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Au
Thanks, the soft lockup message in that dmesg may be helpful. Marking
as affecting the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.
** Attachment added: "dmesg of precise guest while hanging"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1307473/+attachment/4137970/+files/dmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
I have the same symptoms with two trusty-amd64 virtual hosts:
* win2003, linux guests hang for a period of time (~5 seconds, half of a
minute and more)
* win2008 blue screen with the same message
This happens with kernels (host):
Linux vsrv7 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16
Also, seems that these bugs are DUPs:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308341
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332409
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/
It seem to be related to
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1291321, there is
solution for Windows VM there.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
gues
Both systems I mentioned above were upgraded from precise to trusty.
After reinstalling them with clean install issue disappear and VMs are
not crashing anymore.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
So the only thing you ran under taskset was the program in comment #1?
And if you do not run that under taskset, then it doesn't skip?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1307473
Title:
just to clarify, i was pinning my test code inside the guest with
"taskset -c 1". There was no pinning on the host side.
Also, i see the same issue with -smp 2.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
Reproduced just as easily with qemu.org git HEAD.
Again, this appears to only be a case when using -smp 4 while locking to
1 cpu with cpuset.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which
27 matches
Mail list logo
