Xen 4.0.0 first release candidate

Xen 4.0.0 first release candidate

[Keir Fraser]

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

Re: Xen 4.0.0 first release candidate

[Andrew Lyon]

On Tue, Jan 12, 2010 at 7:33 AM, Keir Fraser <keir.fraser@eu.citrix.com> 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
>

Does 4.0 include gpu passthru features? If not are there any updated
patches to try gpu passthru with 4.x?

Andy

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

On 12/01/2010 08:34, "Andrew Lyon" <andrew.lyon@gmail.com> wrote:

> Does 4.0 include gpu passthru features? If not are there any updated
> patches to try gpu passthru with 4.x?

There is support (c/s 20144).

 -- Keir

Re: Xen 4.0.0 first release candidate

[gilberto nunes]

[-- Attachment #1.1: Type: text/html, Size: 2778 bytes --]

[-- Attachment #1.2: image001.jpg --]
[-- Type: image/jpeg, Size: 16538 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

It will indeed have Remus support. I'm not sure it's terrifically well
tested, so you might exercise caution before relying on it in 4.0.0 release.

 -- Keir

On 12/01/2010 09:47, "gilberto nunes" <gilberto.nunes@selbetti.com.br>
wrote:

> hi
> 
> This release already has remus support?
> Is it stable???
> 
> Thanks
> 
> Andrew Lyon escreveu:
>>  
>> On Tue, Jan 12, 2010 at 7:33 AM, Keir Fraser <keir.fraser@eu.citrix.com>
>> <mailto:keir.fraser@eu.citrix.com>  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
>>> 
>>>     
>>>  
>>  
>> 
>> Does 4.0 include gpu passthru features? If not are there any updated
>> patches to try gpu passthru with 4.x?
>> 
>> Andy
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>   

Re: Xen 4.0.0 first release candidate

[Pasi Kärkkäinen]

On Tue, Jan 12, 2010 at 10:06:55AM +0000, Keir Fraser wrote:
> It will indeed have Remus support. I'm not sure it's terrifically well
> tested, so you might exercise caution before relying on it in 4.0.0 release.
>

And definitely test it now and report any bugs/issues found so they can
be fixed for the final release :)

-- Pasi

>  -- Keir
> 
> On 12/01/2010 09:47, "gilberto nunes" <gilberto.nunes@selbetti.com.br>
> wrote:
> 
> > hi
> > 
> > This release already has remus support?
> > Is it stable???
> > 
> > Thanks
> > 
> > Andrew Lyon escreveu:
> >>  
> >> On Tue, Jan 12, 2010 at 7:33 AM, Keir Fraser <keir.fraser@eu.citrix.com>
> >> <mailto:keir.fraser@eu.citrix.com>  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
> >>> 
> >>>     
> >>>  
> >>  
> >> 
> >> Does 4.0 include gpu passthru features? If not are there any updated
> >> patches to try gpu passthru with 4.x?
> >> 
> >> Andy
> >> 
> >> _______________________________________________
> >> 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

Re: Xen 4.0.0 first release candidate

[gilberto nunes]

Oh Yeah....

I am do this right now!! :)

I just wanna know if this remus version include on this release is the 
some from last two weeks....

I found some problems with this versions....

Thanks...

Pasi Kärkkäinen escreveu:
> On Tue, Jan 12, 2010 at 10:06:55AM +0000, Keir Fraser wrote:
>   
>> It will indeed have Remus support. I'm not sure it's terrifically well
>> tested, so you might exercise caution before relying on it in 4.0.0 release.
>>
>>     
>
> And definitely test it now and report any bugs/issues found so they can
> be fixed for the final release :)
>
> -- Pasi
>
>   
>>  -- Keir
>>
>> On 12/01/2010 09:47, "gilberto nunes" <gilberto.nunes@selbetti.com.br>
>> wrote:
>>
>>     
>>> hi
>>>
>>> This release already has remus support?
>>> Is it stable???
>>>
>>> Thanks
>>>
>>> Andrew Lyon escreveu:
>>>       
>>>>  
>>>> On Tue, Jan 12, 2010 at 7:33 AM, Keir Fraser <keir.fraser@eu.citrix.com>
>>>> <mailto:keir.fraser@eu.citrix.com>  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
>>>>>
>>>>>     
>>>>>  
>>>>>           
>>>>  
>>>>
>>>> Does 4.0 include gpu passthru features? If not are there any updated
>>>> patches to try gpu passthru with 4.x?
>>>>
>>>> Andy
>>>>
>>>> _______________________________________________
>>>> 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
>>     

-- 
*Gilberto Nunes Ferreira*
*TI*
*Selbetti Gestão de Documentos*
*Telefone: +55 (47) 3441-6004*
*Celular: +55 (47) 8861-6672*



<><

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

On 12/01/2010 10:50, "gilberto nunes" <gilberto.nunes@selbetti.com.br>
wrote:

> Oh Yeah....
> 
> I am do this right now!! :)
> 
> I just wanna know if this remus version include on this release is the
> some from last two weeks....
> 
> I found some problems with this versions....

There have been no Remus changes checked in since Christmas.

 -- Keir

Re: Xen 4.0.0 first release candidate

[gilberto nunes]

Then I expect problems agains....

