Starting Xen guest on Raspberry-Pi4. #meta-virtualization #yocto


Siddhartha V
 

Hello @Christopher Sir,

         As you suggested I have created the Xen image for RPI4  Thank you so much. Later I did the below steps:

1. I used "sudo dd if=tmp/deploy/images/raspberrypi4-64/xen-image-minimal-raspberrypi4-64.rpi-sdimg of=/dev/sdb bs=4M" command to write theimage to the SDcard and then the RPI4 board booted well. And I used few commands ("Referred the pptx that shared during the yocto dev-day") and things went well. Thank you so much.

Now I am trying to start the guest now. But I am facing some issues:

I have built the guest image successfully.

Before going to issue, I have one question sir, What is my understanding is this:::  
   
  The two files 1. xen-guest-image-minimal-raspberrypi4-64.ext3 and 2. Image should be copied to the /home/root/ directory of the Dom-0. Here first I should copy them to the USB pendrive and then connecting that to the board I should copy them to the board later should create the .config file network related settings to be completed to run the guest.  Is my understanding correct sir?

Now below is the issue that I am facing:

1. I am trying to copy the "xen-guest-image-minimal-raspberrypi4-64.ext3" from "../build/tmp/work/raspberrypi4_64-poky-linux/xen-guest-image-minimal/1.0-r0/deploy-xen-guest-image-minimal-image-complete/" directory to the USB pendrive but getting "Filesystem does not support symbolic links" error.

2. Also next I am trying to copy the "Image" from the "../build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_4.19.126+gitAUTOINC+f6b3ac28f0-r0/deploy-linux-raspberrypi/ " directory. But here There is no actual image but I have a shortcut thing (as shown in the below screenshot). But another file I have "Image-1-4.19.126+git0+f6b3ac28f0-r0-raspberrypi4-64-20200624123806.bin" which  I can copy that (not sure if I am doing right).

Below is the screenshot for the image that I have in that directory. 





Kindly suggest me if I have missed anything or doing anything wrong. Please.


@Ashish sir, Please suggest me if you have any idea on this.
--
--
Best Regards,
Siddhartha V


Christopher Clark
 

On Mon, Jul 20, 2020 at 5:49 AM Siddhartha V
<Siddhuvgowda.18695@...> wrote:

Hello @Christopher Sir,

As you suggested I have created the Xen image for RPI4 Thank you so much. Later I did the below steps:

1. I used "sudo dd if=tmp/deploy/images/raspberrypi4-64/xen-image-minimal-raspberrypi4-64.rpi-sdimg of=/dev/sdb bs=4M" command to write theimage to the SDcard and then the RPI4 board booted well. And I used few commands ("Referred the pptx that shared during the yocto dev-day") and things went well. Thank you so much.
Excellent.

Now I am trying to start the guest now. But I am facing some issues:

I have built the guest image successfully.
That is good too.

Before going to issue, I have one question sir, What is my understanding is this:::

The two files 1. xen-guest-image-minimal-raspberrypi4-64.ext3 and 2. Image should be copied to the /home/root/ directory of the Dom-0. Here first I should copy them to the USB pendrive and then connecting that to the board I should copy them to the board later should create the .config file network related settings to be completed to run the guest. Is my understanding correct sir?
I'm not quite sure. You have two files from your guest image build,
and you should put a copy of each of those into the /home/root/
directory of your running Raspberry Pi.

It sounds like you're trying to use a USB pendrive to do that, which
may be OK. An alternative option could be to copy the ext3 and Image
files over a network, using a command line tool such as scp.

Now below is the issue that I am facing:

1. I am trying to copy the "xen-guest-image-minimal-raspberrypi4-64.ext3" from "../build/tmp/work/raspberrypi4_64-poky-linux/xen-guest-image-minimal/1.0-r0/deploy-xen-guest-image-minimal-image-complete/" directory to the USB pendrive but getting "Filesystem does not support symbolic links" error.
Instead of copying the symbolic link (or "shortcut thing"), inspect it
to find which file it is linking to, and copy that file instead.

You may need to rename it once it has been transferred into /home/root
on the Pi, so that it has the same filename as the link had, to match
the instructions in the presentation.

2. Also next I am trying to copy the "Image" from the "../build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_4.19.126+gitAUTOINC+f6b3ac28f0-r0/deploy-linux-raspberrypi/ " directory. But here There is no actual image but I have a shortcut thing (as shown in the below screenshot). But another file I have "Image-1-4.19.126+git0+f6b3ac28f0-r0-raspberrypi4-64-20200624123806.bin" which I can copy that (not sure if I am doing right).
Hmm. You seem to have built a 4.19 Linux kernel, which doesn't match
the expected version 5.4 Linux kernel that you should have, so I'm not
sure that you are building with all the correct pieces yet.

Christopher


Below is the screenshot for the image that I have in that directory.

Kindly suggest me if I have missed anything or doing anything wrong. Please.


@Ashish sir, Please suggest me if you have any idea on this.
--
--
Best Regards,
Siddhartha V


Siddhartha V
 

Yes sir it built using kernel 4.19.

How can i upgrade it to 5.4 now. Is there any ways? Please suggest ms sir. 


Regards, 
Siddhartha V 


