>> * In some of the timing runs on this system, the "real time" reported by >> the time command was off by 10 to 11 times. Issues were found in >> the messages file that seemed to relate to this including HUGE time >> adjustments by NTP and kernel hrtimer 'interrupt too slow' messages. >> This specific problem seems to be intermittent. > This is on the host? It can easily ruin your day. This was in the guest. >> System: >> SGI XE270, 8-core, Xeon X5570 (Nehalem), Hyperthreading turned off > Shoot, was about to blame hyperthreading. I'll keep it off for the next attempted run. > kvm guests should have an accurate clock without ntp in the guest > (/sys/.../current_clocksource should say 'kvmclock'). OK thanks. > Can you post kvm_stat output during the run? Sure, I'll try to get time on the system again next week and post in to the thread again. We'll still have the issue with the non-sequential nodes and incorrect representation of memory for this two-socket Nehalem system. I don't think that patch has made it in to the kernel. Thanks for replying back. If you have any other things you'd suggest trying, I'm game to give it a whirl. Someone suggested trying to export a whole PCI device to the guest. I won't be able to do that on this machine, maybe later when I have physical access to the system. Besides, that exercise might not poke at what I'm interested in anyway. Others suggested some potential settings EPT (Extended Page Table) and VPID (Virtual Path Identifier?) but I don't see where these settings are exposed (they aren't, for example, in this system's BIOS). More to come then. Thanks. Erik -- 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
