From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: kvm@vger.kernel.org
Cc: ciprich@linuxbox.cz, zamsden@redhat.com
Subject: Re: 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0)
Date: Sun, 8 May 2011 20:41:55 +0200 [thread overview]
Message-ID: <20110508184154.GD2224@nik-comp.lan> (raw)
In-Reply-To: <20110508183303.GA7918@nik-comp.lan>
[-- Attachment #1: Type: text/plain, Size: 6072 bytes --]
(CC Zachary)
well, I should also note that while testing 2.6.37 host, I had Zach's
patch fixing guest clock regression applied...
n.
On Sun, May 08, 2011 at 08:33:04PM +0200, Nikola Ciprich wrote:
> Hello everyboy,
> while installing new virt machine today, I noticed that 2.6.32 x86_64 SMP guests are hanging if they have paravirt-clock enabled...
> Either they don't finish booting at all, or boot but hang soon after..
> Such a hanged guest fully loads all host cpus..
> The host is 6core x86_64 runnig 2.6.37.6 with 24GB RAM.
>
> kvm_stat:
>
> kvm_exit(EXTERNAL_INTERRUPT) 15682 1643
> kvm_exit 15514 1643
> kvm_entry 15416 1643
> kvm_set_irq 1 0
> kvm_msi_set_irq 1 0
> kvm_apic_accept_irq 1 0
> kvm_exit(VMCLEAR) 6 0
> kvm_exit(VMON) 6 0
> kvm_exit(PAUSE_INSTRUCTION) 5 0
> kvm_exit(MCE_DURING_VMENTRY) 5 0
> kvm_exit(MWAIT_INSTRUCTION) 5 0
> kvm_exit(DR_ACCESS) 5 0
> kvm_exit(EPT_VIOLATION) 5 0
> kvm_exit(NMI_WINDOW) 5 0
> kvm_exit(VMPTRLD) 5 0
> kvm_exit(TASK_SWITCH) 5 0
> kvm_exit(VMREAD) 5 0
> kvm_exit(VMLAUNCH) 5 0
> kvm_exit(RDPMC) 5 0
>
> perf top:
> 16.00 10.9% add_preempt_count [kernel.kallsyms]
> 16.00 10.9% do_raw_spin_lock [kernel.kallsyms]
> 15.00 10.2% sub_preempt_count [kernel.kallsyms]
> 8.00 5.4% irq_exit [kernel.kallsyms]
> 7.00 4.8% vmx_vcpu_run /lib/modules/2.6.37lb.09/kernel/arch/x86/kvm/kvm-intel.ko
> 7.00 4.8% page_fault [kernel.kallsyms]
> 5.00 3.4% mempool_free [kernel.kallsyms]
>
> info registers:
> RAX=0000000000f42400 RBX=ffffffff81533f00 RCX=0000000000000016 RDX=00077358f5000000
> RSI=000000001dcd6500 RDI=0000000000000001 RBP=ffff880009a03ee8 RSP=ffff880009a03ee8
> R8 =0000000000000016 R9 =000000000000000a R10=00000000ffffffff R11=0000000000000000
> R12=2a4d17d38f3303c1 R13=ffffffff815fd000 R14=ffffffff81592140 R15=0000000000093510
> RIP=ffffffff810767cb RFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
> CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
> SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
> DS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
> FS =0000 0000000000000000 000fffff 00000000
> GS =0000 ffff880009a00000 000fffff 00000000
> LDT=0000 0000000000000000 000fffff 00000000
> TR =0040 ffff880009a11880 00002087 00008b00 DPL=0 TSS64-busy
> GDT= ffff880009a04000 0000007f
> IDT= ffffffff815fd000 00000fff
> CR0=8005003b CR2=00007f424e540700 CR3=000000021690c000 CR4=000006f0
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000d01
> FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> XMM00=00000000000000000000000000000000 XMM01=0000000000000000000000003c23d70a
> XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
> XMM08=00000000000000000000000000000000 XMM09=00000000000000000000000000000000
> XMM10=00000000000000000000000000000000 XMM11=00000000000000000000000000000000
> XMM12=00000000000000000000000000000000 XMM13=00000000000000000000000000000000
> XMM14=00000000000000000000000000000000 XMM15=00000000000000000000000000000000
>
> info cpus:
> * CPU #0: pc=0xffffffff8105d4a0 thread_id=19639
> CPU #1: pc=0xffffffff81013140 thread_id=19640
> CPU #2: pc=0xffffffff8102a1b6 (halted) thread_id=19641
> CPU #3: pc=0xffffffff81341521 thread_id=19642
> CPU #4: pc=0xffffffff810415d8 thread_id=19643
> CPU #5: pc=0xffffffff811ca521 thread_id=19644
> CPU #6: pc=0xffffffff81013140 thread_id=19646
> CPU #7: pc=0xffffffff8102a1b6 (halted) thread_id=19647
>
>
> and here are trace-cmds for all cpus:
> http://nik.lbox.cz/public/trace-cmd.tar.bz2
>
> Could somebody please have a look at this?
>
> I also tried 2.6.38.5, but the result is the same...
>
> cheers
> nik
>
>
>
>
> --
> -------------------------------------
> Ing. Nikola CIPRICH
> LinuxBox.cz, s.r.o.
> 28. rijna 168, 709 01 Ostrava
>
> tel.: +420 596 603 142
> fax: +420 596 621 273
> mobil: +420 777 093 799
>
> www.linuxbox.cz
>
> mobil servis: +420 737 238 656
> email servis: servis@linuxbox.cz
> -------------------------------------
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-08 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:33 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0) Nikola Ciprich
2011-05-08 18:41 ` Nikola Ciprich [this message]
2011-05-08 18:53 ` Michael Tokarev
2011-05-08 19:06 ` Nikola Ciprich
2011-05-09 3:06 ` David Ahern
2011-05-09 17:32 ` Zachary Amsden
2011-05-09 18:25 ` Nikola Ciprich
2011-05-09 18:30 ` Zachary Amsden
2011-05-09 19:27 ` Nikola Ciprich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110508184154.GD2224@nik-comp.lan \
--to=nikola.ciprich@linuxbox.cz \
--cc=ciprich@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=zamsden@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.