On Wed, 22 Jul, 2020, 12:11 AM Christopher Clark, <christopher.w.clark@...> wrote:
On Mon, Jul 20, 2020 at 5:49 AM Siddhartha V
<Siddhuvgowda.18695@...> wrote:
>
> Hello @Christopher Sir,
>
>          As you suggested I have created the Xen image for RPI4  Thank you so much. Later I did the below steps:
>
> 1. I used "sudo dd if=tmp/deploy/images/raspberrypi4-64/xen-image-minimal-raspberrypi4-64.rpi-sdimg of=/dev/sdb bs=4M" command to write theimage to the SDcard and then the RPI4 board booted well. And I used few commands ("Referred the pptx that shared during the yocto dev-day") and things went well. Thank you so much.

Excellent.

> Now I am trying to start the guest now. But I am facing some issues:
>
> I have built the guest image successfully.

That is good too.

> Before going to issue, I have one question sir, What is my understanding is this:::
>
>   The two files 1. xen-guest-image-minimal-raspberrypi4-64.ext3 and 2. Image should be copied to the /home/root/ directory of the Dom-0. Here first I should copy them to the USB pendrive and then connecting that to the board I should copy them to the board later should create the .config file network related settings to be completed to run the guest.  Is my understanding correct sir?

I'm not quite sure. You have two files from your guest image build,
and you should put a copy of each of those into the /home/root/
directory of your running Raspberry Pi.

It sounds like you're trying to use a USB pendrive to do that, which
may be OK. An alternative option could be to copy the ext3 and Image
files over a network, using a command line tool such as scp.

> Now below is the issue that I am facing:
>
> 1. I am trying to copy the "xen-guest-image-minimal-raspberrypi4-64.ext3" from "../build/tmp/work/raspberrypi4_64-poky-linux/xen-guest-image-minimal/1.0-r0/deploy-xen-guest-image-minimal-image-complete/" directory to the USB pendrive but getting "Filesystem does not support symbolic links" error.

Instead of copying the symbolic link (or "shortcut thing"), inspect it
to find which file it is linking to, and copy that file instead.

You may need to rename it once it has been transferred into /home/root
on the Pi, so that it has the same filename as the link had, to match
the instructions in the presentation.

> 2. Also next I am trying to copy the "Image" from the "../build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_4.19.126+gitAUTOINC+f6b3ac28f0-r0/deploy-linux-raspberrypi/ " directory. But here There is no actual image but I have a shortcut thing (as shown in the below screenshot). But another file I have "Image-1-4.19.126+git0+f6b3ac28f0-r0-raspberrypi4-64-20200624123806.bin" which  I can copy that (not sure if I am doing right).

Hmm. You seem to have built a 4.19 Linux kernel, which doesn't match
the expected version 5.4 Linux kernel that you should have, so I'm not
sure that you are building with all the correct pieces yet.

Christopher

>
> Below is the screenshot for the image that I have in that directory.
>
> Kindly suggest me if I have missed anything or doing anything wrong. Please.
>
>
> @Ashish sir, Please suggest me if you have any idea on this.
> --
> --
> Best Regards,
> Siddhartha V
>

--
Best Regards,
Siddhartha V


Christopher Clark
 

On Tue, Jul 21, 2020 at 11:46 AM siddhartha v
<siddhuvgowda.18695@...> wrote:

Yes sir it built using kernel 4.19.

How can i upgrade it to 5.4 now. Is there any ways? Please suggest ms sir.
If you are building with the latest version of meta-virtualization and
'xen' is present in DISTRO_FEATURES in your local.conf file, then your
build configuration should automatically have set kernel version to
5.4 as the preferred version. You should just be able to build with
the current versions of the source code, and then use a SD card
populated with the new image and new binaries for your guest VM.

The Raspberry Pi kernel, linux-raspberrypi, is set as the preferred
kernel in meta-raspberrypi when you select the raspberrypi4-64 as
MACHINE in local.conf, by this:
./include/rpi-default-providers.inc:PREFERRED_PROVIDER_virtual/kernel
?= "linux-raspberrypi"

The preferred kernel version for that kernel is set by this line in
meta-virtualization/conf/distro/include/meta-virt-xen.inc :
PREFERRED_VERSION_linux-raspberrypi ?= "5.4.%"

and the meta-virt-xen.inc file gets included via meta-virtualization's
layer.conf:
META_VIRT_XEN_CONFIG_PATH = "${LAYERDIR}/conf/distro/include/meta-virt-xen.inc"
USER_CLASSES_append = " meta-virt-xen-cfg"

Have you overridden the USER_CLASSES variable, or
PREFERRED_PROVIDER_virtual/kernel or anything related to the above in
your build configuration files?

Christopher



Regards,
Siddhartha V


On Wed, 22 Jul, 2020, 12:11 AM Christopher Clark, <christopher.w.clark@...> wrote:

On Mon, Jul 20, 2020 at 5:49 AM Siddhartha V
<Siddhuvgowda.18695@...> wrote:

Hello @Christopher Sir,

As you suggested I have created the Xen image for RPI4 Thank you so much. Later I did the below steps:

1. I used "sudo dd if=tmp/deploy/images/raspberrypi4-64/xen-image-minimal-raspberrypi4-64.rpi-sdimg of=/dev/sdb bs=4M" command to write theimage to the SDcard and then the RPI4 board booted well. And I used few commands ("Referred the pptx that shared during the yocto dev-day") and things went well. Thank you so much.
Excellent.

