Avi Kivity wrote:
On 06/01/2010 05:06 PM, Peter Lieven wrote:
avi, i do not know whats going on. but if i supply -cpu xxx,-kvmclock
the guest
still uses kvm-clock, but it seems bug #584516 is not triggered...
thats weird...
I guess that bug was resolved in qemu-kvm.git. Likely 1a03675db1, but
it appears to be part of 0.12 too, so not sure.
What qemu-kvm were you using previously?
i'm using qemu-kvm git from today (aa22e82).
bug #585113 seems to be fixed (this was the irq nobody cared error with
virtio_blk or e1000)
bug #584516 is still there, but if I set - cpu xxx,-kvmclock it is not
triggered. the guest
shows current_clocksource = kvm_clock, but migration seems to succeed
(at least the ~20
times i tested it since you told me about the flag)
do you have a clue what fixed bug #585113. i would like to backport it
to 0.12.4
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
