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
Server Team, which is subscribed to qemu in Ubuntu.
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:
#includesys/time.h
#includetime.h
#includestdio.h
#includestdint.h
#define
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
Server Team, which is subscribed to qemu in Ubuntu.
Public bug reported:
I noticed on 2 different systems that after upgrade from precise to latest
trusty VMs are crashing:
- in case of Windows VMs I'm getting BSOD with error message: A clock
interrupt was not received on a secondary processor within the allocated time
interval.
- On linux
