Am 14.11.11 11:24, schrieb Adi Kriegisch:
> Dear Tim,
>
>> thanks for your hint. I've noticed that too but it seems I have no
>> options regarding clocksource:
>>
>> tsc gives me the infamous "clock went backwards"-error with lockup
>> jiffies simply runs at about twice the speed it should
>> xen gives a stable time
> I see; do your Dom0's have a synchronized clock?
>
>> I've tried:
>>
>> Stock Debian 6 kernel 2.6.32
> I cannot say anything about the other kernels, but there is a related bug
> in the recent version of the Debian Squeeze kernel package version
> 2.6.32-38: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644604
>
> This is fixed in 2.6.32-39 which is pending in stable-proposed-updates. So
> if you're running any kernel from 2.6.32-38 in your DomU, you should
> consider upgrading to the kernel in s-p-o and try again.
I've tried. No success :(
I've gathered some more test cases:
1. start vm with 8 vcpus, migrate -> runs
2. start vm with 8 vcpus, reduce to 3 vcpus, migrate, raise to 8 vcpus
-> crash
3. start vm with 3 vcpus, raise to 8 vcpus, migrate, reduce to 3 vcpus
-> runs
4. start vm with 3 vcpus, raise to 8 vcpus, migrate, reduce to 3 vcpus
-> raise to 8 vcpus -> crash
Seems that whatever I try - raising cpus (or to be precise: taking them
online) after a migration occurred leads to a crash.
BTW: save/restore shows the same behaviour, so it's most likely not
related to migration but to sleep/wakeup CPUs.
regards
Tim
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home