Hello really sorry for late response,
Currently I am working with the warrior series of yocto but the
meta-raspberrypi-xen is in th edunfell series of the yocto. So my doubt is
should I do the building task from the beginning? From the past two days
yocto documentation and any website yocto is not loading ( I am getting
this error* "This site can’t be reached. The connection was reset."*). So I
am not able to access the documentation.
Also, as I am having a very short time period, I tried to build the
image using dunfell from the beginning but I am getting the below error,
ERROR: Task
(/home/siddhu/Documents/yocto/dunfell/sources/poky/meta/recipes-devtools/binutils/binutils-cross_2.34.bb:do_compile)
failed with exit code '1'
WARNING: linux-raspberrypi-1_4.19.120+gitAUTOINC+9da67d7329-r0
do_fetch: Failed to fetch URL
git://github.com/raspberrypi/linux.git;branch=rpi-4.19.y, attempting
MIRRORS if available
ERROR: linux-raspberrypi-1_4.19.120+gitAUTOINC+9da67d7329-r0 do_fetch:
Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset
_PYTHON_SYSCONFIGDATA_NAME; export
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus,guid=5716e12867bf0fe2966f5f465ee359ba";
export SSH_AGENT_PID="1911"; export
SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export
PATH="/home/siddhu/Documents/yocto/dunfell/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/siddhu/Documents/yocto/dunfell/sources/poky/scripts:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot/usr/bin/crossscripts:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot-native/usr/sbin:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot-native/usr/bin:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot-native/sbin:/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/recipe-sysroot-native/bin:/home/siddhu/Documents/yocto/dunfell/sources/poky/bitbake/bin:/home/siddhu/Documents/yocto/dunfell/build/tmp/hosttools";
export HOME="/home/siddhu"; LANG=C git -c core.fsyncobjectfiles=0
fetch -f --prune --progress git://github.com/raspberrypi/linux.git
refs/*:refs/* failed with exit code 128, output:
remote: Enumerating objects: 12, done.
remote: Counting objects: 100% (12/12), done.
remote: Compressing objects: 100% (11/11), done.
fatal: read error: Connection reset by peer1.29 GiB | 340.00 KiB/s
fatal: early EOF
fatal: index-pack failed
ERROR: linux-raspberrypi-1_4.19.120+gitAUTOINC+9da67d7329-r0 do_fetch:
Fetcher failure for URL:
'git://github.com/raspberrypi/linux.git;branch=rpi-4.19.y'. Unable to
fetch URL from any source.
ERROR: Logfile of failure stored in:
/home/siddhu/Documents/yocto/dunfell/build/tmp/work/raspberrypi4-poky-linux-gnueabi/linux-raspberrypi/1_4.19.120+gitAUTOINC+9da67d7329-r0/temp/log.do_fetch.2431
ERROR: Task
(/home/siddhu/Documents/yocto/dunfell/sources/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.19.bb:do_fetch)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1058 tasks of which 1053 didn't need to
be rerun and 4 failed.
Summary: 4 tasks failed:
virtual:native:/home/siddhu/Documents/yocto/dunfell/sources/poky/meta/recipes-support/icu/icu_66.1.bb:do_compile
#/home/siddhu/Documents/yocto/dunfell/sources/poky/meta/recipes-support/icu/icu_66.1.bb:do_make_icudata
/home/siddhu/Documents/yocto/dunfell/sources/poky/meta/recipes-devtools/binutils/binutils-cross_2.34.bb:do_compile
/home/siddhu/Documents/yocto/dunfell/sources/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.19.bb:do_fetch
May I know what wrong I am doing here, Even when I started this yocto for
the first time I faced the same but luckily it was resolved automatically
after trying multiple times. But I need some suggestions here. Kindly
suggest me what wrong I am doing here.
--
Thanks and Regards.
Siddhartha V.
On Sat, Jun 6, 2020 at 6:28 AM Corey Minyard <[email protected]> wrote:
> On Fri, Jun 05, 2020 at 07:53:53PM -0400, Bruce Ashfield wrote:
> > On Fri, Jun 5, 2020 at 5:16 PM Corey Minyard <[email protected]>
> wrote:
> > >
> > > On Fri, Jun 05, 2020 at 07:55:37PM +0000, Stewart Hildebrand wrote:
> > > > + Corey
> > > >
> > > > On Friday, June 5, 2020 3:19 PM, Bruce Ashfield wrote:
> > > > >On Fri, Jun 5, 2020 at 3:12 PM Stewart Hildebrand wrote:
> > > > >> On Thursday, June 4, 2020 5:13 PM, Christopher Clark wrote:
> > > > >> > Hello Siddhartha,
> > > > >> >
> > > > >> > I am also interested in running Xen on the Raspberry Pi 4. I
> hope to have time next week to be able to look into it.
> > > > >> >
> > > > >> > Christopher
> > > > >> >
> > > > >> >
> > > > >> >> On Jun 4, 2020, at 5:05 AM, Siddhartha V wrote:
> > > > >> >>
> > > > >> >> Hello dear meta-virtualization team,
> > > > >> >> I am building the xen minimal image using yocto warrior
> ("bitbake xen-image-minimal") by giving the target machine as
> > > > >"raspberrypi4".
> > > > >>
> > > > >> Corey Minyard created a layer for Xen on Raspberry Pi 4 here
> https://github.com/MontaVista-OpenSourceTechnology/meta-
> > > > >raspberrypi-xen
> > > > >>
> > > > >
> > > > >Someone needs to lean on them to get patches submitted to meta-virt.
> > > >
> > > > Corey: you are hereby encouraged to submit patches to
> meta-virtualization.
> > >
> > > Ok. The layer has the following basic pieces:
> > >
> > > 1 The xen patches for the Pi4, just a few patches. As the Xen group
> > > fixes things, I keep adding :).
> > > 2 Hacks for getting the Pi4 kernel config right for xen. This should
> go
> > > away if you don't use the kernel from the Pi4 yocto layer, as it
> > > doesn't work like most kernels in yocto.
> >
> > I should take a look at the configs and see if I can create a fragment
> > or two, but I can take care of that.
>
> That shouldn't be necessary. The standard fragments work, it's just
> that the Pi kernel does not use them. So this is really Pi+Xen
> specific, and hopefully they can fix the Pi kernel to use the normal
> fragments in the future.
>
> >
> > > 3 The addition of xen-tools. This seems somewhat controversial from a
> > > naming point of view, at least. But all the major distros seem to
> > > have it, and it does make things easier. It brings along a boatload
> > > of perl recipes.
> > > 4 Something to make bridges easier to manage. Distros have another
> tool
> > > to do this (bridge-utils), but that ties into systemd/initd and would
> > > have been rather complex to integrate into yocto. Plus it requires
> > > rebooting to change anything. The one I created is far simpler and
> > > works just as well, maybe better.
> > > 5 A few Pi-specific hacks for config and u-boot.
> > >
> > > 1 is a no brainer, and 2 shouldn't matter in the future. I guess the
> > > questionable ones are 3 and 4.
> >
> > Christopher might have a better idea about #3, but if the
> > functionality is useful, I'm all for having it close to the other Xen
> > components.
> >
> > We've put similar things like #4 into the layer before. Witness
> > cgroups-lite and some of the other semi-custom and more lightweight
> > things. But yah, just a judgement call if they may or may not be
> > useful in other scenarios.
>
> I would like to see it go in, as I couldn't find anything to do this,
> and it's really simple.
>
> >
> > #5 does sound like BSP stuff. Is any of it destined for the rpi layers
> > ? Or is it both rpi AND xen specific, so doesn't really make sense
> > there either ?
>
> It's both Pi and Xen specific. If everything gets put where it should
> be, that would be the only thing left in this layer :).
>
> -corey
>
> >
> > Thanks for the info, most appreciated.
> >
> > Bruce
> >
> > >
> > > -corey
> > >
> > > >
> > > > >Having a layer like that, with fixes missing from meta-virt, makes
> no sense.
> > > > >
> > > > >Bruce
> > > >
> > > > meta-virtualization seems to be using Xen 4.12 at the moment.
> > > >
> > > > Corey's meta-raspberrypi-xen layer uses Xen 4.13. The Xen patches
> are based on Xen 4.13. Between Xen 4.12 and 4.13 there are a few additional
> patches that are required for running on Raspberry Pi 4.
> > > >
> > > > Would you rather uprev meta-virtualization to Xen 4.13, or backport
> the patches and identify additional backports required for running Xen 4.12
> on Raspberry Pi 4?
> > > >
> > > > Stew
> >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5403):
https://lists.yoctoproject.org/g/meta-virtualization/message/5403
Mute This Topic: https://lists.yoctoproject.org/mt/74701134/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
