On 09/14/2010 12:40 PM, Jan Kiszka wrote:
>> For yet unknown reason, this commit breaks Linux guests here if they are >> started with only a single VCPU. They hang during boot, obviously no >> longer receiving interrupts. >> >> I'm using kvm-kmod against a 2.6.34 host kernel, so this may be a side >> effect of the wrapping, though I cannot imagine how. >> >> Anyone any ideas? >> >> > > Most likely, time went backwards, and some 'future - past' calculation > resulted in a negative sleep value which was then interpreted as > unsigned and resulted in a 2342525634 year sleep. Looks like that's the case on first glance at the apic state.
Aside from this bug, it would be better for the guest to use signed arithmetic (or check beforehand) and not sleep if the future is already past.
> > Does your guest use kvmclock, tsc, or some other time source? A kernel that has kvmclock support even hangs in SMP mode.
Does it have the recent kvmclock patches backported? (should be in latest -stable).
The others pick hpet or acpi_pm. TSC is considered unstable.
Wierd. But perhaps it's the scheduler clock that's misbehaving, IIRC it has its own local clock.
-- error compiling committee.c: too many arguments to function -- 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
