Am 26.01.2016 um 11:13 schrieb Yang Zhang: > On 2016/1/26 15:22, Stefan Priebe - Profihost AG wrote: >> Hi, >> >> Am 26.01.2016 um 02:46 schrieb Han, Huaitong: >>> What is the host kernel version and host dmesg information? And does >>> the problem exist when you use latest kernel and QEMU to replace old >>> binary file? >> >> Guest and Host is both 4.1.15. You mean the complete dmesg output from >> host? >> >> What do you mean with replace old binary file? I haven't tested Kernel >> 4.4 as we use 4.1 as it is a long term stable kernel release. > > Have you seen this before? I mean use the old KVM like 3.10? Guest or host? To test with a guest would be quite easy. Downgrading the host is very difficult not sure if the hw is supported. > >> >> Stefan >> >>> On Mon, 2016-01-25 at 14:51 +0100, Stefan Priebe - Profihost AG wrote: >>>> Hi, >>>> >>>> while running qemu 2.4 on whestmere CPUs i'm pretty often getting >>>> this >>>> one while booting: >>>> [ 0.811645] Switched APIC routing to physical x2apic. >>>> [ 1.835678] ------------[ cut here ]------------ >>>> [ 1.835704] WARNING: CPU: 0 PID: 1 at >>>> arch/x86/kernel/apic/apic.c:1309 setup_local_APIC+0x284/0x340() >>>> [ 1.835714] Modules linked in: >>>> [ 1.835724] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.15+72-ph >>>> #1 >>>> [ 1.835731] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), >>>> BIOS rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014 >>>> [ 1.835743] ffffffffb69ffcea ffff88042d5e3d68 ffffffffb669c37b >>>> 0000000000000918 >>>> [ 1.835754] 0000000000000000 ffff88042d5e3da8 ffffffffb6080d67 >>>> ffff88042d5e3da8 >>>> [ 1.835765] 0000000000000001 0000000000000000 0000000000008000 >>>> 0000000000000000 >>>> [ 1.835777] Call Trace: >>>> [ 1.835789] [<ffffffffb669c37b>] dump_stack+0x45/0x57 >>>> [ 1.835799] [<ffffffffb6080d67>] warn_slowpath_common+0x97/0xe0 >>>> [ 1.835806] [<ffffffffb6080dca>] warn_slowpath_null+0x1a/0x20 >>>> [ 1.835813] [<ffffffffb603eeb4>] setup_local_APIC+0x284/0x340 >>>> [ 1.835824] [<ffffffffb6d7c29d>] apic_bsp_setup+0x5b/0xb0 >>>> [ 1.835832] [<ffffffffb6d79fa7>] >>>> native_smp_prepare_cpus+0x23b/0x295 >>>> [ 1.835842] [<ffffffffb6d6c1b9>] kernel_init_freeable+0xc7/0x20f >>>> [ 1.835853] [<ffffffffb668d5c0>] ? rest_init+0x80/0x80 >>>> [ 1.835860] [<ffffffffb668d5ce>] kernel_init+0xe/0xf0 >>>> [ 1.835870] [<ffffffffb66a2fe2>] ret_from_fork+0x42/0x70 >>>> [ 1.835877] [<ffffffffb668d5c0>] ? rest_init+0x80/0x80 >>>> [ 1.835891] ---[ end trace bdbe630a8de2832c ]--- >>>> [ 1.837613] Spurious LAPIC timer interrupt on cpu 0 >>>> [ 1.837957] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 >>>> [ 1.939574] smpboot: CPU0: Intel Westmere E56xx/L56xx/X56xx >>>> (Nehalem-C) (fam: 06, model: 2c, stepping: 01) >>>> [ 1.939630] Performance Events: unsupported p6 CPU model 44 no PMU >>>> driver, software events only. >>>> [ 1.950868] KVM setup paravirtual spinlock >>>> >>>> Greets, >>>> Stefan >>>> -- >>>> 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 >> -- >> 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 >> > > -- 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
