On Tue, Aug 2, 2011 at 12:24 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote: > FWIW, I've pushed my tree here: > > git://git.kiszka.org/qemu-kvm.git queues/cpu-hotplug > thanks. Your cpu-hotplug tree or today's git-master (commit dacdc4b10bafbb21120e1c24a9665444768ef999) works. Previously I tested the second system with master from the middle of last week (commit 497d8129ad4bca8a3b319ee84229d9a0f9cdd15c) which probably was missing something else in between merges. Apologies. > > Strange. Why does it still talk about kvm-clock? > I do get kvmclock dmesg output when onlining e.g. on the second system as well: [ 89.062098] Booting Node 0 Processor 1 APIC 0x1 [ 89.062100] smpboot cpu 1: start_ip = 98000 [ 89.074229] kvm-clock: cpu 1, msr 0:3fd12f81, secondary cpu clock [ 89.075038] NMI watchdog disabled (cpu1): hardware events not enabled [ 89.076103] Switched to NOHz mode on CPU #1 kvm_register_clock() prints the kvm-clock line, isn't this expected to be called when the new CPU is onlined? thanks, - Vasilis -- 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
