Re: [Xen-devel] Re: Attempt to backport changeset-23088, changeset-23089 to Xen 4.1.1- Notice of Ian Campbell

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

On 29.07.2011 00:02, Boris Derzhavets wrote:
> ******************************************
> I found this notice of Ian Campbell 
> ******************************************
> 
> Re: [Xen-devel] Re: Problem with Xen 4.1 on Ubuntu 11.10 ( Oneiric Ocelot) 
> (HVM DomUs crash) Wednesday, July 20, 2011 4:19 AM
> From: "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
> Add sender to Contacts 
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc:"Stefano Stabellini" <Stefano.Stabellini@xxxxxxxxxxxxx>, 
> "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir 
> Fraser" <keir@xxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> 
> 
> I unpacked 4.1.0-3ubuntu4, which appears to be current in Oneiric (and
> looks a lot like the Debian Sid package), the only potentially
> interesting patch is
> debian/patches/tools-firmware-etherboot-packaged.diff which switches
> from the ipxe in the Xen tree to the packaged one from /usr/lib/ipxe.
> 

Just to note that there is a newer (4.1.1) package pending to be build but got
stuck because of dependency problems after having it promoted from universe to 
main.

-Stefan

> Both Ubuntu Oneiric and Debian Sid appear to contain ipxe 1.0.0
> +git-1.293e34-2 whereas the Xen tree embeds v1.0.0 itself. Could be
> worth investigating.
> 
> Ian.
> 
> -----------------------------------------------------------------------------------------------------------------------------
> 
> Same file is in  XEN 4.1.1 Ubuntu Oneiric packaging :
> 
> boris@boris-System-P5Q3:~/CHUCK-STUFF/xen-4.1.1/debian/patches$ ls -l 
> tools-firmware-etherboot-packaged.diff
> 
> -rw-r--r-- 1 boris boris 1464 2011-07-28 21:17 
> tools-firmware-etherboot-packaged.diff
> 
> 
> Boris.
> --- On Thu, 7/28/11, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> 
> From: Keir Fraser <keir.xen@xxxxxxxxx>
> Subject: Re: [Xen-devel] Re: Attempt to backport changeset-23088, 
> changeset-23089 to Xen 4.1.1
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>, 
> "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad 
> Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> Date: Thursday, July 28, 2011, 3:53 PM
> 
> On 28/07/2011 20:41, "Boris Derzhavets" <bderzhavets@xxxxxxxxx> wrote:
> 
>> Only 3 CSs backported :-
>> changeset 23104  - No problems . HVM fix
>> Next step =>  23088 and 23089 .  This step causes build failure.
> 
> Is that 23089:8ec7808f9c23 and 23088:49728fe8dd6a? There is zero chance of
> either of those being the cause of a build failure under tools/firmware.
> 
>  -- Keir
> 
>> Boris.
>>
>> --- On Thu, 7/28/11, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>>>
>>> From: Keir Fraser <keir.xen@xxxxxxxxx>
>>> Subject: [Xen-devel] Re: Attempt to backport changeset-23088, 
>>> changeset-23089
>>> to Xen 4.1.1
>>> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
>>> Cc: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>,
>>> "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad
>>> Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
>>> Date: Thursday, July 28, 2011, 3:04 PM
>>>
>>> On 28/07/2011 18:58, "Boris Derzhavets" <bderzhavets@xxxxxxxxx
>>> </mc/compose?to=bderzhavets@xxxxxxxxx> > wrote:
>>>
>>>> Build  error :-
>>>
>>> The stated changesets don't touch tools/firmware. They're unlikely to be
>>> causing your build failure.
>>>
>>>   -- Keir
>>>
>>>> Calculated checksum:  0x44  Setting checksum.
>>>> ls -l VGABIOS-lgpl-latest.cirrus.debug.bin
>>>> -rw-rw-r-- 1 buildd buildd 35840 Jul 28 17:27
>>>> VGABIOS-lgpl-latest.cirrus.debug.bin
>>>> make[8]: Leaving directory
>>>>
>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/vgabio
>>> s>
>>> '
>>>> make[7]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>>> make[7]: Entering directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>>> /usr/bin/make -C etherboot all
>>>> make[8]: Entering directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/ether
>>>> bo
>>>> ot'
>>>> make[8]: *** No rule to make target `/usr/lib/ipxe/rtl8139.rom', needed by
>>>> `eb-roms.h'.  Stop.
>>>> make[8]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware/ether
>>>> bo
>>>> ot'
>>>> make[7]: *** [subdir-all-etherboot] Error 2
>>>> make[7]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>>> make[6]: *** [subdirs-all] Error 2
>>>> make[6]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>>> make[5]: *** [all] Error 2
>>>> make[5]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools/firmware'
>>>> make[4]: *** [subdir-all-firmware] Error 2
>>>> make[4]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools'
>>>> make[3]: *** [subdirs-all] Error 2
>>>> make[3]: Leaving directory
>>>> `/build/buildd/xen-4.1.1/debian/build/build-utils_amd64/tools'
>>>> make[2]: *** [debian/stamps/build-utils_amd64] Error 2
>>>> make[2]: Leaving directory `/build/buildd/xen-4.1.1'
>>>> make[1]: *** [build_amd64_real] Error 2
>>>> make[1]: Leaving directory `/build/buildd/xen-4.1.1'
>>>> make: *** [debian/stamps/build-base] Error 2
>>>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>>>>
>>>> Boris.
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx </mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx>
>>> http://lists.xensource.com/xen-devel
>>
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


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