Now I am trying to start the guest now. But I am facing some issues:

I have built the guest image successfully.
That is good too.

Before going to issue, I have one question sir, What is my understanding is this:::

The two files 1. xen-guest-image-minimal-raspberrypi4-64.ext3 and 2. Image should be copied to the /home/root/ directory of the Dom-0. Here first I should copy them to the USB pendrive and then connecting that to the board I should copy them to the board later should create the .config file network related settings to be completed to run the guest. Is my understanding correct sir?
I'm not quite sure. You have two files from your guest image build,
and you should put a copy of each of those into the /home/root/
directory of your running Raspberry Pi.

It sounds like you're trying to use a USB pendrive to do that, which
may be OK. An alternative option could be to copy the ext3 and Image
files over a network, using a command line tool such as scp.

Now below is the issue that I am facing:

1. I am trying to copy the "xen-guest-image-minimal-raspberrypi4-64.ext3" from "../build/tmp/work/raspberrypi4_64-poky-linux/xen-guest-image-minimal/1.0-r0/deploy-xen-guest-image-minimal-image-complete/" directory to the USB pendrive but getting "Filesystem does not support symbolic links" error.
Instead of copying the symbolic link (or "shortcut thing"), inspect it
to find which file it is linking to, and copy that file instead.

You may need to rename it once it has been transferred into /home/root
on the Pi, so that it has the same filename as the link had, to match
the instructions in the presentation.

2. Also next I am trying to copy the "Image" from the "../build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_4.19.126+gitAUTOINC+f6b3ac28f0-r0/deploy-linux-raspberrypi/ " directory. But here There is no actual image but I have a shortcut thing (as shown in the below screenshot). But another file I have "Image-1-4.19.126+git0+f6b3ac28f0-r0-raspberrypi4-64-20200624123806.bin" which I can copy that (not sure if I am doing right).
Hmm. You seem to have built a 4.19 Linux kernel, which doesn't match
the expected version 5.4 Linux kernel that you should have, so I'm not
sure that you are building with all the correct pieces yet.

Christopher


Below is the screenshot for the image that I have in that directory.

Kindly suggest me if I have missed anything or doing anything wrong. Please.


@Ashish sir, Please suggest me if you have any idea on this.
--
--
Best Regards,
Siddhartha V


Siddhartha V
 

Hi sir,

  Actually i built the image using the below repos which you suggested earlier :

git://git.yoctoproject.org/poky
  18b6b2ae819cbf0ef3858944b4cd02ab74df6607
git://git.openembedded.org/meta-openembedded
  463f9a3ef0935d772a0be0437a8c09df64ed2f07
git://git.yoctoproject.org/meta-raspberrypi
  e589e0f3fda8f15f1093909328605e0bb6516d94
https://github.com/dozylynx/meta-virtualization
  0c809ead05224a61a784744240bb9c125990c481

Shall I download the new latest version directly and build the image again now?

And I have below lines in the local.conf file:


MACHINE = "raspberrypi4-64"
DISTRO_FEATURES_append = " virtualization xen"
QEMU_TARGETS = "i386 x86_64 aarch64 arm"
PACKAGECONFIG_pn-qemu += " xen fdt"
PACKAGECONFIG_remove_pn-qemu += " sdl"
PREFERRED_VERSION_linux-raspberrypi = "4.19.%"
IMAGE_FSTYPES = "tar.xz tar.bz2 ext3 rpi-sdimg"


This was built almost 2/3 weeks before. Should I download the meta-virtualization now and build the new image now? Should I take any particular commit no. or can I download the recipes directly?

Please suggest me what can be done to build the latest version Image please.

Regards,
Siddhartha V 



On Wed, 22 Jul, 2020, 1:47 AM Christopher Clark, <christopher.w.clark@...> wrote:
On Tue, Jul 21, 2020 at 11:46 AM siddhartha v
<siddhuvgowda.18695@...> wrote:
>
> Yes sir it built using kernel 4.19.
>
> How can i upgrade it to 5.4 now. Is there any ways? Please suggest ms sir.

If you are building with the latest version of meta-virtualization and
'xen' is present in DISTRO_FEATURES in your local.conf file, then your
build configuration should automatically have set kernel version to
5.4 as the preferred version. You should just be able to build with
the current versions of the source code, and then use a SD card
populated with the new image and new binaries for your guest VM.

The Raspberry Pi kernel, linux-raspberrypi, is set as the preferred
kernel in meta-raspberrypi when you select the raspberrypi4-64 as
MACHINE in local.conf, by this:
./include/rpi-default-providers.inc:PREFERRED_PROVIDER_virtual/kernel
?= "linux-raspberrypi"

The preferred kernel version for that kernel is set by this line in
meta-virtualization/conf/distro/include/meta-virt-xen.inc :
PREFERRED_VERSION_linux-raspberrypi ?= "5.4.%"

and the meta-virt-xen.inc file gets included via meta-virtualization's
layer.conf:
META_VIRT_XEN_CONFIG_PATH = "${LAYERDIR}/conf/distro/include/meta-virt-xen.inc"
USER_CLASSES_append = " meta-virt-xen-cfg"

Have you overridden the USER_CLASSES variable, or
PREFERRED_PROVIDER_virtual/kernel or anything related to the above in
your build configuration files?

