From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: VMX status report. Xen:24446 & Dom0: 20a27c1e... Date: Tue, 3 Jan 2012 13:20:07 -0400 Message-ID: <20120103172007.GD749@andromeda.dapyr.net> References: <40352EBA8B4DF841A9907B883F22B59BDD99@SHSMSX102.ccr.corp.intel.com> <20111229173208.GA18032@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20111229173208.GA18032@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: "xen-devel@lists.xensource.com" , "Zhou, Chao" List-Id: xen-devel@lists.xenproject.org On Thu, Dec 29, 2011 at 12:32:08PM -0500, Konrad Rzeszutek Wilk wrote: > On Thu, Dec 29, 2011 at 08:42:17AM +0000, Zhou, Chao wrote: > > Hi all, > > > > This is the test report of xen-unstable tree. There is one issue which has existed in xen upstream since CS #22415 but was found recently. > > After we hotplug a VF or NIC to guest for several times(about 10 times) the guest can't get ip address. The old CS #22402 doesn't have this issue, but it exists in latest xen upstream. > > > > > > Version Info > > ================================================================= > > xen-changeset: 24446:2863b2f43a3b > > pvops git: Jeremy's tree > > commit 20a27c1e25b8550066902c9d6ca91631e656dfa3 > > When are you guys planning to switch to the upstream kernel? ping? As in the 3.0 or 3.1 or 3.2.x kernel?