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
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
