----- Messaggio originale ----- > Da: "Chris J Arges" <chris.j.arges@xxxxxxxxxxxxx> > A: "Paolo Bonzini" <pbonzini@xxxxxxxxxx>, kvm@xxxxxxxxxxxxxxx > Inviato: Mercoledì, 27 agosto 2014 23:24:14 > Oggetto: kvm-unit-test failures (was: [PATCH 1/2 v3] add check parameter to run_tests configuration) > > <snip> > > Thanks, looks good. Are there more failures? > > > > Paolo > > > > Paolo, > Thanks for applying those patches! > > I now only see the two failures on my machine: > model name : Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz > > I'm running with the tip of kvm master: > 0ac625df43ce9d085d4ff54c1f739611f4308b13 (Merge tag 'kvm-s390-20140825') > > sudo ./x86-run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline | > grep -v PASS > qemu-system-x86_64 -enable-kvm -device pc-testdev -device > isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio > -device pci-testdev -kernel x86/apic.flat -smp 2 -cpu > qemu64,+x2apic,+tsc-deadline > enabling apic > enabling apic > paging enabled > cr0 = 80010011 > cr3 = 7fff000 > cr4 = 20 > apic version: 1050014 > x2apic enabled > FAIL: tsc deadline timer clearing > tsc deadline timer enabled This is fixed in kvm/next (3.18). > SUMMARY: 16 tests, 1 unexpected failures > Return value from qemu: 3 > > sudo ./x86-run x86/kvmclock_test.flat -smp 2 --append "10000000 `date +%s`" > qemu-system-x86_64 -enable-kvm -device pc-testdev -device > isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio > -device pci-testdev -kernel x86/kvmclock_test.flat -smp 2 --append > 10000000 1409174399 > enabling apic > enabling apic > kvm-clock: cpu 0, msr 0x:44d4c0 > kvm-clock: cpu 0, msr 0x:44d4c0 > Wallclock test, threshold 5 > Seconds get from host: 1409174399 > Seconds get from kvmclock: 1409173176 > Offset: -1223 Weird, your clock is 20 minutes behind in the VM than it is in the host. Is the offset always around -1200? What happens if you reboot? (I get 0, 1 or sometimes 2). Paolo -- 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
