* Marcus (shadow...@gmail.com) wrote: > I can answer some of the questions. It's been 3 months or so since I > looked into it. I ended up disabling kvmclock from the qemu command > line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 guests. > Sending the guest to the BIOS CLI or PXE would not reproduce the > issue. I didn't attempt an array of qemu versions, but I can say that > it did occur on 1.7.0 and 1.6.1, with the host running kernel 3.10 or > 3.12. The CPUs are Intel E5-2650.
If you could test it with the latest 2.0.x-rc that would be interesting to know, since you have a setup where it fails for you. > As mentioned by others, the mode of reproduction is to launch the vm, > wait about an hour, and then try to migrate it > > Here's are example qemu command lines (as generated from libvirt with > the only difference being "<timer name='kvmclock' present='no'/>"): Out of interest what created the config file with kvmclock enabled? virt-manager doesn't seem to have done over here. Dave -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