Christopher

>
>
> Regards,
> Siddhartha V
>
>
> On Wed, 22 Jul, 2020, 12:11 AM Christopher Clark, <christopher.w.clark@...> wrote:
>>
>> On Mon, Jul 20, 2020 at 5:49 AM Siddhartha V
>> <Siddhuvgowda.18695@...> wrote:
>> >
>> > Hello @Christopher Sir,
>> >
>> >          As you suggested I have created the Xen image for RPI4  Thank you so much. Later I did the below steps:
>> >
>> > 1. I used "sudo dd if=tmp/deploy/images/raspberrypi4-64/xen-image-minimal-raspberrypi4-64.rpi-sdimg of=/dev/sdb bs=4M" command to write theimage to the SDcard and then the RPI4 board booted well. And I used few commands ("Referred the pptx that shared during the yocto dev-day") and things went well. Thank you so much.
>>
>> Excellent.
>>
>> > Now I am trying to start the guest now. But I am facing some issues:
>> >
>> > I have built the guest image successfully.
>>
>> That is good too.
>>
>> > Before going to issue, I have one question sir, What is my understanding is this:::
>> >
>> >   The two files 1. xen-guest-image-minimal-raspberrypi4-64.ext3 and 2. Image should be copied to the /home/root/ directory of the Dom-0. Here first I should copy them to the USB pendrive and then connecting that to the board I should copy them to the board later should create the .config file network related settings to be completed to run the guest.  Is my understanding correct sir?
>>
>> I'm not quite sure. You have two files from your guest image build,
>> and you should put a copy of each of those into the /home/root/
>> directory of your running Raspberry Pi.
>>
>> It sounds like you're trying to use a USB pendrive to do that, which
>> may be OK. An alternative option could be to copy the ext3 and Image
>> files over a network, using a command line tool such as scp.
>>
>> > Now below is the issue that I am facing:
>> >
>> > 1. I am trying to copy the "xen-guest-image-minimal-raspberrypi4-64.ext3" from "../build/tmp/work/raspberrypi4_64-poky-linux/xen-guest-image-minimal/1.0-r0/deploy-xen-guest-image-minimal-image-complete/" directory to the USB pendrive but getting "Filesystem does not support symbolic links" error.
>>
>> Instead of copying the symbolic link (or "shortcut thing"), inspect it
>> to find which file it is linking to, and copy that file instead.
>>
>> You may need to rename it once it has been transferred into /home/root
>> on the Pi, so that it has the same filename as the link had, to match
>> the instructions in the presentation.
>>
>> > 2. Also next I am trying to copy the "Image" from the "../build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_4.19.126+gitAUTOINC+f6b3ac28f0-r0/deploy-linux-raspberrypi/ " directory. But here There is no actual image but I have a shortcut thing (as shown in the below screenshot). But another file I have "Image-1-4.19.126+git0+f6b3ac28f0-r0-raspberrypi4-64-20200624123806.bin" which  I can copy that (not sure if I am doing right).
>>
>> Hmm. You seem to have built a 4.19 Linux kernel, which doesn't match
>> the expected version 5.4 Linux kernel that you should have, so I'm not
>> sure that you are building with all the correct pieces yet.
>>
>> Christopher
>>
>> >
>> > Below is the screenshot for the image that I have in that directory.
>> >
>> > Kindly suggest me if I have missed anything or doing anything wrong. Please.
>> >
>> >
>> > @Ashish sir, Please suggest me if you have any idea on this.
>> > --
>> > --
>> > Best Regards,
>> > Siddhartha V
>> >


--
Best Regards,
Siddhartha V


Ashish <ashishm@...>
 

Hi Siddharth ,

1) With inputs from Christopher (@ https://lists.yoctoproject.org/g/meta-virtualization/message/5464 ) 
    we can generate an Xen image with kernel 5.4 following  :
      poky: 18b6b2ae819cbf0ef3858944b4cd02ab74df6607
meta-openembedded: 463f9a3ef0935d772a0be0437a8c09df64ed2f07
meta-raspberrypi: 5576a22061864bc451ec4fcacb7d830bf76b7ebd
meta-virtualization: d75bc448866d2b36779251efb1310d0234ece30b

2) On top of
meta-virtualization , apply the patches from series Patch[00/10] Xen on Raspberry Pi 4 series
You can extract these patches from Christopher's repo @ https://github.com/dozylynx/meta-virtualization

3) Configure your local.conf file for rpi-4 architecture
Example from mine :- 271 QEMU_TARGETS ="i386 x86_64 aarch64 arm" 272 DISTRO_FEATURES_append = " xen virtualization" 273 MACHINE = "raspberrypi4-64" 274 DL_DIR = "/home/ashish/Downloads/poky-tar-files"
4) Generate an image by 
              $ bitbake -k xen-image-minimal 

This should give you an working dom0 image 
Hope this helps !


Siddhartha V
 

Sure sir, Thank you



--
Thanks and Regards.
Siddhartha V.
 


On Wed, Jul 22, 2020 at 11:28 AM Ashish Mishra <ashishm@...> wrote:
Yes .
-  Also please keep the communication via group reply & on forum. 

- We should prefer group reply on forums compared to private communication.
   As that can help others in future. 
   ( i missed sending as group reply & accidentally sent only to you )

