For the record -- my time problems booting with the new kernel seem to be coming from the paravirtual clocksource (KVM_CLOCK) introduced in 2.6.26. Booting with "no-kvmclock" on the kernel command line makes things work OK. The next question to answer is whether this is an issue with the Intrepid kernel or the Hardy kvm...
For the record -- my time problems booting with the new kernel seem to be coming from the paravirtual clocksource (KVM_CLOCK) introduced in 2.6.26. Booting with "no-kvmclock" on the kernel command line makes things work OK. The next question to answer is whether this is an issue with the Intrepid kernel or the Hardy kvm...