some old xl bugs

some old xl bugs

[Zhang, Yang Z]

Hi Stefano

Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.

1. [XL]Fail to create multi-guests with NIC assigned
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
xm don't have the issue.

2. [XL]Guest network broken after do SAVE/RESTOR with xl                      
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1703
I never pass this case after using xl. 

3. [XL]"xl vcpu-set" causes dom0 crash or panic                    
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
This is a regression which I found during Xen 4.1 release cycle testing.

4. [XL]device reset fail when create/destroy guest 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1752
This is not a critical bug. But the warning is boring.

If you need more information about those bugs, please let me know.

best regards
yang

Re: some old xl bugs

[Ian Jackson]

Zhang, Yang Z writes ("[Xen-devel] some old xl  bugs "):
> Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> 2. [XL]Guest network broken after do SAVE/RESTOR with xl                      
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1703
> I never pass this case after using xl. 

My test system does this and it works.  That is, it does save/restore
tests of guests and checks that the guest is working afterwards by
talking to the guest over the vif.

Ian.

Re: some old xl bugs

[Stefano Stabellini]

thanks for the remainder

On Thu, 26 May 2011, Zhang, Yang Z wrote:
> Hi Stefano
> 
> Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> 
> 1. [XL]Fail to create multi-guests with NIC assigned
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
> xm don't have the issue.
> 

from the logs:

*** glibc detected *** xl: malloc(): memory corruption (fast):

it appears to be triggered by libxl_domain_create_new.
Could you please add some more debug messages to xl and libxl to find
out exactly what causes the memory corruption?


> 3. [XL]"xl vcpu-set" causes dom0 crash or panic                    
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> This is a regression which I found during Xen 4.1 release cycle testing.

This one is pretty bad. Konrad, I have the feeling somebody else
reported a similar bug recently... 

Re: Re: some old xl bugs

[Konrad Rzeszutek Wilk]

On Thu, May 26, 2011 at 04:21:23PM +0100, Stefano Stabellini wrote:
> thanks for the remainder
> 
> On Thu, 26 May 2011, Zhang, Yang Z wrote:
> > Hi Stefano
> > 
> > Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> > 
> > 1. [XL]Fail to create multi-guests with NIC assigned
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
> > xm don't have the issue.
> > 
> 
> from the logs:
> 
> *** glibc detected *** xl: malloc(): memory corruption (fast):
> 
> it appears to be triggered by libxl_domain_create_new.
> Could you please add some more debug messages to xl and libxl to find
> out exactly what causes the memory corruption?
> 
> 
> > 3. [XL]"xl vcpu-set" causes dom0 crash or panic                    
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> > This is a regression which I found during Xen 4.1 release cycle testing.
> 
> This one is pretty bad. Konrad, I have the feeling somebody else
> reported a similar bug recently... 

I did. But I think you fixed it initially, and then later on tglrx
accepted the patch to fix this for good in generic.

I can't reproduce it anymore on 2.6.39.

Re: Re: some old xl bugs

[Stefano Stabellini]

On Thu, 26 May 2011, Konrad Rzeszutek Wilk wrote:
> On Thu, May 26, 2011 at 04:21:23PM +0100, Stefano Stabellini wrote:
> > thanks for the remainder
> > 
> > On Thu, 26 May 2011, Zhang, Yang Z wrote:
> > > Hi Stefano
> > > 
> > > Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> > > 
> > > 1. [XL]Fail to create multi-guests with NIC assigned
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
> > > xm don't have the issue.
> > > 
> > 
> > from the logs:
> > 
> > *** glibc detected *** xl: malloc(): memory corruption (fast):
> > 
> > it appears to be triggered by libxl_domain_create_new.
> > Could you please add some more debug messages to xl and libxl to find
> > out exactly what causes the memory corruption?
> > 
> > 
> > > 3. [XL]"xl vcpu-set" causes dom0 crash or panic                    
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> > > This is a regression which I found during Xen 4.1 release cycle testing.
> > 
> > This one is pretty bad. Konrad, I have the feeling somebody else
> > reported a similar bug recently... 
> 
> I did. But I think you fixed it initially, and then later on tglrx
> accepted the patch to fix this for good in generic.
> 
> I can't reproduce it anymore on 2.6.39.
> 

I thought it was that bug, I am glad is gone. We should probably submit
one of the two fixes to Jeremy's tree.

Re: Re: some old xl bugs

[Konrad Rzeszutek Wilk]

On Thu, May 26, 2011 at 11:36:54AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, May 26, 2011 at 04:21:23PM +0100, Stefano Stabellini wrote:
> > thanks for the remainder
> > 
> > On Thu, 26 May 2011, Zhang, Yang Z wrote:
> > > Hi Stefano
> > > 
> > > Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> > > 
> > > 1. [XL]Fail to create multi-guests with NIC assigned
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
> > > xm don't have the issue.
> > > 
> > 
> > from the logs:
> > 
> > *** glibc detected *** xl: malloc(): memory corruption (fast):
> > 
> > it appears to be triggered by libxl_domain_create_new.
> > Could you please add some more debug messages to xl and libxl to find
> > out exactly what causes the memory corruption?

Weird, I seem to have something similar happening now that I updated my
Ubuntu 11.04 box (apt-get update).
> > 
> > 
> > > 3. [XL]"xl vcpu-set" causes dom0 crash or panic                    
> > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1730
> > > This is a regression which I found during Xen 4.1 release cycle testing.
> > 
> > This one is pretty bad. Konrad, I have the feeling somebody else
> > reported a similar bug recently... 
> 
> I did. But I think you fixed it initially, and then later on tglrx
> accepted the patch to fix this for good in generic.
> 
> I can't reproduce it anymore on 2.6.39.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Re: some old xl bugs

[Konrad Rzeszutek Wilk]

On Thu, May 26, 2011 at 02:24:31PM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, May 26, 2011 at 11:36:54AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Thu, May 26, 2011 at 04:21:23PM +0100, Stefano Stabellini wrote:
> > > thanks for the remainder
> > > 
> > > On Thu, 26 May 2011, Zhang, Yang Z wrote:
> > > > Hi Stefano
> > > > 
> > > > Here is some xl related bugs which opened for long time and I didn't see anyone working on them. I retest them with latest xen upstream and all of them are still exist.
> > > > 
> > > > 1. [XL]Fail to create multi-guests with NIC assigned
> > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1761
> > > > xm don't have the issue.
> > > > 
> > > 
> > > from the logs:
> > > 
> > > *** glibc detected *** xl: malloc(): memory corruption (fast):
> > > 
> > > it appears to be triggered by libxl_domain_create_new.
> > > Could you please add some more debug messages to xl and libxl to find
> > > out exactly what causes the memory corruption?
> 
> Weird, I seem to have something similar happening now that I updated my
> Ubuntu 11.04 box (apt-get update).

False alarm. Had the libxen* in /usr/lib and /usr/lib64 and they were both different
versions.