Thanks,
Ashish 





On Wed, Jul 22, 2020 at 11:04 AM siddhartha v <siddhuvgowda.18695@...> wrote:
Thank you sir.


File path is that you shared in last mail right naa sir. 

On Wed, 22 Jul, 2020, 10:34 AM Ashish Mishra, <ashishm@...> wrote:
Siddartha ,

1) cd to meta-virtualization 

2) git apply --check  <path-of-patch-file>
    This can help you to check if the patch is proper or there is some error.

3) If step-2 doesn't give an error try 
    git am <path-of-patch-file>

Thanks ,
Ashish 




On Wed, Jul 22, 2020 at 10:27 AM siddhartha v <siddhuvgowda.18695@...> wrote:
Thank tou ashish sir,

Ok i will sure follow your instructions. 

Also I am newbie and wrking on this linux, and all for the first time. don't know how to apply patches.

Can you please help me out how can I apply patches on meta-virtualization. 

kind request sir.

Regards, 
Siddhartha V 

On Wed, 22 Jul, 2020, 10:03 AM Ashish, <ashishm@...> wrote:
Hi Siddharth ,

1) With inputs from Christopher (@ https://lists.yoctoproject.org/g/meta-virtualization/message/5464 ) 
    we can generate an Xen image with kernel 5.4 following  :
      poky: 18b6b2ae819cbf0ef3858944b4cd02ab74df6607
meta-openembedded: 463f9a3ef0935d772a0be0437a8c09df64ed2f07
meta-raspberrypi: 5576a22061864bc451ec4fcacb7d830bf76b7ebd
meta-virtualization: d75bc448866d2b36779251efb1310d0234ece30b

2) On top of
meta-virtualization , apply the patches from series Patch[00/10] Xen on Raspberry Pi 4 series
You can extract these patches from Christopher's repo @ https://github.com/dozylynx/meta-virtualization

3) Configure your local.conf file for rpi-4 architecture
Example from mine :- 271 QEMU_TARGETS ="i386 x86_64 aarch64 arm" 272 DISTRO_FEATURES_append = " xen virtualization" 273 MACHINE = "raspberrypi4-64" 274 DL_DIR = "/home/ashish/Downloads/poky-tar-files"
4) Generate an image by 
              $ bitbake -k xen-image-minimal 

This should give you an working dom0 image 
Hope this helps !

--
Best Regards,
Siddhartha V


Siddhartha V
 
Edited

Hi sir,

 I tried to do some work on patch you suggested but sadly I didn't get how to download the  patches from the https://github.com/dozylynx/meta-virtualization      I tried a lot and also googled to get some knowledge but that also didn't help me. So I directly downloaded the raspberry-pi4-xen-series branch from https://github.com/dozylynx/meta-virtualization and tried to build the image. But I got stuck with below error :
