From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen 4.0.0 first release candidate Date: Tue, 12 Jan 2010 16:59:01 +0000 Message-ID: References: <618391.28633.qm@web56101.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <618391.28633.qm@web56101.mail.re3.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Boris Derzhavets Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Hm, nothing recent looks especially likely to cause this. Maybe c/s 20767, if the format string it modifies is still incorrect after the change. It might be interesting to revert 20767 and 20762 and see if the problem still occurs. -- Keir On 12/01/2010 15:50, "Boris Derzhavets" wrote: > I did clone of xen-unstable.hg about 10-12 days ago on the same box and it > worked. That's one of the recent CSs. > > Boris. > > --- On Tue, 1/12/10, Keir Fraser wrote: >> >> From: Keir Fraser >> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate >> To: "Boris Derzhavets" >> Cc: "xen-devel@lists.xensource.com" >> Date: Tuesday, January 12, 2010, 10:29 AM >> >> Any idea when this last worked in xen-unstable? >> >> -- Keir >> >> On 12/01/2010 15:18, "Boris Derzhavets" > > wrote: >> >>> Attempt to load Xen 4.0-rc1 with 2.6.31.6 pvops kernel on top of Ubuntu 9.04 >>> server. ( Xen 3.4.3-rc1-pre loads fine with any kernel) :- >>> dmesg :- >>> >>> . . . . . . . . >>> >>> [ 499.890371] xend[1609]: segfault at 26f9000 ip 00007f8e61f895af sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 499.905480] xend[1612]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 499.934416] xend[1620]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 499.949121] xend[1623]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 499.988220] xend[1633]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 500.013995] xend[1641]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 500.053252] xend[1652]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 500.069849] xend[1657]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 500.085520] xend[1660]: segfault at 26f9000 ip 00007f8e61f895c8 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.907064] __ratelimit: 205 callbacks suppressed >>> [ 504.907070] xend[2628]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.922303] xend[2631]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.937531] xend[2634]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.952277] xend[2638]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.966630] xend[2641]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.981380] xend[2644]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 504.996759] xend[2647]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 505..012018] xend[2650]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 505.026693] xend[2653]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> [ 505.041834] xend[2656]: segfault at 26f9000 ip 00007f8e61f895c3 sp >>> 00007f8e5e1b4e28 error 6 in libc-2.9.so[7f8e61f06000+168000] >>> >>> Boris. >>> >>> --- On Tue, 1/12/10, Keir Fraser >> > wrote: >>>> >>>> From: Keir Fraser >>> > >>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate >>>> To: "Sassy Natan" > >>>> Cc: "xen-devel@lists.xensource.com >>>> " >>>> >>> > >>>> Date: Tuesday, January 12, 2010, 6:38 AM >>>> >>>> You can use any kernel as dom0 for Xen 4.0, so long as that kernel includes >>>> dom0 support. So that could be 2.6.18, or 2.6.27 from XCI project, or >>>> Jeremy's pv_ops git tree, or some distro kernel. The kernel built by >>>> default >>>> by the Xen 4.0 build system will be Jeremy's pv_ops tree, but that doesn't >>>> mean you *have* to use it. >>>> >>>> -- Keir >>>> >>>> On 12/01/2010 11:31, "Sassy Natan" >>> >>>> > > >>>> wrote: >>>> >>>>> Hi Keir, Xen Group ... >>>>> >>>>> Just to make things more clear, I wanted to know which kernel version this >>>>> version support? >>>>> Is it still work with the old stable kernel 2.6.18 or should I grub the >>>>> new >>>>> version from Jeremy branches? >>>>> >>>>> To my understating version 4.0 of xen is plan to work by default with the >>>>> pv_ops mechanism on the dom0. >>>>> But at the moment the latest stable kernel 2.6.32.3 does not include a >>>>> dom0 >>>>> support but only domU support (both oldstyle and pv_ops). >>>>> >>>>> So, Does the release of Xen 4.0 is plan to include Dom0 support in the >>>>> kernel >>>>> mainline? >>>>> >>>>> According to Jeremy there is quite more work to do in-order to have Xen >>>>> Dom0 >>>>> support in the kernel mainline. see more here: >>>>> http://article.gmane.org/gmane.comp.emulators.xen.devel/75992 >>>>> >>>>> >>>>> Can you please provide more feedback on this issue? >>>>> >>>>> >>>>> Thanks for the support, and thanks for publishing to the open source this >>>>> amazing virtualization system. >>>>> Sassy >>>>> On Tue, Jan 12, 2010 at 9:33 AM, Keir Fraser >>>> >>>>> >>>> > > >>>>> wrote: >>>>>> Folks, >>>>>> >>>>>> The first release candidate for Xen 4.0.0 has been tagged and published. >>>>>> >>>>>> You can grab it from here: >>>>>> http://xenbits.xensource.com/xen-unstable.hg (tagged '4.0.0-rc1') >>>>>> >>>>>> Please test it! >>>>>> >>>>>> -- Keir >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-devel mailing list >>>>>> Xen-devel@lists.xensource.com >>>>>> >>>>>> >>>>> > >>>>>> http://lists.xensource.com/xen-devel >>>>> >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> >>>> >>> > >>>> http://lists.xensource.com/xen-devel >>> >>> >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > >