From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad@acsinet11.oracle.com
Subject: Re: Re: some old xl bugs
Date: Fri, 27 May 2011 10:06:35 -0400 [thread overview]
Message-ID: <20110527140635.GD6734@dumpdata.com> (raw)
In-Reply-To: <20110526182431.GA4634@dumpdata.com>
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.
prev parent reply other threads:[~2011-05-27 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 5:41 some old xl bugs Zhang, Yang Z
2011-05-26 14:53 ` Ian Jackson
2011-05-26 15:21 ` Stefano Stabellini
2011-05-26 15:36 ` Konrad Rzeszutek Wilk
2011-05-26 15:41 ` Stefano Stabellini
2011-05-26 18:24 ` Konrad Rzeszutek Wilk
2011-05-27 14:06 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110527140635.GD6734@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Konrad@acsinet11.oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).