####
ERROR: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/temp/log.do_fetch.3928
ERROR: Task (/home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3957 tasks of which 3949 didn't need to be rerun and 1 failed.
####
Below is the detailed log:


############Detailed Log###############
 
siddhu@siddhu:~/Documents/yocto/zindagi/build$ bitbake -k xen-image-minimal 
Loading cache: 100% |############################################| Time: 0:00:01
Loaded 3347 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:02
Parsing of 2270 .bb files complete (2269 cached, 1 parsed). 3348 targets, 147 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
 
Build Configuration:
BB_VERSION           = "1.44.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "raspberrypi4-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.0+snapshot-20200722"
TUNE_FEATURES        = "aarch64 cortexa72 crc crypto"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "local-rpi:18b6b2ae819cbf0ef3858944b4cd02ab74df6607"
meta-oe              
meta-networking      
meta-filesystems     
meta-python          
meta-perl            = "local-rpi:463f9a3ef0935d772a0be0437a8c09df64ed2f07"
meta-raspberrypi     = "local-rpi:e589e0f3fda8f15f1093909328605e0bb6516d94"
meta-virtualization-raspberry-pi4-xen-series = "<unknown>:<unknown>"
 
Initialising tasks: 100% |#######################################| Time: 0:00:04
Sstate summary: Wanted 39 Found 3 Missed 36 Current 1554 (7% match, 97% complete)
NOTE: Executing Tasks
 
NOTE: Task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_deploy_source_date_epoch unihash changed to 9b3b0c4c8d476222964814d569df4d59e06a0ac0d3cb4abe0303a982099a8c16
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_package became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_packagedata became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_populate_sysroot became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_package_qa became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_deploy became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_package_write_rpm became valid
NOTE: Task /home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb:do_deploy_source_date_epoch unihash changed to 54770a4ded5d4d2dc259fae6f2332be28f4aecac039c1017fd674e394232a6fe
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb:do_populate_sysroot became valid
NOTE: Setscene task /home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb:do_deploy became valid
NOTE: Task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/xen/xen-tools_git.bb:do_populate_lic unihash changed to 604c548ce45ed5d7741ef76d7453ce49359921b4c716d9b7295a8b6884b9e47e
NOTE: Task /home/siddhu/Documents/yocto/zindagi/sources/meta-virtualization-raspberry-pi4-xen-series/recipes-extended/images/xen-image-minimal.bb:do_deploy_source_date_epoch unihash changed to 35ac984fe0e0bb454791c4e70320015bd433949b6c0bc35761bd7b745359428d
NOTE: Task /home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-bsp/rpi-u-boot-scr/rpi-u-boot-scr.bb:do_populate_lic unihash changed to 933fb59a1811901b6756f733da986f69cdb626258cff5004b436566968ce7883
NOTE: Setscene tasks completed
WARNING: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Failed to fetch URL git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y, attempting MIRRORS if available
ERROR: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-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=fb644bd839a1d48731370a435f1822fc"; export SSH_AGENT_PID="1608"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/siddhu/Documents/yocto/zindagi/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/siddhu/Documents/yocto/zindagi/sources/poky/scripts:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot/usr/bin/crossscripts:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot-native/usr/sbin:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot-native/usr/bin:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot-native/sbin:/home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/recipe-sysroot-native/bin:/home/siddhu/Documents/yocto/zindagi/sources/poky/bitbake/bin:/home/siddhu/Documents/yocto/zindagi/build/tmp/hosttools"; export HOME="/home/siddhu"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/raspberrypi/linux.git /home/siddhu/Documents/yocto/zindagi/build/downloads/git2/github.com.raspberrypi.linux.git --progress failed with exit code 128, output:
Cloning into bare repository '/home/siddhu/Documents/yocto/zindagi/build/downloads/git2/github.com.raspberrypi.linux.git'...
remote: Enumerating objects: 8449639, done.        
fatal: read error: Connection reset by peer768.82 MiB | 191.00 KiB/s   
fatal: early EOF
fatal: index-pack failed
 
ERROR: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/temp/log.do_fetch.3928
ERROR: Task (/home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3957 tasks of which 3949 didn't need to be rerun and 1 failed.
 
Summary: 1 task failed:
  /home/siddhu/Documents/yocto/zindagi/sources/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch
siddhu@siddhu:~/Documents/yocto/zindagi/build$ 
 
###############################


The other layers I was using along with the aspberry-pi4-xen-series branch from https://github.com/dozylynx/meta-virtualization  are as below:

git://git.yoctoproject.org/poky
  18b6b2ae819cbf0ef3858944b4cd02ab74df6607
git://git.openembedded.org/meta-openembedded
  463f9a3ef0935d772a0be0437a8c09df64ed2f07
git://git.yoctoproject.org/meta-raspberrypi
  e589e0f3fda8f15f1093909328605e0bb6516d94

Even earlier when I started this work, I got this error but later when Christopher sir suggested the commit no's this got resolved.I think now also I am missing some important points.



 Later I read the https://lists.yoctoproject.org/g/meta-virtualization/message/5464    there Christopher sir told we should checkout the meta-raspberrypi: 5576a22061864bc451ec4fcacb7d830bf76b7ebd and meta-virtualization: d75bc448866d2b36779251efb1310d0234ece30b, plus this patch series applied on top, or clone the raspberry-pi4-xen-series branch from his repository.

As I didn't know how to download the patches, I cloned the above through below commands:

1. git clone git://git.yoctoproject.org/meta-raspberrypi
cd meta-raspberrypi
git checkout 5576a22061864bc451ec4fcacb7d830bf76b7ebd

2.git clone https://github.com/dozylynx/meta-virtualization  -b  raspberry-pi4-xen-series

And I have below lines in my local.conf:

MACHINE = "raspberrypi4-64"
DISTRO_FEATURES_append = " xen virtualization"
QEMU_TARGETS = "i386 x86_64 aarch64 arm"
PACKAGECONFIG_pn-qemu += " xen fdt"
PACKAGECONFIG_remove_pn-qemu += " sdl"
IMAGE_FSTYPES = "tar.xz tar.bz2 ext3 rpi-sdimg"

Is this ok sir? I have not built yet but before I start building I wanted to know If I am on right path. Why I doubt here is I am didn't get the proper grip on yocto yet.

Can I build the image by " $ bitbake -k xen-image-minimal " ?


--
Best Regards,
Siddhartha V


Ashish <ashishm@...>
 

Hi Siddhartha , 

Let us help you by :

1)  You can create an patch by " git format-patch -1 " .
      This will create patch of current HEAD

2)  You can get Christopher patches by below two ways :
       a) Clone meta-virtualization 
               - Checkout the commit ( d75bc448866d2b36779251efb1310d0234ece30b ) shared by Chris in his input to us. 
               -  Apply the required patches  ( sharing an tar of patches just so that you can proceed ahead ) 
                  Attached along is the tar with patches  patch-folder-siddharth.tar
               - Patches can be applied by :  
                      $ git apply --check <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>
                      $ git am <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>    ( if apply --check doesn't generates an error ) 
         
      b) Clone his personal repo and switch to branch 
           $ git clone https://github.com/dozylynx/meta-virtualization 
           $ git checkout raspberry-pi4-xen-series

3)  Add below in your conf/local.conf
     QEMU_TARGETS ="i386 x86_64 aarch64 arm" 
     DISTRO_FEATURES_append = " xen virtualization" 
     MACHINE = "raspberrypi4-64" 
 
4)  Also as a suggestion start with clean repo.
     - Generally i share the error as log attachment & keep only error message on mail. 
       This makes going through the thread simpler . 
       Again this is not some hard rule but sharing my experience . 

5)  w.r.t grip on Yocto , we all keep on learning as Yocto has a steep learning curve but its worth all the effort for such a great tool .
 
