From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"kvm" <kvm@vger.kernel.org>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Michael S.Tsirkin" <mst@redhat.com>,
"Gleb Natapov" <gleb@cloudius-systems.com>
Subject: RE: [question] lots of interrupts injected to vm when pressing some key w/o releasing
Date: Thu, 27 Nov 2014 16:54:53 +0800 [thread overview]
Message-ID: <201411271654507543497@sangfor.com> (raw)
In-Reply-To: A9667DDFB95DB7438FA9D7D576C3D87E0ABF2C24@SHSMSX104.ccr.corp.intel.com
>>>>>>>> I tested win-server-2008 with "-cpu
>>>>>>>> core2duo,hv_spinlocks=0xffff,hv_relaxed,hv_time",
>>>>>>>> this problem still happened, about 200,000 vmexits per-second,
>>>>>>>> bringing very bad experience, just like being stuck.
>>>>>>>
>>>>>>> Please upload a full trace somewhere, or at least the "perf report"
>>>>>>> output.
>>>>>>>
>>>>>>
>>>>>> And, if I remove the commit of 0bc830b0, the problem disappeared.
>>>>>
>>>>> Please send the full trace file. If you compress it, it should be small.
>>>>>
>>>> See the attach 1, please.
>>>>
>>>>> Paolo
>>>
>>> Can you try the follow draft patch to see whether it solve your
>>> problem? This patch is based on commit 0bc830b0.
>>>
>> After applying this patch, VM got stuck with black-screen at boot
>
>It is works well in my side. And this patch does fix the issue in my box.
>I am using window 2008 R2 for testing, here is the qemu cmdline:
>qemu-system-x86_64 -enable-kvm -m 4G -smp 4 -net nic,macaddr=00:12:41:41:13:41 -net tap,script=/etc/kvm/qemu-ifup win2k8.qcow
>
>Can you provide your configuration for me to test?
>
/usr/bin/kvm -id 2284096534876 -chardev socket,id=qmp,path=/var/run/qemu-server/2284096534876.qmp,server,nowait -mon chardev=qmp,mode=control -vnc :0,websocket,to=200,x509,password -pidfile /var/run/qemu-server/2284096534876.pid -daemonize -name win2008-x64 -smp sockets=1,cores=2 -cpu core2duo,hv_spinlocks=0xffff,hv_relaxed -nodefaults -vga cirrus -no-hpet -k en-us -boot menu=on,splash-time=8000 -m 4096 -usb -drive if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100 -drive file=/sf/data/local/images/host-4061863144dc/d23a20df36a5/win2008-x64.vm/vm-disk-1.qcow2,if=none,id=drive-ide1,cache=none,aio=threads -device ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1 -netdev type=tap,id=net0,ifname=228409653487600,script=/sf/etc/kvm
/vtp-bridge,vhost=on,vhostforce=on -device virtio-net-pci,romfile=,mac=FE:FC:FE:99:4C:2E,netdev=net0,bus=pci.0,addr=0x12,id=net0 -rtc driftfix=slew,clock=rt,base=localtime -global kvm-pit.lo
st_tick_policy=discard -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -chardev socket,path=/var/run/qemu-server/2284096534876.virtser,server,nowait,id=channelser -device virtio-serial,max_ports=2,ioeventfd=off -device virtserialport,chardev=channelser,name=channelser.virtserial0.0 -bios /sf/share/kvm/bios.bin.1
You can change "-id" option to "-uuid".
Thanks,
Zhang Haoyu
>> stage, # trace-cmd report:
>> version = 6
>> CPU 0 is empty
>> CPU 1 is empty
>> CPU 2 is empty
>> CPU 3 is empty
>> CPU 5 is empty
>> CPU 7 is empty
>> cpus=8
>> kvm-1266 [004] 14399.834397: kvm_set_irq: gsi 9
>> level 1 source 0 kvm-1266 [004] 14399.834403:
>> kvm_pic_set_irq: chip 1 pin 1 (edge|masked) kvm-1266
>> [004] 14399.834411: kvm_apic_accept_irq: apicid 0 vec 177
>> (LowPrio|level) kvm-1266 [004] 14399.834412:
>> kvm_ioapic_set_irq: pin 9 dst 3 vec=177
>> (LowPrio|logical|level) kvm-1266 [004] 14402.180013:
>> kvm_set_irq: gsi 9 level 1 source 0 kvm-1266
>> [004] 14402.180019: kvm_pic_set_irq: chip 1 pin 1
>> (edge|masked) kvm-1266 [004] 14402.180028:
>> kvm_apic_accept_irq: apicid 1 vec 177 (LowPrio|level)
>> kvm-1266 [004] 14402.180029: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level) kvm-1266 [004]
>> 14404.525627: kvm_set_irq: gsi 9 level 1 source 0
>> kvm-1266 [004] 14404.525634: kvm_pic_set_irq: chip 1
>> pin 1 (edge|masked) kvm-1266 [004] 14404.525641:
>> kvm_apic_accept_irq: apicid 0 vec 177 (LowPrio|level)
>> kvm-1266 [004] 14404.525642: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level) kvm-1266 [004]
>> 14406.871238: kvm_set_irq: gsi 9 level 1 source 0
>> kvm-1266 [004] 14406.871245: kvm_pic_set_irq: chip 1
>> pin 1 (edge|masked) kvm-1266 [004] 14406.871254:
>> kvm_apic_accept_irq: apicid 1 vec 177 (LowPrio|level)
>> kvm-1266 [004] 14406.871256: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level) kvm-1266 [006]
>> 14409.216849: kvm_set_irq: gsi 9 level 1 source 0
>> kvm-1266 [006] 14409.216855: kvm_pic_set_irq: chip 1
>> pin 1 (edge|masked) kvm-1266 [006] 14409.216862:
>> kvm_apic_accept_irq: apicid 0 vec 177 (LowPrio|level)
>> kvm-1266 [006] 14409.216863: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level) kvm-1266 [006]
>> 14411.562475: kvm_set_irq: gsi 9 level 1 source 0
>> kvm-1266 [006] 14411.562481: kvm_pic_set_irq: chip 1
>> pin 1 (edge|masked) kvm-1266 [006] 14411.562489:
>> kvm_apic_accept_irq: apicid 1 vec 177 (LowPrio|level)
>> kvm-1266 [006] 14411.562491: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level) kvm-1266 [004]
>> 14413.908074: kvm_set_irq: gsi 9 level 1 source 0
>> kvm-1266 [004] 14413.908080: kvm_pic_set_irq: chip 1
>> pin 1 (edge|masked) kvm-1266 [004] 14413.908088:
>> kvm_apic_accept_irq: apicid 0 vec 177 (LowPrio|level)
>> kvm-1266 [004] 14413.908089: kvm_ioapic_set_irq: pin 9
>> dst 3 vec=177 (LowPrio|logical|level)
>>
>> Thanks,
>> Zhang Haoyu
>>
>Best regards,
>Yang
next prev parent reply other threads:[~2014-11-27 8:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 2:20 [question] lots of interrupts injected to vm when pressing some key w/o releasing Zhang Haoyu
2014-11-20 6:19 ` Paolo Bonzini
2014-11-20 6:59 ` [question] lots of interrupts injected to vm when pressing somekey " Zhang Haoyu
2014-11-20 7:06 ` Gleb Natapov
2014-11-24 8:58 ` [question] lots of interrupts injected to vm when pressingsomekey " Zhang Haoyu
[not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABEF25B@SHSMSX104.ccr.corp.intel.com>
2014-11-21 22:31 ` [question] lots of interrupts injected to vm when pressing some key " Paolo Bonzini
[not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF0FE3@SHSMSX104.ccr.corp.intel.com>
2014-11-25 9:49 ` Paolo Bonzini
[not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF396A@SHSMSX104.ccr.corp.intel.com>
2014-12-03 15:42 ` Paolo Bonzini
2014-12-15 9:39 ` Zhang Haoyu
2014-12-15 9:40 ` Paolo Bonzini
2014-11-24 12:17 ` Zhang Haoyu
2014-11-24 12:25 ` Paolo Bonzini
2014-11-25 1:54 ` [question] lots of interrupts injected to vm when pressing somekey " Zhang Haoyu
2014-11-25 7:02 ` Paolo Bonzini
2014-11-25 11:20 ` Zhang Haoyu
2014-11-25 13:52 ` Paolo Bonzini
[not found] ` <201411261511537876936@sangfor.com>
[not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF2A95@SHSMSX104.ccr.corp.intel.com>
2014-11-27 7:20 ` [question] lots of interrupts injected to vm when pressing some key " Zhang Haoyu
[not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF2C24@SHSMSX104.ccr.corp.intel.com>
2014-11-27 8:54 ` Zhang Haoyu [this message]
2014-11-28 8:27 ` Wanpeng Li
2014-11-28 9:44 ` Zhang Haoyu
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=201411271654507543497@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@cloudius-systems.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=yang.z.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).