[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] vmx status report against cset 14912 - 1 fixed issue, 4 old issues


  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Zhao, Yunfeng" <yunfeng.zhao@xxxxxxxxx>
  • Date: Wed, 25 Apr 2007 17:44:11 +0800
  • Delivery-date: Wed, 25 Apr 2007 02:42:58 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceG3J3OlwL2jeGuSIK4ido1hBOBCQAOIa5QAACbto8AAKc0AAAArNhfAAA/NoA=
  • Thread-topic: [Xen-devel] vmx status report against cset 14912 - 1 fixed issue, 4 old issues

>> [Yunfeng] The guest was booted with a 2.16.16 smp kernel which we
built
>> for PV test. It only happens on SMP HVM linux guest.I also saw the
same
>> issue on some SLES SMP HVM guests with SLES release kernel and PV
>> drivers.
>
>It would be interesting to see what happens if the platform-pci
interrupt is
>pinned strictly to vcpu0. So, what happens if you boot the guest with
>'acpi=0'? Or, what about if you kill any irqbalance programs that are
>running after boot, then 'cat /proc/interrupts' to find the
xen-platform-pci
>interrupt number (x) and then 'echo 1 >/proc/irq/<x>/smp_affinity'?
>
>I couldn't repro just with SpecJBB but it's quite possible the kernel
build
>is really required to repro. Specjbb itself does very little I/O.

[Yunfeng] Ok, we will try this, and send out the result.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.