We as an community need to be thankful to Christopher for his effort !!

Hope it helps !!

 


Siddhartha V
 

Thank you so much sir.


Yes sir really we should be verymuch thankful Christopher sir.

Thank you sir. 

On Wed, 22 Jul, 2020, 8:37 PM Ashish, <ashishm@...> wrote:
Hi Siddhartha , 

Let us help you by :

1)  You can create an patch by " git format-patch -1 " .
      This will create patch of current HEAD

2)  You can get Christopher patches by below two ways :
       a) Clone meta-virtualization 
               - Checkout the commit ( d75bc448866d2b36779251efb1310d0234ece30b ) shared by Chris in his input to us. 
               -  Apply the required patches  ( sharing an tar of patches just so that you can proceed ahead ) 
                  Attached along is the tar with patches  patch-folder-siddharth.tar
               - Patches can be applied by :  
                      $ git apply --check <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>
                      $ git am <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>    ( if apply --check doesn't generates an error ) 
         
      b) Clone his personal repo and switch to branch 
           $ git clone https://github.com/dozylynx/meta-virtualization 
           $ git checkout raspberry-pi4-xen-series

3)  Add below in your conf/local.conf
     QEMU_TARGETS ="i386 x86_64 aarch64 arm" 
     DISTRO_FEATURES_append = " xen virtualization" 
     MACHINE = "raspberrypi4-64" 
 
4)  Also as a suggestion start with clean repo.
     - Generally i share the error as log attachment & keep only error message on mail. 
       This makes going through the thread simpler . 
       Again this is not some hard rule but sharing my experience . 

5)  w.r.t grip on Yocto , we all keep on learning as Yocto has a steep learning curve but its worth all the effort for such a great tool .
 
We as an community need to be thankful to Christopher for his effort !!

Hope it helps !!

 


--
Best Regards,
Siddhartha V


Siddhartha V
 

Hello Ashish sir and Christopher sir,


I cloned the raspberry-pi4-xen-series branch and tried to build the xen image with below two diff recipes commits of meta-raspberrypi layer:

1. meta-raspberrypi     = "local-rpi:5576a22061864bc451ec4fcacb7d830bf76b7ebd"  With inputs from Christopher sir (@ https://lists.yoctoproject.org/g/meta-virtualization/message/5464 )

and 

2. meta-raspberrypi     = "local-rpi:e589e0f3fda8f15f1093909328605e0bb6516d94" suggested long back ( https://lists.yoctoproject.org/g/meta-virtualization/message/5393)


But in both the build I am getting " Failed do_fetch" error for linux-raspberrypi-5.4 kernel.

##########error########
ERROR: linux-raspberrypi-1_5.4.47+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.47+gitAUTOINC+aafb8f095e_machine-r0/temp/log.do_fetch.3251
ERROR: Task (/home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4100 tasks of which 3941 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch
Summary: There were 2 WARNING messages shown.
######################

One more difference that I observed here is:

1. When I use meta-raspberrypi = "local-rpi:5576a22061864bc451ec4fcacb7d830bf76b7ebd"  the kernel fetching is : " linux-raspberrypi-1_5.4.47+gitAUTOINC+aafb8f095e_machine" {log.do_fetch3251}

2. And when I use "meta-raspberrypi     = "local-rpi:e589e0f3fda8f15f1093909328605e0bb6516d94""  the kernel fetching is "linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0". {log.do_fetch.8692}

I didn't get why this change occurring actually.

I am attaching do-fetch_log for both.kindly suggest me if I am doing anything wrong. Please.


--
Thanks and Regards.
Siddhartha V.


On Thu, Jul 23, 2020 at 11:29 AM Siddhartha V via lists.yoctoproject.org <Siddhuvgowda.18695=gmail.com@...> wrote:


hello Ashish sir and Christopher sir,


I cloned the raspberry-pi4-xen-series branch and tried to build the xen image with below two diff recipes commits of meta-raspberrypi layer:

1. meta-raspberrypi     = "local-rpi:5576a22061864bc451ec4fcacb7d830bf76b7ebd"  With inputs from Christopher sir (@ https://lists.yoctoproject.org/g/meta-virtualization/message/5464 )

and 

2. meta-raspberrypi     = "local-rpi:e589e0f3fda8f15f1093909328605e0bb6516d94" suggested long back ( https://lists.yoctoproject.org/g/meta-virtualization/message/5393)


But in both the build I am getting " Failed do_fetch" error for linux-raspberrypi-5.4 kernel.

##########error########
ERROR: linux-raspberrypi-1_5.4.47+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.47+gitAUTOINC+aafb8f095e_machine-r0/temp/log.do_fetch.3251
ERROR: Task (/home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4100 tasks of which 3941 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch
Summary: There were 2 WARNING messages shown.
######################

One more difference that I observed here is:

1. When I use meta-raspberrypi = "local-rpi:5576a22061864bc451ec4fcacb7d830bf76b7ebd"  the kernel fetching is : " linux-raspberrypi-1_5.4.47+gitAUTOINC+aafb8f095e_machine" {log.do_fetch3251}

2. And when I use "meta-raspberrypi     = "local-rpi:e589e0f3fda8f15f1093909328605e0bb6516d94""  the kernel fetching is "linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0". {log.do_fetch.8692}

I didn't get why this change occurring actually.

I am attaching do-fetch_log for both.kindly suggest me if I am doing anything wrong. Please.


--
Thanks and Regards.
Siddhartha V.
 


On Wed, Jul 22, 2020 at 8:37 PM Ashish <ashishm@...> wrote:
Hi Siddhartha , 

Let us help you by :

1)  You can create an patch by " git format-patch -1 " .
      This will create patch of current HEAD

2)  You can get Christopher patches by below two ways :
       a) Clone meta-virtualization 
               - Checkout the commit ( d75bc448866d2b36779251efb1310d0234ece30b ) shared by Chris in his input to us. 
               -  Apply the required patches  ( sharing an tar of patches just so that you can proceed ahead ) 
                  Attached along is the tar with patches  patch-folder-siddharth.tar
               - Patches can be applied by :  
                      $ git apply --check <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>
                      $ git am <patch-folder/0001-libvirt-fix-patch-fuzz-warning.patch>    ( if apply --check doesn't generates an error ) 
         
      b) Clone his personal repo and switch to branch 
           $ git clone https://github.com/dozylynx/meta-virtualization 
           $ git checkout raspberry-pi4-xen-series

3)  Add below in your conf/local.conf
     QEMU_TARGETS ="i386 x86_64 aarch64 arm" 
     DISTRO_FEATURES_append = " xen virtualization" 
     MACHINE = "raspberrypi4-64" 
 
4)  Also as a suggestion start with clean repo.
     - Generally i share the error as log attachment & keep only error message on mail. 
       This makes going through the thread simpler . 
       Again this is not some hard rule but sharing my experience . 

5)  w.r.t grip on Yocto , we all keep on learning as Yocto has a steep learning curve but its worth all the effort for such a great tool .
 
