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
>

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
>> >

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 !

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 !!

 

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 )

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.