After 2 or 3 minutes, remus die and Vm on back enter in boot state, and 
Vm on primary machina enter in Suspend state.... :(

It is terryble thing... :|



Keir Fraser escreveu:
> On 12/01/2010 10:50, "gilberto nunes" <gilberto.nunes@selbetti.com.br>
> wrote:
>
>   
>> Oh Yeah....
>>
>> I am do this right now!! :)
>>
>> I just wanna know if this remus version include on this release is the
>> some from last two weeks....
>>
>> I found some problems with this versions....
>>     
>
> There have been no Remus changes checked in since Christmas.
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   

-- 
*Gilberto Nunes Ferreira*
*TI*
*Selbetti Gestão de Documentos*
*Telefone: +55 (47) 3441-6004*
*Celular: +55 (47) 8861-6672*



<><

Re: Xen 4.0.0 first release candidate

[Sassy Natan]

[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]

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 <keir.fraser@eu.citrix.com>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
>

[-- Attachment #1.2: Type: text/html, Size: 2176 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

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" <sassyn@gmail.com> 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 <keir.fraser@eu.citrix.com>
> 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
> 
> 

Re: Xen 4.0.0 first release candidate

[Sassy Natan]

[-- Attachment #1.1: Type: text/plain, Size: 2174 bytes --]

OK,
Thanks for the quick answer.

Can u please tell me which branch I should download from Jeremy git server
in order to test it?

10x again
Sassy

On Tue, Jan 12, 2010 at 1:38 PM, Keir Fraser <keir.fraser@eu.citrix.com>wrote:

> 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" <sassyn@gmail.com> 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 <keir.fraser@eu.citrix.com>
> > 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
> >
> >
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3296 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

Clone the git repo from:
http://www.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
or:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
And use branch 'xen/master'.

 -- Keir

On 12/01/2010 11:48, "Sassy Natan" <sassyn@gmail.com> wrote:

> OK,
> Thanks for the quick answer.
>  
> Can u please tell me which branch I should download from Jeremy git server in
> order to test it?
>  
> 10x again
> Sassy
> 
> On Tue, Jan 12, 2010 at 1:38 PM, Keir Fraser <keir.fraser@eu.citrix.com>
> wrote:
>> 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" <sassyn@gmail.com> 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 <keir.fraser@eu.citrix.com>
>>> 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
>>> 
>>> 
>> 
>> 
> 
> 

Re: Xen 4.0.0 first release candidate

[Pasi Kärkkäinen]

On Tue, Jan 12, 2010 at 01:48:53PM +0200, Sassy Natan wrote:
>    OK,
>    Thanks for the quick answer.
> 
>    Can u please tell me which branch I should download from Jeremy git server
>    in order to test it?
>

See this wiki page for instructions:
http://wiki.xensource.com/xenwiki/XenParavirtOps

Other Xen dom0 kernels:
http://wiki.xensource.com/xenwiki/XenDom0Kernels

-- Pasi

>    10x again
>    Sassy
> 
>    On Tue, Jan 12, 2010 at 1:38 PM, Keir Fraser
>    <[1]keir.fraser@eu.citrix.com> wrote:
> 
>      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" <[2]sassyn@gmail.com> 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:
>      > [3]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
>      <[4]keir.fraser@eu.citrix.com>
>      > wrote:
>      >> Folks,
>      >>
>      >> The first release candidate for Xen 4.0.0 has been tagged and
>      published.
>      >>
>      >> You can grab it from here:
>      >> [5]http://xenbits.xensource.com/xen-unstable.hg (tagged '4.0.0-rc1')
>      >>
>      >> Please test it!
>      >>
>      >>  -- Keir
>      >>
>      >>
>      >>
>      >> _______________________________________________
>      >> Xen-devel mailing list
>      >> [6]Xen-devel@lists.xensource.com
>      >> [7]http://lists.xensource.com/xen-devel
>      >
>      >
> 
> References
> 
>    Visible links
>    1. mailto:keir.fraser@eu.citrix.com
>    2. mailto:sassyn@gmail.com
>    3. http://article.gmane.org/gmane.comp.emulators.xen.devel/75992
>    4. mailto:keir.fraser@eu.citrix.com
>    5. http://xenbits.xensource.com/xen-unstable.hg
>    6. mailto:Xen-devel@lists.xensource.com
>    7. http://lists.xensource.com/xen-devel

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

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 5132 bytes --]

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 <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Sassy Natan" <sassyn@gmail.com>
Cc: "xen-devel@lists.xensource.com" <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" <sassyn@gmail.com> 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 <keir.fraser@eu.citrix.com>
> 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



      

[-- Attachment #1.2: Type: text/html, Size: 6694 bytes --]

[-- Attachment #2: dmesg-xen-4.log.gz --]
[-- Type: application/x-gzip, Size: 18565 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

Any idea when this last worked in xen-unstable?

 -- Keir

On 12/01/2010 15:18, "Boris Derzhavets" <bderzhavets@yahoo.com> 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 <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Sassy Natan" <sassyn@gmail.com>
>> Cc: "xen-devel@lists.xensource.com" <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" <sassyn@gmail.com
>> </mc/compose?to=sassyn@gmail..com> > 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
>>> <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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>> 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
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> http://lists.xensource.com/xen-devel
>>> 
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 6439 bytes --]

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 <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <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" <bderzhavets@yahoo.com> 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 <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Sassy Natan" <sassyn@gmail.com>
>> Cc: "xen-devel@lists.xensource.com" <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" <sassyn@gmail.com
>> </mc/compose?to=sassyn@gmail..com> > 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
>>> <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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>> 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
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> http://lists.xensource.com/xen-devel
>>> 
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=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



      

[-- Attachment #1.2: Type: text/html, Size: 10010 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

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" <bderzhavets@yahoo.com> 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 <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <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" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > 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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>> </mc/compose?to=sassyn@gmail.com>
>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> > >
>>>> 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
>>>>> <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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>> 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
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 8494 bytes --]

Sorry, i need an exact commands to revert to two CSs.
Googling doesn't help for sure. Otherwise , it doesn't make sense.

Boris.


--- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, January 12, 2010, 11:59 AM

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" <bderzhavets@yahoo.com> 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 <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <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" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > 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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>> </mc/compose?to=sassyn@gmail.com>
>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> > >
>>>> 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
>>>>> <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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>> 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
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=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



      

[-- Attachment #1.2: Type: text/html, Size: 15693 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

hg export 20762 | patch -Rp1
hg export 20767 | patch -Rp1
...then rebuild and reinstall Xen and dom0 tools.
Afterwards, to revert the above:
hg diff | patch -Rp1

 -- Keir

On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> Sorry, i need an exact commands to revert to two CSs.
> Googling doesn't help for sure. Otherwise , it doesn't make sense.
> 
> Boris.
> 
> 
> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Tuesday, January 12, 2010, 11:59 AM
>> 
>> 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" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > 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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>> 
>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>> <xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> > >
>>>>>> >
>>>>>> 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
>>>>>>> <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 <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> >
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>> 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
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>>  
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 12935 bytes --]

I cannot handle that :-

root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
patching file tools/python/xen/lowlevel/xc/xc.c
Unreversed patch detected!  Ignore -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 1078.
Hunk #2 FAILED at 1105.
Hunk #3 FAILED at 1117.
3 out of 3 hunks FAILED -- saving rejects to file tools/python/xen/lowlevel/xc/xc.c.rej
patching file xen/arch/ia64/xen/dom0_ops.c
Unreversed patch detected!  Ignore -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 715.
1 out of 1 hunk FAILED -- saving rejects to file xen/arch/ia64/xen/dom0_ops..c.rej
patching file xen/arch/x86/sysctl.c
Unreversed patch detected!  Ignore -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 75.
2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
patching file xen/include/public/sysctl.h
Unreversed patch detected!  Ignore -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 94.
2 out of 2 hunks FAILED -- saving rejects to file xen/include/public/sysctl..h.rej
patching file xen/include/xen/nodemask.h
Unreversed patch detected!  Ignore -R? [n] -R
Apply anyway? [n] y
Hunk #1 FAILED at 38.
Hunk #2 FAILED at 214.
2 out of 2 hunks FAILED -- saving rejects to file xen/include/xen/nodemask.h.rej



--- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, January 12, 2010, 2:32 PM

hg export 20762 | patch -Rp1
hg export 20767 | patch -Rp1
....then rebuild and reinstall Xen and dom0 tools.
Afterwards, to revert the above:
hg diff | patch -Rp1

 -- Keir

On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> Sorry, i need an exact commands to revert to two CSs.
> Googling doesn't help for sure. Otherwise , it doesn't make sense.
> 
> Boris.
> 
> 
> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Tuesday, January 12, 2010, 11:59 AM
>> 
>> 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" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > 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 <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>> 
>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>> <xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> > >
>>>>>> >
>>>>>> 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
>>>>>>> <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 <keir.fraser@eu.citrix..com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> >
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>> 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
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>>  
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=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



      

[-- Attachment #1.2: Type: text/html, Size: 26981 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

Weird, looks like the changesets are not applied to your checked-out copy of
the tree. What happens if you try 'hg update tip' first? The other option is
to binary-chop changesets between tip (c/s 20790) and the last known good
changeset:
hg update 20750 (for example)
Build, install, test...
hg update 20770 (if previous test succeeded, meaning bug is between
changesets 20751 and 20790)
Build, install, test...

And so on. Rather tedious unfortunately.

 -- Keir

On 12/01/2010 19:52, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> I cannot handle that :-
> 
> root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
> patching file tools/python/xen/lowlevel/xc/xc.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 1078.
> Hunk #2 FAILED at 1105.
> Hunk #3 FAILED at 1117.
> 3 out of 3 hunks FAILED -- saving rejects to file
> tools/python/xen/lowlevel/xc/xc.c.rej
> patching file xen/arch/ia64/xen/dom0_ops.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 715.
> 1 out of 1 hunk FAILED -- saving rejects to file
> xen/arch/ia64/xen/dom0_ops.c.rej
> patching file xen/arch/x86/sysctl.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 64.
> Hunk #2 FAILED at 75.
> 2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
> patching file xen/include/public/sysctl.h
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 34.
> Hunk #2 FAILED at 94.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/public/sysctl.h.rej
> patching file xen/include/xen/nodemask.h
> Unreversed patch detected!  Ignore -R? [n] -R
> Apply anyway? [n] y
> Hunk #1 FAILED at 38.
> Hunk #2 FAILED at 214.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/xen/nodemask.h.rej
> 
> 
> 
> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Tuesday, January 12, 2010, 2:32 PM
>> 
>> hg export 20762 | patch -Rp1
>> hg export 20767 | patch -Rp1
>> ...then rebuild and reinstall Xen and dom0 tools.
>> Afterwards, to revert the above:
>> hg diff | patch -Rp1
>> 
>>  -- Keir
>> 
>> On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > wrote:
>> 
>>> Sorry, i need an exact commands to revert to two CSs.
>>> Googling doesn't help for sure. Otherwise , it doesn't make sense.
>>> 
>>> Boris.
>>> 
>>> 
>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>> Date: Tuesday, January 12, 2010, 11:59 AM
>>>> 
>>>> 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" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>> 
>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > >
>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>> <xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > > 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 <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > wrote:
>>>>>>>> 
>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> >
>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > > "
>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com> >
>>>>>>>> > >
>>>>>>>>> 
>>>>>>>> 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
>>>>>>>>> <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
>>>>>>>>> <keir.fraser@eu.citrix.com </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> > >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > >
>>>>>>>>> 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
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Xen-devel mailing list
>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> 
>>>>>>>  
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>>  
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 23487 bytes --]

Just performed fresh clone , build and install xen 4.0-rc2-pre:-

Recent CSc :-

changeset:   20796:13d4e78ede97
tag:         tip
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:33:34 2010 +0000
summary:     x86 hvm: Change default setting of guest CPUID RDTSCP bit

changeset:   20795:6512068aa0db
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:18:38 2010 +0000
summary:     x86: fix unmaskable msi assignment issue.

changeset:   20794:3f8fd65732cc
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:17:00 2010 +0000
summary:     x86: minor cleanup to arch_memory_op()

changeset:   20793:4573383ec3dd
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:16:37 2010 +0000
summary:     Update Xen version to 4.0.0-rc2-pre

...........................

Attempt to start xend:-

root@ServerJaunty:~# /etc/init.d/xend start
Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory


Boris.

--- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, January 12, 2010, 4:09 PM

Weird, looks like the changesets are not applied to your checked-out copy of
the tree. What happens if you try 'hg update tip' first? The other option is
to binary-chop changesets between tip (c/s 20790) and the last known good
changeset:
hg update 20750 (for example)
Build, install, test...
hg update 20770 (if previous test succeeded, meaning bug is between
changesets 20751 and 20790)
Build, install, test...

And so on. Rather tedious unfortunately.

 -- Keir

On 12/01/2010 19:52, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> I cannot handle that :-
> 
> root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
> patching file tools/python/xen/lowlevel/xc/xc.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 1078.
> Hunk #2 FAILED at 1105.
> Hunk #3 FAILED at 1117.
> 3 out of 3 hunks FAILED -- saving rejects to file
> tools/python/xen/lowlevel/xc/xc.c.rej
> patching file xen/arch/ia64/xen/dom0_ops.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 715.
> 1 out of 1 hunk FAILED -- saving rejects to file
> xen/arch/ia64/xen/dom0_ops.c.rej
> patching file xen/arch/x86/sysctl.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 64.
> Hunk #2 FAILED at 75.
> 2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
> patching file xen/include/public/sysctl.h
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 34.
> Hunk #2 FAILED at 94.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/public/sysctl.h.rej
> patching file xen/include/xen/nodemask.h
> Unreversed patch detected!  Ignore -R? [n] -R
> Apply anyway? [n] y
> Hunk #1 FAILED at 38.
> Hunk #2 FAILED at 214.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/xen/nodemask.h.rej
> 
> 
> 
> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Tuesday, January 12, 2010, 2:32 PM
>> 
>> hg export 20762 | patch -Rp1
>> hg export 20767 | patch -Rp1
>> ...then rebuild and reinstall Xen and dom0 tools.
>> Afterwards, to revert the above:
>> hg diff | patch -Rp1
>> 
>>  -- Keir
>> 
>> On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > wrote:
>> 
>>> Sorry, i need an exact commands to revert to two CSs.
>>> Googling doesn't help for sure. Otherwise , it doesn't make sense.
>>> 
>>> Boris.
>>> 
>>> 
>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>> Date: Tuesday, January 12, 2010, 11:59 AM
>>>> 
>>>> 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" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>> 
>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > >
>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>> <xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > > 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 <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > wrote:
>>>>>>>> 
>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>>> To: "Sassy Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail..com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> >
>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > > "
>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com> >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com> >
>>>>>>>> > >
>>>>>>>>> 
>>>>>>>> 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
>>>>>>>>> <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
>>>>>>>>> <keir.fraser@eu.citrix.com </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com> > >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > >
>>>>>>>>> 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
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Xen-devel mailing list
>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> 
>>>>>>>  
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>>  
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  





      

[-- Attachment #1.2: Type: text/html, Size: 51598 bytes --]

[-- Attachment #2: dmesg011310.log.gz --]
[-- Type: application/x-gzip, Size: 13723 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 24861 bytes --]

root@ServerJaunty:/# find . -name "libxenctrl.so.*"  -print

../usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0
../usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0.0
../usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0
../usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0.0

../usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4
../usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4.0
../usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4
../usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4.0

../usr/lib/libxenctrl.so.4.0
../usr/lib/libxenctrl.so.4.0.0

Due to :

# cd xen-unstable.hg
# make uninstall
# make install-xen
# make install-tools

Boris.

--- On Wed, 1/13/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Keir Fraser" <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Wednesday, January 13, 2010, 5:26 AM

Just performed fresh clone , build and install xen 4.0-rc2-pre:-

Recent CSc :-

changeset:   20796:13d4e78ede97
tag:         tip
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:33:34 2010 +0000
summary:     x86 hvm: Change default setting of guest CPUID RDTSCP bit

changeset:   20795:6512068aa0db
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:18:38 2010 +0000
summary:     x86: fix unmaskable msi assignment issue.

changeset:   20794:3f8fd65732cc
user:        Keir
 Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:17:00 2010 +0000
summary:     x86: minor cleanup to arch_memory_op()

changeset:   20793:4573383ec3dd
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Wed Jan 13 08:16:37 2010 +0000
summary:     Update Xen version to 4.0.0-rc2-pre

............................

Attempt to start xend:-

root@ServerJaunty:~# /etc/init.d/xend start
Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open
 shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in
 <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen..xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or
 directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen.lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory
..Traceback (most recent call last):
  File "/usr/sbin/xend", line 36, in <module>
    from xen.xend.server import
 SrvDaemon
  File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line 20, in <module>
    import xen..lowlevel.xc
ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file or directory


Boris.

--- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Tuesday, January 12, 2010, 4:09 PM

Weird, looks like the changesets are not applied to your checked-out copy of
the tree. What happens if you try 'hg update tip' first? The other option is
to
 binary-chop changesets between tip (c/s 20790) and the last known good
changeset:
hg update 20750 (for example)
Build, install, test...
hg update 20770 (if previous test succeeded, meaning bug is between
changesets 20751 and 20790)
Build, install, test...

And so on. Rather tedious unfortunately.

 -- Keir

On 12/01/2010 19:52, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> I cannot handle that :-
> 
> root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
> patching file tools/python/xen/lowlevel/xc/xc.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 1078.
> Hunk #2 FAILED at 1105.
> Hunk #3 FAILED at 1117.
> 3 out of 3 hunks FAILED -- saving rejects to file
>
 tools/python/xen/lowlevel/xc/xc.c.rej
> patching file xen/arch/ia64/xen/dom0_ops.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 715.
> 1 out of 1 hunk FAILED -- saving rejects to file
> xen/arch/ia64/xen/dom0_ops.c..rej
> patching file xen/arch/x86/sysctl.c
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 64.
> Hunk #2 FAILED at 75.
> 2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
> patching file xen/include/public/sysctl.h
> Unreversed patch detected!  Ignore -R? [n] n
> Apply anyway? [n] y
> Hunk #1 FAILED at 34.
> Hunk #2 FAILED at 94.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/public/sysctl.h.rej
> patching file xen/include/xen/nodemask.h
> Unreversed patch detected! 
 Ignore -R? [n] -R
> Apply anyway? [n] y
> Hunk #1 FAILED at 38..
> Hunk #2 FAILED at 214.
> 2 out of 2 hunks FAILED -- saving rejects to file
> xen/include/xen/nodemask.h.rej
> 
> 
> 
> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> 
>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>> Cc: "xen-devel@lists.xensource.com"
 <xen-devel@lists.xensource.com>
>> Date: Tuesday, January 12, 2010, 2:32 PM
>> 
>> hg export 20762 | patch -Rp1
>> hg export 20767 | patch -Rp1
>> ...then rebuild and reinstall Xen and dom0 tools.
>> Afterwards, to revert the above:
>> hg diff | patch -Rp1
>> 
>>  -- Keir
>> 
>> On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com
>> </mc/compose?to=bderzhavets@yahoo.com> > wrote:
>> 
>>> Sorry, i need an exact commands to revert to two CSs.
>>> Googling doesn't help for sure. Otherwise , it doesn't
 make sense.
>>> 
>>> Boris.
>>> 
>>> 
>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com
>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>> 
>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo..com> >
>>>> Cc: "xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>> <xen-devel@lists.xensource.com
>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>> Date: Tuesday, January 12,
 2010, 11:59 AM
>>>> 
>>>> 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" <bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>> 
>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>> Subject: Re: [Xen-devel] Xen 4..0.0 first release
 candidate
>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > >
>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>> <xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>>>> </mc/compose?to=bderzhavets@yahoo..com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > >
 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 <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > wrote:
>>>>>>>> 
>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>>> To: "Sassy
 Natan" <sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> >
>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>>
 </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > > "
>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>>
 </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> > >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com> >
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com>
>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail...com> >
>>>>>>>> > >
>>>>>>>>> 
>>>>>>>> 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
>>>>>>>>> <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
>>>>>>>>> <keir.fraser@eu.citrix.com </mc/compose?to=keir.fraser@eu.citrix..com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir...fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir...fraser@eu.citrix.com> > >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > >
>>>>>>>>> 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
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>>
 </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>> 
>>>>>>>>>
 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Xen-devel mailing list
>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>> 
>>>>>>>  
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing
 list
>>>>>> Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>>>  
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>> http://lists.xensource.com/xen-devel
>>> 
>>>  
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  





      
-----Inline Attachment Follows-----

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



      

[-- Attachment #1.2: Type: text/html, Size: 40994 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Keir Fraser]

Yes, the libxenctrl and libxenguest version numbers got bumped. I assume
your xend start failure was because you installed fresh libxenctrl but
didn't upgrade the xend xc.so extension package, which is therefore linked
against the old no-longer-existing version of libxenctrl.

 -- Keir

On 13/01/2010 10:37, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> root@ServerJaunty:/# find . -name "libxenctrl..so.*"  -print
> 
> ./usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0
> ./usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0.0
> ./usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0
> ./usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0.0
> 
> ./usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4
> ./usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4.0
> ./usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4
> ./usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4.0
> 
> ./usr/lib/libxenctrl.so.4.0
> ./usr/lib/libxenctrl.so.4.0.0
> 
> Due to :
> 
> # cd xen-unstable.hg
> # make uninstall
> # make install-xen
> # make install-tools
> 
> Boris.
> 
> --- On Wed, 1/13/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
>> 
>> From: Boris Derzhavets <bderzhavets@yahoo.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Keir Fraser" <keir..fraser@eu.citrix.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Wednesday, January 13, 2010, 5:26 AM
>> 
>> Just performed fresh clone , build and install xen 4.0-rc2-pre:-
>> 
>> Recent CSc :-
>> 
>> changeset:   20796:13d4e78ede97
>> tag:         tip
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:33:34 2010 +0000
>> summary:     x86 hvm: Change default setting of guest CPUID RDTSCP bit
>> 
>> changeset:   20795:6512068aa0db
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:18:38 2010 +0000
>> summary:     x86: fix unmaskable msi assignment issue.
>> 
>> changeset:   20794:3f8fd65732cc
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:17:00 2010 +0000
>> summary:     x86: minor cleanup to arch_memory_op()
>> 
>> changeset:   20793:4573383ec3dd
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:16:37 2010 +0000
>> summary:     Update Xen version to 4.0.0-rc2-pre
>> 
>> ............................
>> 
>> Attempt to start xend:-
>> 
>> root@ServerJaunty:~# /etc/init.d/xend start
>> Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen..xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen..xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2..6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen..lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> 
>> 
>> Boris.
>> 
>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>>> 
>>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>>> Date: Tuesday, January 12, 2010, 4:09 PM
>>> 
>>> Weird, looks like the changesets are not applied to your checked-out copy of
>>> the tree. What happens if you try 'hg update tip' first? The other option is
>>> to binary-chop changesets between tip (c/s 20790) and the last known good
>>> changeset:
>>> hg update 20750 (for example)
>>> Build, install, test...
>>> hg update 20770 (if previous test succeeded, meaning bug is between
>>> changesets 20751 and 20790)
>>> Build, install, test...
>>> 
>>> And so on. Rather tedious unfortunately..
>>> 
>>>  -- Keir
>>> 
>>> On 12/01/2010 19:52, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:
>>> 
>>>> I cannot handle that :-
>>>> 
>>>> root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
>>>> patching file tools/python/xen/lowlevel/xc/xc.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 1078.
>>>> Hunk #2 FAILED at 1105.
>>>> Hunk #3 FAILED at 1117.
>>>> 3 out of 3 hunks FAILED -- saving rejects to file
>>>> tools/python/xen/lowlevel/xc/xc.c.rej
>>>> patching file xen/arch/ia64/xen/dom0_ops.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 715.
>>>> 1 out of 1 hunk FAILED -- saving rejects to file
>>>> xen/arch/ia64/xen/dom0_ops.c..rej
>>>> patching file xen/arch/x86/sysctl.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 64.
>>>> Hunk #2 FAILED at 75.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
>>>> patching file xen/include/public/sysctl.h
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 34.
>>>> Hunk #2 FAILED at 94.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file
>>>> xen/include/public/sysctl..h.rej
>>>> patching file xen/include/xen/nodemask.h
>>>> Unreversed patch detected!  Ignore -R? [n] -R
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 38..
>>>> Hunk #2 FAILED at 214.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file
>>>> xen/include/xen/nodemask.h..rej
>>>> 
>>>> 
>>>> 
>>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>>>>> 
>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>>>>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>>>>> Date: Tuesday, January 12, 2010, 2:32 PM
>>>>> 
>>>>> hg export 20762 | patch -Rp1
>>>>> hg export 20767 | patch -Rp1
>>>>> ...then rebuild and reinstall Xen and dom0 tools.
>>>>> Afterwards, to revert the above:
>>>>> hg diff | patch -Rp1
>>>>> 
>>>>>  -- Keir
>>>>> 
>>>>> On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>> </mc/compose?to=bderzhavets@yahoo.com> > wrote:
>>>>> 
>>>>>> Sorry, i need an exact commands to revert to two CSs.
>>>>>> Googling doesn't help for sure. Otherwise , it doesn't make sense.
>>>>>> 
>>>>>> Boris.
>>>>>> 
>>>>>> 
>>>>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>>>>> 
>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo..com> >
>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>>>>> <xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>> Date: Tuesday, January 12, 2010, 11:59 AM
>>>>>>> 
>>>>>>> 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" <bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>>>>> 
>>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>>>>> Subject: Re: [Xen-devel] Xen 4..0.0 first release candidate
>>>>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > >
>>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource..com
>>>>>>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo..com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > > 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 <keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > wrote:
>>>>>>>>>>> 
>>>>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>>>>>> To: "Sassy Natan" <sassyn@gmail.com
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> >
>>>>>>>>>>>> 
>>>>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > > "
>>>>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> >
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 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
>>>>>>>>>>>> <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
>>>>>>>>>>>> <keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix..com>
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir....fraser@eu.citrix.com> >
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir...fraser@eu.citrix.com> > >
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix..com>
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > >
>>>>>>>>>>>> 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
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Xen-devel mailing list
>>>>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>>> 
>>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Xen-devel mailing list
>>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>> 
>>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Xen-devel mailing list
>>>>>>> Xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>> http://lists.xensource.com/xen-devel
>>>>>> 
>>>>>>  
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>> http://lists.xensource.com/xen-devel
>>>> 
>>>>  
>>> 
>>> 
>> 
>>  
>> 
>> -----Inline Attachment Follows-----
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
> 
>  

Re: Xen 4.0.0 first release candidate

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 27732 bytes --]

Thank you. My mistake.

--- On Wed, 1/13/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:

From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Wednesday, January 13, 2010, 6:03 AM

Yes, the libxenctrl and libxenguest version numbers got bumped. I assume
your xend start failure was because you installed fresh libxenctrl but
didn't upgrade the xend xc.so extension package, which is therefore linked
against the old no-longer-existing version of libxenctrl.

 -- Keir

On 13/01/2010 10:37, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:

> root@ServerJaunty:/# find . -name "libxenctrl..so.*"  -print
> 
> ./usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0
> ./usr/src/xen-unstable.hg/dist/install/usr/lib64/libxenctrl.so.4.0.0
> ./usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0
> ./usr/src/xen-unstable.hg/tools/libxc/libxenctrl.so.4.0.0
> 
> ./usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4
> ./usr/src/xen-3.4-testing.hg/dist/install/usr/lib64/libxenctrl.so.3.4.0
> ./usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4
> ./usr/src/xen-3.4-testing.hg/tools/libxc/libxenctrl.so.3.4.0
> 
> ./usr/lib/libxenctrl.so.4.0
> ./usr/lib/libxenctrl.so.4.0.0
> 
> Due to :
> 
> # cd xen-unstable.hg
> # make uninstall
> # make install-xen
> # make install-tools
> 
> Boris.
> 
> --- On Wed, 1/13/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
>> 
>> From: Boris Derzhavets <bderzhavets@yahoo.com>
>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>> To: "Keir Fraser" <keir..fraser@eu.citrix.com>
>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>> Date: Wednesday, January 13, 2010, 5:26 AM
>> 
>> Just performed fresh clone , build and install xen 4.0-rc2-pre:-
>> 
>> Recent CSc :-
>> 
>> changeset:   20796:13d4e78ede97
>> tag:         tip
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:33:34 2010 +0000
>> summary:     x86 hvm: Change default setting of guest CPUID RDTSCP bit
>> 
>> changeset:   20795:6512068aa0db
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:18:38 2010 +0000
>> summary:     x86: fix unmaskable msi assignment issue.
>> 
>> changeset:   20794:3f8fd65732cc
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:17:00 2010 +0000
>> summary:     x86: minor cleanup to arch_memory_op()
>> 
>> changeset:   20793:4573383ec3dd
>> user:        Keir Fraser <keir.fraser@citrix.com>
>> date:        Wed Jan 13 08:16:37 2010 +0000
>> summary:     Update Xen version to 4.0.0-rc2-pre
>> 
>> ............................
>> 
>> Attempt to start xend:-
>> 
>> root@ServerJaunty:~# /etc/init.d/xend start
>> Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon...py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen..xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon...py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen..xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2..6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in <module>
>>     import xen.lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> .Traceback (most recent call last):
>>   File "/usr/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon..py", line
>> 20, in <module>
>>     import xen..lowlevel.xc
>> ImportError: libxenctrl.so.3.4: cannot open shared object file: No such file
>> or directory
>> 
>> 
>> Boris.
>> 
>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>>> 
>>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>>> Date: Tuesday, January 12, 2010, 4:09 PM
>>> 
>>> Weird, looks like the changesets are not applied to your checked-out copy of
>>> the tree. What happens if you try 'hg update tip' first? The other option is
>>> to binary-chop changesets between tip (c/s 20790) and the last known good
>>> changeset:
>>> hg update 20750 (for example)
>>> Build, install, test...
>>> hg update 20770 (if previous test succeeded, meaning bug is between
>>> changesets 20751 and 20790)
>>> Build, install, test...
>>> 
>>> And so on. Rather tedious unfortunately..
>>> 
>>>  -- Keir
>>> 
>>> On 12/01/2010 19:52, "Boris Derzhavets" <bderzhavets@yahoo.com> wrote:
>>> 
>>>> I cannot handle that :-
>>>> 
>>>> root@ServerJaunty:/usr/src/xen-unstable.hg# hg export 20762 | patch -Rp1
>>>> patching file tools/python/xen/lowlevel/xc/xc.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 1078.
>>>> Hunk #2 FAILED at 1105.
>>>> Hunk #3 FAILED at 1117.
>>>> 3 out of 3 hunks FAILED -- saving rejects to file
>>>> tools/python/xen/lowlevel/xc/xc.c.rej
>>>> patching file xen/arch/ia64/xen/dom0_ops.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 715.
>>>> 1 out of 1 hunk FAILED -- saving rejects to file
>>>> xen/arch/ia64/xen/dom0_ops.c..rej
>>>> patching file xen/arch/x86/sysctl.c
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 64.
>>>> Hunk #2 FAILED at 75.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file xen/arch/x86/sysctl.c.rej
>>>> patching file xen/include/public/sysctl.h
>>>> Unreversed patch detected!  Ignore -R? [n] n
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 34.
>>>> Hunk #2 FAILED at 94.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file
>>>> xen/include/public/sysctl..h.rej
>>>> patching file xen/include/xen/nodemask.h
>>>> Unreversed patch detected!  Ignore -R? [n] -R
>>>> Apply anyway? [n] y
>>>> Hunk #1 FAILED at 38..
>>>> Hunk #2 FAILED at 214.
>>>> 2 out of 2 hunks FAILED -- saving rejects to file
>>>> xen/include/xen/nodemask.h..rej
>>>> 
>>>> 
>>>> 
>>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>>>>> 
>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com>
>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>>>>> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>>>>> Date: Tuesday, January 12, 2010, 2:32 PM
>>>>> 
>>>>> hg export 20762 | patch -Rp1
>>>>> hg export 20767 | patch -Rp1
>>>>> ...then rebuild and reinstall Xen and dom0 tools.
>>>>> Afterwards, to revert the above:
>>>>> hg diff | patch -Rp1
>>>>> 
>>>>>  -- Keir
>>>>> 
>>>>> On 12/01/2010 18:34, "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>> </mc/compose?to=bderzhavets@yahoo.com> > wrote:
>>>>> 
>>>>>> Sorry, i need an exact commands to revert to two CSs.
>>>>>> Googling doesn't help for sure. Otherwise , it doesn't make sense.
>>>>>> 
>>>>>> Boris.
>>>>>> 
>>>>>> 
>>>>>> --- On Tue, 1/12/10, Keir Fraser <keir.fraser@eu.citrix.com
>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > wrote:
>>>>>>> 
>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo..com> >
>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> "
>>>>>>> <xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>> Date: Tuesday, January 12, 2010, 11:59 AM
>>>>>>> 
>>>>>>> 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" <bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > 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 <keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > wrote:
>>>>>>>>> 
>>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > >
>>>>>>>>> Subject: Re: [Xen-devel] Xen 4..0.0 first release candidate
>>>>>>>>> To: "Boris Derzhavets" <bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > >
>>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > "
>>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource..com
>>>>>>>>> </mc/compose?to=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" <bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> >
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo..com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com>
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com
>>>>>>>>> </mc/compose?to=bderzhavets@yahoo.com> > > > 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 <keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com>
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > wrote:
>>>>>>>>>>> 
>>>>>>>>>>> From: Keir Fraser <keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > >
>>>>>>>>>>> Subject: Re: [Xen-devel] Xen 4.0.0 first release candidate
>>>>>>>>>>> To: "Sassy Natan" <sassyn@gmail.com
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> >
>>>>>>>>>>>> 
>>>>>>>>>>> Cc: "xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> > > "
>>>>>>>>>>> <xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=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" <sassyn@gmail.com
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail.com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail.com </mc/compose?to=sassyn@gmail.com> >
>>>>>>>>>>> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> >
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> </mc/compose?to=sassyn@gmail..com </mc/compose?to=sassyn@gmail..com>
>>>>>>>>>>> >
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 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
>>>>>>>>>>>> <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
>>>>>>>>>>>> <keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix..com>
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir....fraser@eu.citrix.com> >
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com>
>>>>>>>>>>>> </mc/compose?to=keir..fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir...fraser@eu.citrix.com> > >
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix..com>
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> >
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu..citrix.com>
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com
>>>>>>>>>>>> </mc/compose?to=keir.fraser@eu.citrix.com> > > > >
>>>>>>>>>>>> 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
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Xen-devel mailing list
>>>>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > > >
>>>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>>>> 
>>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> Xen-devel mailing list
>>>>>>>>> Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> > >
>>>>>>>>> http://lists.xensource.com/xen-devel
>>>>>>>> 
>>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Xen-devel mailing list
>>>>>>> Xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com
>>>>>>> </mc/compose?to=Xen-devel@lists.xensource.com> >
>>>>>>> http://lists.xensource.com/xen-devel
>>>>>> 
>>>>>>  
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> </mc/compose?to=Xen-devel@lists.xensource.com>
>>>>> http://lists.xensource.com/xen-devel
>>>> 
>>>>  
>>> 
>>> 
>> 
>>  
>> 
>> -----Inline Attachment Follows-----
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com </mc/compose?to=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



      

[-- Attachment #1.2: Type: text/html, Size: 63560 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Stefan Kuhne]

[-- Attachment #1.1: Type: text/plain, Size: 266 bytes --]

Keir Fraser schrieb:

Hello,
> 
> You can grab it from here:
> http://xenbits.xensource.com/xen-unstable.hg (tagged '4.0.0-rc1')
> 
how can i get it?

git clone http://xenbits.xensource.com/xen-unstable.hg RC-1

doesn't work.

Regards,
Stefan Kuhne


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Stefan Kuhne]

[-- Attachment #1.1: Type: text/plain, Size: 313 bytes --]

Stefan Kuhne schrieb:
> Keir Fraser schrieb:
> 
> Hello,
>> You can grab it from here:
>> http://xenbits.xensource.com/xen-unstable.hg (tagged '4.0.0-rc1')
>>
> how can i get it?
> 
I've got it with:

hg clone -r 4.0.0-rc1 http://xenbits.xensource.com/xen-unstable.hg RC-1

Regards,
Stefan Kuhne


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen 4.0.0 first release candidate

[Zhigang Wang]

Stefan Kuhne wrote:
> Keir Fraser schrieb:
> 
> Hello,
>> You can grab it from here:
>> http://xenbits.xensource.com/xen-unstable.hg (tagged '4.0.0-rc1')
>>
> how can i get it?
> 
> git clone http://xenbits.xensource.com/xen-unstable.hg RC-1
> 
> doesn't work.
> 
> Regards,
> Stefan Kuhne
> 

hg clone http://xenbits.xensource.com/xen-unstable.hg

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