We as an community need to be thankful to Christopher for his effort !!

Hope it helps !!

 


--
Best Regards,
Siddhartha V

--
Best Regards,
Siddhartha V

--
Best Regards,
Siddhartha V


Ashish <ashishm@...>
 

Based on my understanding , it seems problem with your network
( fatal: read error: Connection reset by peer )

Can you try just fetching all the prerequisites first :
    $ bitbake -c cleanall linux-raspberrypi
    $ bitbake -c fetch linux-raspberrypi            ( Fetch only Linux )
                  or 
    $ bitbake -c fetchall xen-image-minimal    ( Fetch all packages for concerned image )



Siddhartha V
 

Hello sir,

  As you suggested I tried "bitbake -c fetchall xen-image-minimal " but it was not able to run I got below error:

ERROR: Task do_fetchall does not exist for target xen-image-minimal (/home/siddhu/Documents/yocto/zindagi/sources1/meta-virtualization/recipes-extended/images/xen-image-minimal.bb:do_fetchall). Close matches:
  do_fetch
ERROR: Command execution failed:
1

Later I tried "bitbake -c fetch linux-raspberrypi" to check if I can fetch the linux alone but even here I couldn't It doesn't look like the network issue. But am not getting what's going wrong here:

Below is the error log for "bitbake -c fetch linux-raspberrypi" command:


WARNING: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Failed to fetch URL git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y, attempting MIRRORS if available
ERROR: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure: Unable to find revision 97badb4baeb8999263a9bc2fa85c3060ffff344b in branch rpi-5.4.y even from upstream
ERROR: linux-raspberrypi-1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0 do_fetch: Fetcher failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/zindagi/build/tmp/work/raspberrypi4_64-poky-linux/linux-raspberrypi/1_5.4.40+gitAUTOINC+aafb8f095e_machine-r0/temp/log.do_fetch.3919
ERROR: Task (/home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/siddhu/Documents/yocto/zindagi/sources1/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_5.4.bb:do_fetch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
siddhu@siddhu:~/Documents/yocto/zindagi/build$

What can I do now?

--
Thanks and Regards.
Siddhartha V.
 


On Thu, Jul 23, 2020 at 5:27 PM Ashish <ashishm@...> wrote:
Based on my understanding , it seems problem with your network
( fatal: read error: Connection reset by peer )

Can you try just fetching all the prerequisites first :
    $ bitbake -c cleanall linux-raspberrypi
    $ bitbake -c fetch linux-raspberrypi            ( Fetch only Linux )
                  or 
    $ bitbake -c fetchall xen-image-minimal    ( Fetch all packages for concerned image )




--
Best Regards,
Siddhartha V


Ashishx88 <ashish.emailaddress@...>
 

For an quick check , can you try to build at "dunfell" branch for all the layer
 ( poky / meta-openembedded / met-rasberrypie & meta-virtualization )

@dunfell expectation is it should be able to fetch kernel
as the rpi4 patches doesn't come into picture.





Siddhartha V
 

Sure sir I will try and check that. 
Thank you
--
Thanks and Regards.
Siddhartha V.
 


On Fri, Jul 24, 2020 at 5:13 PM AshishKumar Mishra <ashish.emailaddress@...> wrote:
For an quick check , can you try to build at "dunfell" branch for all the layer
 ( poky / meta-openembedded / met-rasberrypie & meta-virtualization )

@dunfell expectation is it should be able to fetch kernel
as the rpi4 patches doesn't come into picture.





--
Best Regards,
Siddhartha V