Re: [Xen-devel] VMX status report. Xen:24911 & Dom0: d93dc5c4...

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Wed, Mar 14, 2012 at 08:54:50AM +0000, Ren, Yongjie wrote:
> > -----Original Message-----
> > From: xen-devel-bounces@xxxxxxxxxxxxx
> > [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of Konrad Rzeszutek
> > Wilk
> > Sent: Wednesday, March 14, 2012 12:55 AM
> > To: Zhou, Chao
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] VMX status report. Xen:24911 & Dom0:
> > d93dc5c4...
> > 
> > On Tue, Mar 13, 2012 at 09:18:27AM +0000, Zhou, Chao wrote:
> > > Hi all,
> > >
> > > This is the test report of xen-unstable tree. We've switched our Dom0 to
> > upstream Linux 3.1-rc7 instead of Jeremy's 2.6.32.x tree.
> > 
> > Nice! Thanks for doing that. Thought some of the issues reported below I
> > think
> > are fixed in 3.3.. Especially the 'xl vcpu-set' one - which I think is also
> > back-ported to the 3.x stable kernel.
> > 
> As some our internal patches are based on 3.1-rc7, we use 3.1 as a base Dom0 
> for testing.
> We also tried most of these new bugs with 3.3 kernel, and found they still 
> exist.

which of the BZs below are against 3.3?

> As for the 'xl vcpu-set' issue, upstream linux 3.3 also has the similar issue.
> I just gave some update for this on the bugzilla. You may have a look.
> http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730

OK, first of I am really excited that you guys are using the upstream kernel
and testing against the latest.

I think the issue I've seen before and it was due to a mix of vCPU hotplug code.
If I booted the kernel with max_cpus=16 (on the Linux command line) and did 
those
operations it worked. But it is a bug nonethless. Any ideas for a fix?

> 
> -- Jay
> 
> > > We've also upgraded our nightly test system from RHEL5.5 to RHEL6.2.
> > > We found four new issues and one old issue got fixed.
> > >
> > > Version Info
> > >
> > ============================================================
> > =====
> > > xen-changeset:  24911:d7fe4cd831a0
> > > Dom0: linux.git  3.1-rc7 (commit: d93dc5c4...)
> > >
> > ============================================================
> > =====
> > >
> > >
> > > New issues(4)
> > > ==============
> > > 1. when detaching a VF from hvm guest, "xl dmesg" will show some
> > warning information
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1809
> > > 2. Dom0 hang when bootup a guest with a VF(the guest has been bootup
> > with a different VF before)
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1810
> > > 3. RHEL6.2/6.1 guest runs quite slow
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1811
> > > 4. after detaching a VF from a guest, shutdown the guest is very slow
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1812
> > >
> > > Fixed issue(1)
> > > ==============
> > > 1. Dom0 crash on power-off
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1740
> > >     ----kernel3.1.0 doesn't have this issue now
> > >
> > > Old issues(5)
> > 
> > These old ones are with 3.1.x?
> > > ==============
> > > 1. [ACPI] System cann't resume after do suspend
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1707
> > > 2. [XL]"xl vcpu-set" causes dom0 crash or panic
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1730
> > > 3. [VT-D]fail to detach NIC from guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1736
> > > 4. Sometimes Xen panic on ia32pae Sandybridge when restore guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1747
> > > 5. [VT-D] device reset fail when create/destroy guest
> > >   http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1752
> > >
> > >
> > > Thanks
> > > Zhou, Chao
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxx
> > > http://lists.xen.org/xen-devel
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel