The problem is that Xfwm's built-in compositor and virgl don't play nice
together.
Work-around: Boot the VM with virgl=off (on the video device) or gl=off
(on the display), run xfwm4-tweaks-settings in the VM, select the
"Compositor" tab, and uncheck "Enable display compositing". Then shut
down t
On Wed, Jun 17, 2015 at 04:01:33PM +0200, Paolo Bonzini wrote:
> On 12/06/2015 16:10, Paul Donohue wrote:
> > To correct that problem, this commit resets the periodic timer after
> > loading from a snapshot or migration if the clock has either jumped
> > backward or has jumped
On Wed, Jun 17, 2015 at 04:00:06PM +0200, Paolo Bonzini wrote:
> On 12/06/2015 16:08, Paul Donohue wrote:
> > +static inline int64_t get_max_clock_jump(void)
> > +{
> > +// This should be small enough to prevent excessive interrupts from
> > being
> > +
the reset notification if the
host clock jumps forward by more than a hard-coded limit. The limit is
currently set to a value of 60 seconds, which should be small enough to
prevent excessive timer loops, but large enough to avoid frequent resets
in idle VMs.
Signed-off-by: Paul Donohue
timer in these cases.
Paul Donohue (2):
qemu-timer: Call clock reset notifiers on large forward jumps
mc146818rtc: Reset the periodic timer on resume from snapshot
hw/timer/mc146818rtc.c | 6 ++
include/qemu/timer.h | 9 +
qemu-timer.c | 2 +-
3 files changed, 16 insertions(+), 1 deletion(-)
.
To correct that problem, this commit resets the periodic timer after
loading from a snapshot or migration if the clock has either jumped
backward or has jumped forward by more than the clock jump limit that
is used by the reset notifier code in qemu-timer.
Signed-off-by: Paul Donohue
---
hw/
