Re: [Xen-devel] VMX status report. Xen:24446 & Dom0: 20a27c1e...

["Ren, Yongjie" <yongjie.ren@xxxxxxxxx>]

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Konrad
> Rzeszutek Wilk
> Sent: Wednesday, January 04, 2012 1:20 AM
> To: Zhou, Chao
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Zhou, Chao
> Subject: Re: [Xen-devel] VMX status report. Xen:24446 & Dom0: 20a27c1e...
> 
> 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?
> 
We still wait for some PM and RAS patches to be merged into upstream. As you 
may know, Jinsong is dong RAS rebase to your 3.1 dom0 tree.
Switching to upstream kernel is in our plan. If these patches is in upstream, 
we'll switch to upstream kernel or 3.1 kernel.

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

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