*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Fred, this bug is for STOP 0x101, not STOP 0x5c.
STOP 0x101 cannot be fixed by an upgrade. You have to disable the
watchdog using QEMU option hv_relaxed or the equivalent in libvirt.
--
You received this
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen STOP: 0x005c again on day 9. So it has not been
fixed by a kernel upgrade to 3.16.0-23-generic with above method from
askubuntu.com.
--
You received this bug notification because you ar
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same here, had issues with 3.13.0-44-generic, upgraded to
3.16.0-23-generic and the problem was solved. Followed this tutorial
http://askubuntu.com/questions/541775/how-can-i-install-ubuntu-14-10s-
kernel-in
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
** This bug has been marked a duplicate of bug 1346917
Using KSM on NUMA capable machines can cause KVM guest performance and
stability issues
--
You received this bug notification because you are a me
I confirm, like Jeff Wilson, that I had the same issue with 3.13 and got
resolved with 3.14.1.
I cannot right now test the kernel suggested in #46.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130747
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 w
** Tags added: ksm-numa-guest-freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
https://bug
I have resolved my problem by running kernel 3.14.1-031401 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/, Ubuntu
14.04 LTS. The host has been running solid for a good 24 hours with 1
Windows Server 2008 R2, 2 cpu, VM running and two additional VMs running
for three hours.
The
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
https://bugs.launchpa
dup of #1332409?
seems to be a 3.13 only bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
h
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 Ubuntu
Bugs, which is su
I have a similar or the same problem with my Windows Server 2008 R2
virtual machines. The virtual machine stops with a Blue Screen error
101, clock interrupt was not received on a secondary processor. The
error only occurs when the VM has 2 cpus. The error seems to occur when
the VM is some load
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage
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-
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
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 Ubuntu
Bugs, which is s
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.
Thanks, that's great to know!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
https://bugs.launc
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications a
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
g
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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 Ubuntu
Bugs, which is
However, you mention that you have your VM pinned to CPU 1, while the
command line is doing '-cpu 4'. When I run a VM with -cpu 4 locked to a
single physical cpu, it definately does not do well. I'm not sure
whether to call that a bug or mis-use.
Example:
cgm create cpuset qemu
cgm setvalue cpu
I tried using 2.0.0~rc1+dfsg-0ubuntu3, using a trusty livecd iso, using
the command
kvm -hda x.img -cdrom ubuntu-13.10-desktop-amd64.iso -m 1024 -realtime
mlock=off -smp 4,sockets=1,cores=4,threads=1 -rtc base=localtime
but still have not seen this.
--
You received this bug notification because
Great, thanks for the test case!
Tried this with current git.qemu.org git HEAD on a trusty
kernel, was not able to reproduce. Trying on another host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130
I left over night following simple app which runs inside linux VM (pinned to
CPU1). and displays how much ticks happened during the 1 second sleep. I found
several occasions where sleep was taking much longer.
code:
#include
#include
#include
#include
#define CPUSPEED 2533422000
static __inl
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about th
41 matches
Mail list logo
