[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Query regarding builnig Xen on Raspberry-Pi3


  • To: siddhartha v <siddhuvgowda.18695@xxxxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Thu, 14 May 2020 09:47:45 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iwjA033oVFDu/lnWuVfXkk08uWmO4fyWnkvnpcWvjn0=; b=fQ20hZNS0q/oZUCVbbx75YEyVQtTJeed747GV8s5c/3ETuUCdooeJU4GTXVocGerPuFuPO4fTSmGGObnC0VlO3xY69UiPlsWPrFPwAg4mLRzliQiT6wLW1bPSDXCzCAKZekE58QnZUcvL+7rb10X22b2FwVXZ9POwgZqOrU9t5regiMhtAypmxUOyUvD+BcrWtu6uLc5sQLjgl9Yuh8XxORpa/09wAkiq+5DZgnCZlxBYKG/zhj3TJHfoBv/On7znLcUDplUNqkrVoXnh/50r/6zajzT7mG1YXBfeH4bkunaK55sMRfl9xfd2OYLMOFELBkJq2aZAEiYesd+3PbA+g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AdpMdVg+26tzaIPTNb+u0C1LFRtdmV5s6jI320JdEWPmLJGCNmIPZEpsVwC7nWhFPbNJb3/qXrnQlGg5Phz/BRwGwOyDUDoXfjRAlXmLKEO5vnqgiMKrt2CERT84LbcSyw19LWnslBu0PUR4Lt7M1Wu94x9FrUfnTRkBUnR9NgLD/FD+IhrMh0yayZpeP9yUUs9IE2u0HjfFQdWfEUxDKYI++1FUv0U9prvfQFnCCGRmQosRxv9gviNCF9TWGlcrlXTXMkGNTePB1Um3uN8ZOVqFZ50IzbAHc6vhfOw6bUvHpid5cLn1H6Ty2zCI610an/uHnPYXhs302rc3li4IeQ==
  • Authentication-results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; lists.xenproject.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;lists.xenproject.org; dmarc=bestguesspass action=none header.from=arm.com;
  • Authentication-results-original: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=arm.com;
  • Cc: nd <nd@xxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 14 May 2020 09:48:18 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHWKb9ZHLxMR4/HfU+5kZ7ecO0Q+6inK5OAgAAIxwCAABr1gIAAAS+AgAAERoCAAABRgIAAANsA
  • Thread-topic: Query regarding builnig Xen on Raspberry-Pi3


> On 14 May 2020, at 10:44, Bertrand Marquis <bertrand.marquis@xxxxxxx> wrote:
> 
> 
> 
>> On 14 May 2020, at 10:43, siddhartha v <siddhuvgowda.18695@xxxxxxxxx> wrote:
>> 
>> ok sir,
>> 
>> For building should I use "bitbake xen-image-minimal" command?
> 
> Please use:
> bitbake xen-image-minimal.bb

Sorry remove .bb

Bertrand

> 
>> 
>> On Thu, May 14, 2020 at 2:58 PM Bertrand Marquis <Bertrand.Marquis@xxxxxxx> 
>> wrote:
>> Hi,
>> 
>>> On 14 May 2020, at 10:24, siddhartha v <siddhuvgowda.18695@xxxxxxxxx> wrote:
>>> 
>>> Hi sir, 
>>>  I tried to build by adding the line that you suggested but I got below 
>>> error:
>>> 
>>> siddhu@siddhu:~/Documents/yocto/build$ bitbake core-image-base
>>> ERROR: Unable to start bitbake server (None)
>>> ERROR: Server log for this session 
>>> (/home/siddhu/Documents/yocto/build/bitbake-cookerdaemon.log):
>>> --- Starting bitbake server pid 26317 at 2020-05-14 14:52:35.773040 ---
>>> ERROR: ParseError at /home/siddhu/Documents/yocto/build/conf/local.conf:43: 
>>> unparsed line: 'DISTRO_FEATURES += “virtualization xen”'
>>> siddhu@siddhu:~/Documents/yocto/build$ 
>>> 
>> 
>> You must have some wrong comas in the line.
>> Please try to rewrite it.
>> 
>> Bertrand
>> 
>>> 
>>> 
>>> On Thu, May 14, 2020 at 1:17 PM Bertrand Marquis <Bertrand.Marquis@xxxxxxx> 
>>> wrote:
>>> 
>>>> On 14 May 2020, at 08:16, siddhartha v <siddhuvgowda.18695@xxxxxxxxx> 
>>>> wrote:
>>>> 
>>>> Hello,
>>>> 
>>>>       I am trying to build the Xen to my Raspberry pi3 board. Below is the 
>>>> details,
>>>> BBlayers.conf file:
>>>> 
>>>> # POKY_BBLAYERS_CONF_VERSION is increased each time 
>>>> build/conf/bblayers.conf
>>>> # changes incompatibly
>>>> POKY_BBLAYERS_CONF_VERSION = "2"
>>>> 
>>>> BBPATH = "${TOPDIR}"
>>>> BBFILES ?= ""
>>>> 
>>>> BBLAYERS ?= " \
>>>>  /home/siddhu/Documents/yocto/sources/poky/meta \
>>>>  /home/siddhu/Documents/yocto/sources/poky/meta-poky \
>>>>  /home/siddhu/Documents/yocto/sources/poky/meta-yocto-bsp \
>>>>  /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-oe \
>>>>  /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-multimedia \
>>>>  /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-python \
>>>>  /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-networking \
>>>>  /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-filesystems \
>>>>  /home/siddhu/Documents/yocto/sources/meta-cloud-services \
>>>>  /home/siddhu/Documents/yocto/sources/meta-selinux \
>>>>  /home/siddhu/Documents/yocto/sources/meta-virtualization\
>>>>  /home/siddhu/Documents/yocto/sources/meta-raspberrypi \
>>>>  "
>>>> 
>>>> The build went well but after writing to SD card. I typed "$: xl info " 
>>>> but I got " xl not found" error. May I know what mistake I am doing here 
>>>> please.
>>>> 
>>>> 
>>>> I have attached the local.conf too where I have enabled the virtualisation 
>>>> after going through the readme of the meta-virtualisation.
>>> 
>>> To activate Xen build you need to add to your local.conf:
>>> 
>>> DISTRO_FEATURES += “virtualization xen”
>>> 
>>> You have something to add virtualization but not xen
>>> 
>>> Then you must start Xen which should start Linux, in your current system 
>>> you have more then probably just started the Linux generated but Xen needs 
>>> to be started first and then Xen is starting Linux.
>>> 
>>> Once you have done that, it would also help if you provide your boot logs.
>>> 
>>> Regards
>>> Bertrand
>>> 
>>>> -- 
>>>> Thanks and Regards.
>>>> Siddhartha V.
>>>> 
>>>> <local.conf>
>>> 
>>> 
>>> 
>>> -- 
>>> Thanks and Regards.
>>> Siddhartha V.
>>> 
>> 
>> 
>> 
>> -- 
>> Thanks and Regards.
>> Siddhartha V.
>> 
> 


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.