On 2015-01-28 03:10:23, Jidong Xiao wrote:
> On Tue, Jan 27, 2015 at 5:55 AM, Mikhail Sennikovskii
> wrote:
> > Hi all,
>>
> > I've posted the bolow mail to the qemu-dev mailing list, but I've got no
> > response there.
> > That's why I decided to re-post it here as well, and besides that I think
On 2015-01-26 19:29:03, Paolo Bonzini wrote:
>
> On 26/01/2015 12:13, Zhang Haoyu wrote:
> > Thanks, Paolo,
> > but too many internal snapshots were saved by customers,
>> switching to external snapshot mechanism has significant impaction
> > on subsequent upgrade.
On 2015-01-26 17:29:43, Paolo Bonzini wrote:
>
> On 26/01/2015 02:07, Zhang Haoyu wrote:
> > Hi, Kashyap
> > I've tried ‘drive_backup’ via QMP,
>> but the snapshots were missed to backup to destination,
> > I think the reason is that backup_run() only copy the
&
On 2015-01-23 07:30:19, Kashyap Chamarthy wrote:
>On Wed, Jan 21, 2015 at 11:39:44AM +0100, Paolo Bonzini wrote:
> >
> >
> > On 21/01/2015 11:32, Zhang Haoyu wrote:
> > > Hi,
>> >
> > > Does drive_mirror support incremental ba
for
the changed data.
Next time backup, only the dirty data will be mirrored to destination.
Even the VM shutdown and start after several days,
the bitmap will be loaded while starting vm.
Any ideas?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" i
On 2014-12-22 09:28:52, Paolo Bonzini wrote:
>
>On 22/12/2014 07:39, Zhang Haoyu wrote:
>> Hi,
>>
>> When I perform P2V from native servers with win2008 to kvm vm,
>> some cases failed due to the physical disk was using GPT for partition,
>> and QEMU doesn
o pay anyone for support, you probably
Hi, Paolo,
do you mean the commit fc57ac2 KVM: lapic: sync highest ISR to hardware apic on
EOI ?
I want to backport it to our product.
Thanks,
Zhang Haoyu
> should have thought about this yourself. If you hadn't thought about
> it, and you are goin
On 2014/12/23 9:36, Fam Zheng wrote:
> On Mon, 12/22 20:21, Zhang Haoyu wrote:
>>
>> On 2014/12/22 20:05, Paolo Bonzini wrote:
>>>
>>>
>>> On 22/12/2014 12:40, Zhang Haoyu wrote:
>>>> On 2014/12/22 17:54, Paolo Bonzini wrote:
>>>&
On 2014/12/22 20:05, Paolo Bonzini wrote:
>
>
> On 22/12/2014 12:40, Zhang Haoyu wrote:
>> On 2014/12/22 17:54, Paolo Bonzini wrote:
>>>
>>>
>>> On 22/12/2014 10:48, Zhang Haoyu wrote:
>>>> Hi,
>>>>
>>>> I cannot re
On 2014/12/22 17:54, Paolo Bonzini wrote:
>
>
> On 22/12/2014 10:48, Zhang Haoyu wrote:
>> Hi,
>>
>> I cannot receive qemu-dev/kvm-dev mails sent by myself,
>> but mails from others can be received,
>> any helps?
>
> For qemu-devel, you need to conf
On 2014/12/22 17:52, Paolo Bonzini wrote:
>
>
> On 22/12/2014 10:40, Zhang Haoyu wrote:
>>> 2) the FAT driver is not free, which prevents distribution in Fedora and
>>> several other distributions
>>>
>> Sorry, I cannot follow you,
>> the "
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
On 2014/12/22 17:28, Paolo Bonzini wrote:
>
>
> On 22/12/2014 07:39, Zhang Haoyu wrote:
>> Hi,
>>
>> When I perform P2V from native servers with win2008 to kvm vm,
>> some cases failed due to the physical disk was using GPT for partition,
>> and QEMU doesn
/OVMF
But, it seems that OVMF is not stable enough for kvm.
Any advises?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
Does "is_guest_mode() == true" mean in L1 (guest hypervisor)?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Paolo, Yang
What's the status of this problem?
Thanks,
Zhang Haoyu
On 2014-12-04 00:13:49, Paolo Bonzini wrote:
>
>
>On 28/11/2014 12:59, Zhang, Yang Z wrote:
>>
>> According the feedback from Haoyu on my test patch which skipping the
>> interrupt injection if
On 2014-12-12 18:27:14, Paolo Bonzini wrote:
>
>
>On 12/12/2014 10:56, Zhang Haoyu wrote:
>> Strange, I didn't find this commit in
>> https://git.kernel.org/cgit/virt/kvm/kvm.git/log/
>> but found it from the repository downloaded by git clone
>> git://g
On 2014-12-11 19:06:33, Zhang, Yang Z wrote:
>Zhang Haoyu wrote on 2014-12-11:
>> Then?
>
>It's already in upstream KVM
>
Strange, I didn't find this commit in
https://git.kernel.org/cgit/virt/kvm/kvm.git/log/
but found it from the repository downloaded by git clone
Then?
>> On 05/11/2014 10:02, Chen, Tiejun wrote:
I think both are ok.
If we zero max_irr in vmx_set_rvi(), we still need this check:
if ((is_guest_mode(vcpu) && nested_exit_on_intr(vcpu)) || max_irr
==
-1)
>>>
>>> No, I don't think we need to add this.
>>
>> You don't,
ic_clear_isr() is inline function,
which is called by apic_set_eoi(), you can check it, this method is a bit
complicated.
Any better ideas?
>On Thu, Dec 4, 2014 at 3:15 PM, Zhang Haoyu wrote:
>>>Is this the correct function?
>>>kvm_lapic_set_eoi
>>>
>&g
oad and
>> extract kvm.ko out then run nm kvm.ko | grep lsr, nothing found.
>>
>> On Thu, Dec 4, 2014 at 12:32 PM, Zhang Haoyu wrote:
>>>>what does vapic affect Windows 7 at all if I disable it? if it just a
>>>>minor performance drop, I am fine with that.
o depends on the frequency of access to above three apic regs.
>On Thu, Dec 4, 2014 at 10:06 AM, Zhang Haoyu wrote:
>>>Sure, but I am little confused as KVM is part of linux kernel now, if
>>>I want to try it, should I just upgrade kernel or compile kvm kernel
>>>module
>Sure, but I am little confused as KVM is part of linux kernel now, if
>I want to try it, should I just upgrade kernel or compile kvm kernel
>module by myself ?!
>
You can just apply the patch to kvm module and rebuild it.
>On Thu, Dec 4, 2014 at 10:01 AM, Zhang Haoyu wrote:
>
>I just confirmed that vapic is causing win7 stuck.
>
You'd better try the commit fc57ac2c9ca :-)
>On Thu, Dec 4, 2014 at 9:34 AM, Thomas Lau wrote:
>> Hi,
>>
>> I don't want to recompile stuff, does it matter to have hv_vapic on at all?
>>
>> O
Message
> From: Vadim Rozenfeld
> Sent: Wednesday, 3 December, 2014 7:30 PM
> To: Thomas Lau
> Cc: Zhang Haoyu; kvm; imammedo
> Subject: Re: Windows 7 VM BSOD
>
> If you run WS2008(R2) or Win7 - always turn on relaxed timing. Otherwise
> it's just a matter of time when
ment.
Thanks,
Zhang Haoyu
> On Wed, Dec 3, 2014 at 6:36 PM, Thomas Lau wrote:
> > Hi,
> >
> > How do I know if my qemu-kvm version support this?
> >
> > On Wed, Dec 3, 2014 at 6:25 PM, Zhang Haoyu wrote:
> >>> Hi All,
> >>>
> >>>
> Hi,
>
> How do I know if my qemu-kvm version support this?
>
I don't know which qemu version starts to support hv-relaxed,
but I'm sure qemu-1.4.1 and later versions support it.
qemu will report error if it dosen't support it.
Please show your qemu version.
Thanks,
> Hi All,
>
> I am running 3.13.0-24-generic kernel on Ubuntu 14, Windows 7 VM
> installation was fine, but it does random reboot by itself, the error
> code is 0x0101, does anyone know how to fix this?
Could you try hv_relaxed, like "-cpu kvm64,hv_relaxed".
T
> > Hi,
> >
> > EXIT_REASON_EPT_VIOLATION's corresponding handle is handle_ept_violation(),
> > and EXIT_REASON_EPT_MISCONFIG's corresponding handle is
> > handle_ept_misconfig(),
> > what's the difference between them?
> >
> > I read the SDM-3C 28.2.3 EPT-Induced VM Exits, and found below descr
an access using the guest physical
address."
According to above description, EPT-MISCONFIG is from error settings ,
but from the its exit-handle handle_ept_misconfig(),
it seems that handle_ept_misconfig() handles mmio pagefault,
I'm really confused, I think I'm missing something
>Hi all,
>On Thu, Nov 27, 2014 at 03:20:43PM +0800, Zhang Haoyu wrote:
>>>>>>>> I tested win-server-2008 with "-cpu
>>>>>>>> core2duo,hv_spinlocks=0x,hv_relaxed,hv_time",
>>>>>>>> this problem still happe
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,
: 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
>diff --git a/virt/kvm/ioapic.c b
Hi,
what is virtio-1 device?
>>>
>>> Are you mean subsystem device id is '1'? That should be a network card.
>>>
>> In the mail "qemu: towards virtio-1 host support", "virtio: allow virtio-1
>> queue layout",
>> "dataplane: allow virtio-1 devices", etc., "virtio-1 devices" was menti
devices", etc., "virtio-1 devices" was mentioned,
I don't know which devices it incorporates?
Thanks,
Zhang Haoyu
>Tiejun
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
what is virtio-1 device?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
0 0
...
And, if I remove the commit of 0bc830b0, the problem disappeared.
Thanks,
Zhang Haoyu
>Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
paravirtualized time
>counter (-cpu ...,hv_time).
>
I tested win-server-2008 with "-cpu
core2duo,hv_spinlocks=0x,hv_relaxed,hv_time",
this problem still happened, about 200,000 vmexits per-second,
bringing very bad experience, just like being stuck.
Thanks,
Zhang Ha
erience. But the other keys are okay.
Sorry for wrong description, the interrupt rate is normal,
but huge numbers of vmexit induced by PIO were produced.
Thanks,
Zhang Haoyu
>And, linux guest has no this problem.
>
>If I remove the commit of 0bc830b05c667218d703f2026ec866c49df974fc, then
>On Thu, Nov 20, 2014 at 02:59:36PM +0800, Zhang Haoyu wrote:
>> >On 20/11/2014 03:20, Zhang Haoyu wrote:
>> >> Hi all,
>> >>
>> >> If I press the one of "Insert/Delete/Home/End/PageUp/PageDown/UpArrow/
>> >> DownArrow/LeftArrow/Rig
>On 20/11/2014 03:20, Zhang Haoyu wrote:
>> Hi all,
>>
>> If I press the one of "Insert/Delete/Home/End/PageUp/PageDown/UpArrow/
>> DownArrow/LeftArrow/RightArrow" key w/o releasing, then lots of interrupts
>> will be injected to vm(win7/win2008), ab
okay.
And, linux guest has no this problem.
If I remove the commit of 0bc830b05c667218d703f2026ec866c49df974fc, then the
problem disappeared, but win7 guest got stuck at booting stage.
And so strange that If the vm has only one vcpu, then the problem also
disappeared.
Any ideas?
Thanks,
Z
Hi all,
Does the combination of qemu-2.0.1 and linux-3.10 fully support direct-assign
vga adapters to vm?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
u have
> > on the host, and how it's configured.
> >
> > I think you will get something more closely resembling this
> > behaviour if you enable RFS in host.
> >
> > > When I pin iperf in a guest I do indeed see that all interrupts
> > > are arriving to th
> Hi,
>
> I saw this page:
>
> http://www.linux-kvm.org/page/Migration.
>
> It looks like Migration is a feature provided by KVM? But when I look
> at the Linux kernel source code, i.e., virt/kvm, and arch/x86/kvm, I
> don't see the code for this migration feature.
>
Most of live migration code
nt to install some applications for all of the clones,
>>>> what should I do?
>
>How would you do it for bare metal? Do the same for your guests.
>
For bare-metal, I use manager to push the applications to each host-agent
which is running in each host, the host-agent is resp
t should I do?
>
>Install the applications on each clone separately, or use some other
>method to make it available (like installing on a shared network
>resource).
>
Could you detail "installing on a shared network resource"?
Thanks,
Zhang Haoyu
>> Can I rebase ima
agent,
which is responsible to install the applications.
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
this value. The setup for
>> netperf consisted of
>> > 1 vm and 1 vhost , each running on their own dedicated core.
>> >
>> Could you provide your changing code?
>>
>> Thanks,
>> Zhang Haoyu
>>
>Hi Zhang,
>Do you mean the change in
of
> 1 vm and 1 vhost , each running on their own dedicated core.
>
Could you provide your changing code?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 2014-10-12 15:34, Kevin Wolf wrote:
Am 11.10.2014 um 09:14 hat Zhang Haoyu geschrieben:
In qcow2_update_snapshot_refcount -> qcow2_process_discards() -> bdrv_discard()
may free the Qcow2DiscardRegion which is referenced by "next" pointer in
qcow2_process_discards() now, in n
d_pwritev
| qcow2_co_writev
|- qcow2_alloc_cluster_link_l2
|-- qcow2_free_any_clusters
|--- qcow2_free_clusters
| update_refcount
|- qcow2_process_discards
|-- g_free(d) <== In next iteration, this Qcow2DiscardRegion will be
double-free.
Signed-off-by: Zhang Haoyu
Signed-o
ve degree can be used to decide the threshold of which
vcpus belong to the same gang, just a wild thought.
> Regards,
> Wanpeng Li
>>
>> Thanks,
>> Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
/task is running in guest.
Is there a plane for this work?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
be virtio_console.
>
>Looks like the ppoll takes more time to poll more fds.
>
>Some trace data with systemtap:
>
>12 fds:
>
>time rel_time symbol
>15 (+1) qemu_poll_ns [enter]
>18(+3) qemu_poll_ns [return]
>
>76 fd:
>
&g
rtio_console driver in guest,
to see whether there is difference in virtio-blk performance and cpu usage.
2. Does not emulate virito-serial deivce, then install virtio_balloon
driver (and also dose not emulate virtio-balloon device),
to see whether virtio-blk performance degradation will happen
ical Slot: 18
>Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
>Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR- Interrupt: pin A routed to IRQ 10
>Region 0: I/O ports at c0c0 [size=32]
>Region 1: Memory at febd4000 (32-bit, non-prefetchable) [size=4K]
>Expansion ROM at feb8 [disabled] [size=256K]
>Capabilities: [40] MSI-X: Enable+ Count=3 Masked-
>Vector table: BAR=1 offset=
>PBA: BAR=1 offset=0800
>Kernel driver in use: virtio-pci
>Kernel modules: virtio_pci
>
>Thanks,
>Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
e missing "}" for if (ioapic->irq_eoi[i] ==
IOAPIC_SUCCESSIVE_IRQ_MAX_COUNT) {
Cc: Michael S. Tsirkin
Cc: Jan Kiszka
Signed-off-by: Jason Wang
Signed-off-by: Zhang Haoyu
---
include/trace/events/kvm.h | 20 +++
virt/kvm/ioapic.c | 50 +++
no suitable irq handler in case it may
>> register one very soon and for guest who has a bad irq detection routine (
>> such
>> as note_interrupt() in linux ), this bad irq would be recognized soon as in
>> the
>> past.
>
o suitable irq handler in case it may
register one very soon and for guest who has a bad irq detection routine ( such
as note_interrupt() in linux ), this bad irq would be recognized soon as in the
past.
Cc: Michael S. Tsirkin
Signed-off-by: Jason Wang
Signed-off-by: Zhang Haoyu
---
includ
>> such
>> as note_interrupt() in linux ), this bad irq would be recognized soon as in
>> the
>> past.
>>
>> Cc: Michael S. Tsirkin
>> Signed-off-by: Jason Wang
>> Signed-off-by: Zhang Haoyu
>> ---
>> include/trace/events/kvm.h
o suitable irq handler in case it may
register one very soon and for guest who has a bad irq detection routine ( such
as note_interrupt() in linux ), this bad irq would be recognized soon as in the
past.
Cc: Michael S. Tsirkin
Signed-off-by: Jason Wang
Signed-off-by: Zhang Haoyu
---
includ
o has a bad irq detection routine ( such
as note_interrupt() in linux ), this bad irq would be recognized soon as in the
past.
Cc: Michael S. Tsirkin
Signed-off-by: Jason Wang
Signed-off-by: Zhang Haoyu
---
include/trace/events/kvm.h | 20 ++
virt/kvm/ioapic.c | 51
o suitable irq handler in case it may
register one very soon and for guest who has a bad irq detection routine ( such
as note_interrupt() in linux ), this bad irq would be recognized soon as in the
past.
Cc: Michael S. Tsirkin
Signed-off-by: Jason Wang
Signed-off-by: Zhang Haoyu
---
includ
Hi, Paolo, Amit,
any ideas?
Thanks,
Zhang Haoyu
On 2014-9-4 15:56, Zhang Haoyu wrote:
>>>>> If virtio-blk and virtio-serial share an IRQ, the guest operating system
>>>>> has to check each virtqueue for activity. Maybe there is some
>>>>> ineff
7;include/linux/unaligned': File too large
How to resolve these errors?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
>> > > If virtio-blk and virtio-serial share an IRQ, the guest operating system
>> > > has to check each virtqueue for activity. Maybe there is some
>> > > inefficiency doing that.
>> > > AFAIK virtio-serial registers 64 virtqueues (on 31 ports + console) even
>> > > if everything is unused.
>>
> >+* possibility to get proper irq handler
>> >+* registered. So we need to give some breath to
>> >+* guest. TODO: 1 is too long?
>> >+*/
>> >+
got back again, very obvious.
>> add comments:
>> Although the virtio-serial is enabled, I don't use it at all, the
>> degradation still happened.
>
>Using the vectors= option as mentioned below, you can restrict the
>number of MSI vectors the virtio-serial device gets. Yo
?
>>
>> I am going to observe the difference of perf top data on qemu and perf kvm
>> stat data when disable/enable virtio-serial in guest,
>> and the difference of perf top data on guest when disable/enable
>> virtio-serial in guest,
>> any ideas?
>
>So
oing to observe the difference of perf top data on qemu and perf kvm
>stat data when disable/enable virtio-serial in guest,
>and the difference of perf top data on guest when disable/enable virtio-serial
>in guest,
>any ideas?
>
>Thanks,
>Zhang Haoyu
>>If you restrict th
, I think it has no business with legacy interrupt mode, right?
I am going to observe the difference of perf top data on qemu and perf kvm stat
data when disable/enable virtio-serial in guest,
and the difference of perf top data on guest when disable/enable virtio-serial
in guest,
any ideas?
,base=localtime -global
kvm-pit.lost_tick_policy=discard -global PIIX4_PM.disable_s3
=1 -global PIIX4_PM.disable_s4=1
Any ideas?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
Hi, Yang, Gleb, Michael,
Could you help review below patch please?
Thanks,
Zhang Haoyu
>> Hi Jason,
>> I tested below patch, it's okay, the e1000 interrupt storm disappeared.
>> But I am going to make a bit change on it, could you help review it?
>>
>>
= 0;
++ ioapic->irq_eoi[i] = 0;
>+ } else {
>+ ioapic_service(ioapic, i);
>+ }
>+ }
++ else {
++ ioapic->irq_eoi[i] = 0;
++
tual interrupt injection sometimes,
>> then some time delay sensitive applications will be impacted?
>
>I don't test it too much but it only give a minor delay of 1% irq in the
>hope of guest irq handler will be registered shortly. But I suspect it's
>the bug of e1000
l may not be sufficient. And you can
>search e1000 in the archives and you can find some behaviour of e1000
>registers were not fictionalized like what spec said. It was really
>suggested to use virtio-net instead of e1000 in guest.
>>
Will the "[PATCH] kvm: ioapic: conditionally
handler is registered. And Windows guest does not have a mechanism to
>>> detect and disable irq in such condition.
>>>
>> Sorry, I don't understand,
>> I think one interrupt should not been enabled before its handler is
>> successfully registered,
>>
ndition.
>
Sorry, I don't understand,
I think one interrupt should not been enabled before its handler is
successfully registered,
is it possible that e1000 emulation inject the interrupt before the interrupt
is succesfully enabled?
Thanks,
Zhang Haoyu
>e1000 emulation is far from
Hi, all
I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC
interrupt storm,
because "if (!ent->fields.mask && (ioapic->irr & (1 << i)))" is always true in
__kvm_ioapic_update_eoi().
Any ideas?
Thanks,
Zhang Haoyu
--
To unsubsc
3)
>vhost threads server all VMs" and "vhost: add polling mode",
>now I get the patch
>"http://thread.gmane.org/gmane.comp.emulators.kvm.devel/88682/focus=88723";
>posted by Shirley,
>any update to this patch?
>
>And, I want to make a bit change on
;
Hi, Razya, Shirley
I am going to test the combination of
"several (depends on total number of cpu on host, e.g., total_number * 1/3)
vhost threads server all VMs" and "vhost: add polling mode",
now I get the patch
"http://thread.gmane.org/gmane.comp.emulators.kvm.devel/8
Hi, Krishna, Shirley
How got get the latest patch of M:N Implementation of mulitiqueue,
I am going to test the the combination of "M:N Implementation of mulitiqueue"
and "vhost: add polling mode".
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line &quo
/* Lynxpoint-H PCH */
>>0x8c10, 0x8c11, 0x8c12, 0x8c13, 0x8c14, 0x8c15, 0x8c16, 0x8c17,
>>0x8c18, 0x8c19, 0x8c1a, 0x8c1b, 0x8c1c, 0x8c1d, 0x8c1e, 0x8c1f,
>>/* Lynxpoint-LP PCH */
>>0x9c10, 0x9c11, 0x9c12, 0x9c13, 0x9c14, 0x9c15, 0x9c16
9, 0x9c1a, 0x9c1b,
>/* Wildcat PCH */
>0x9c90, 0x9c91, 0x9c92, 0x9c93, 0x9c94, 0x9c95, 0x9c96, 0x9c97,
>0x9c98, 0x9c99, 0x9c9a, 0x9c9b,
>/* Patsburg (X79) PCH */
>0x1d10, 0x1d12, 0x1d14, 0x1d16, 0x1d18, 0x1d1a, 0x1d1c, 0x1d1e,
>};
>
>Hopefully if you run 'lspci -n', you'll see your device ID listed among
>these. We don't currently have any quirks for PCIe switches, so if your
>IOMMU group is still bigger than it should be, that may be the reason.
>Thanks,
>
Using device specific mechanisms to enable and verify ACS-like capability is
okay,
but with regard to those devices which completely don't support ACS-like
capabilities,
what shall we do, how about applying the [PATCH] pci: Enable overrides for
missing ACS capabilities,
and how to reduce the risk of data corruption and info leakage between VMs?
Thanks,
Zhang Haoyu
>Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
e-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-,
03 ComponentID=01 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB-
LinkType=MemMapped LinkValid+
Addr: fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
The intel 82599(02:00.0 or 02:00.1) is behind the pci bridge (
l doc vfio.txt, I'm not sure should I unbind all of the devices
which belong to one iommu_group?
If so, because PF and its VFs belong to the same iommu_group, if I unbind the
PF, its VFs also diappeared.
I think I misunderstand someting,
any advises?
Thanks,
Zhang Haoyu
--
To unsubscribe from this
>EOI
>> How to confirm whether lazy eli has been included?
>>
>not in linux-3.10.0
So, do you mean hv_vapic need the support of lazy eoi?
>> >Btw, hv_spinlocks=0xfff is a pretty huge value.
>> >
>> which value do you advise to use?
>MS seems
fff is a pretty huge value.
>
which value do you advise to use?
Thanks,
Zhang Haoyu
>Best regards,
>Vadim.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
=1 -global
PIIX4_PM.disable_s4=1 -post win2008_iotest -enable-kvm -L /boot/pc-bios
Seen similar problem before?
Any ideas?
Thanks,
Zhang Haoyu
>> >> Hi, Vadim
>> >> I read the kvm-2012-forum paper < KVM as a Microsoft-compatible
>> >> hypervisor>,
>> >&
Maybe tie a knot between "vhost-net scalability tuning: threading for many VMs"
and "vhost: Add polling mode" is a good marriage,
because it's more possibility to get work to do with less polling time, so less
cpu cycles waste.
Thanks,
Zhang Haoy
>> Hi, Vadim
>> I read the kvm-2012-forum paper < KVM as a Microsoft-compatible hypervisor>,
>> Any update and other references, please?
>>
>> Thanks,
>> Zhang Haoyu
>>
>>
>
>Unfortunately, not too much.
>From the the most r
Hi, Vadim
I read the kvm-2012-forum paper < KVM as a Microsoft-compatible hypervisor>,
Any update and other references, please?
Thanks,
Zhang Haoyu
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More m
x2APIC mode,
>>>> you are writing the wrong MSR address.
>>>> Please see SDN 3A 10.12.1.2 x2APIC Register Address Space, you will get
>>>> the answer.
>>>>
>>>Oh, I was writing to 0x1b, which is the address of IA32_APIC_BASE MSR.
>>
Hi,
According to this:
https://github.com/torvalds/linux/commit/0d1de2d901f4ba0972a3886496a44fb1d3300dbd
It looks like kvm have been supporting x2apic since kernel 2.6.32, or
even earlier.
>>> This patch is to emul
>> Hi,
>>
>> According to this:
>>
>> https://github.com/torvalds/linux/commit/0d1de2d901f4ba0972a3886496a44fb1d3300dbd
>>
>> It looks like kvm have been supporting x2apic since kernel 2.6.32, or
>> even earlier.
>>
> This patch is to emulate x2apic for guest
Hi,
According to this:
https://github.com/torvalds/linux/commit/0d1de2d901f4ba0972a3886496a44fb1d3300dbd
It looks like kvm have been supporting x2apic since kernel 2.6.32, or
even earlier.
>>> This patch is to emulate x2apic for guest, then guest can ben
> Hi,
>
> According to this:
>
> https://github.com/torvalds/linux/commit/0d1de2d901f4ba0972a3886496a44fb1d3300dbd
>
> It looks like kvm have been supporting x2apic since kernel 2.6.32, or
> even earlier.
>
This patch is to emulate x2apic for guest, then guest can benefit from some
advantages of
l check it.
>
>>Also, some old scheduler versions didn't put VMs on different
>>CPUs aggressively enough, this resulted in conflicts
>>when VMs compete for the same CPU.
>I will check it.
>
No aggressively contention for the same CPU, but when I pin each vcpu to
dif
1 - 100 of 118 matches
Mail list logo
