From: Luca Miccio <lucmiccio@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
andre.przywara@arm.com, Dario.faggioli@citrix.com,
Stefano Stabellini <Stefano@aporeto.com>,
xen-devel@lists.xenproject.org, nd@arm.com
Subject: Re: [GSoC] Xen on ARM: create multiple guests from device tree
Date: Thu, 23 Mar 2017 19:03:17 +0100 [thread overview]
Message-ID: <0095A93B-AC2C-4922-AD99-AA3F4277BAAD@gmail.com> (raw)
In-Reply-To: <8dfa724f-091d-9f06-51c9-64d233bdea04@arm.com>
Hello Julien
> Il giorno 23 mar 2017, alle ore 15:49, Julien Grall <julien.grall@arm.com> ha scritto:
>
> Hello Luca,
>
> On 23/03/17 02:23, Luca Miccio wrote:
>> I tried also this method but i had the same error. So i came up with the
>> idea of removing the
>> psci method from the configure and also from the dtsi file that i have
>> changed.
>
> I guess you are using only 1 core in this case. Am I right?
>
No, i am using 4 cores, with —cores option and i think that i am using actually 4 cores
because on the model “control panel” i have 4 green triangles which ones of them should
represent the number of cores and their status.
It is only my opinion so, please, tell me if i am wrong.
>>
>> With this configuration the model booted up correctly, even if the
>> process took about 10 minutes.
>> Just for my personal knowledge: it is normal that the boot is very slow?
>> Is the rootfs that i’m using?
>
> Booting a full distro on the model can be slow. Usually I write my own initscript to start the necessary daemon and skip systemd.
>
> 42sh> cat /root/init.sh
>
> set -x
> mount -t proc proc /proc
> mount -t devtmpfs dev /dev
>
> export HOME=/root
>
> rm -rf /var/run/xenstore
> rm -rf /var/run/xen
>
> /etc/init.d/xencommons start
>
> exec /bin/bash
>
> -------------------
>
> And I pass init=/root/init.sh on the Linux kernel command line.
>
That helped a lot, thank you.
> Cheers,
>
> --
> Julien Grall
Luca.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-23 18:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:09 [GSoC] Xen on ARM: create multiple guests from device tree Luca Miccio
2017-03-21 20:36 ` Stefano Stabellini
2017-03-22 19:45 ` Luca Miccio
2017-03-22 20:11 ` Julien Grall
2017-03-22 21:38 ` Stefano Stabellini
2017-03-23 0:01 ` Luca Miccio
2017-03-23 0:27 ` Stefano Stabellini
2017-03-23 0:32 ` Luca Miccio
2017-03-23 0:55 ` Stefano Stabellini
2017-03-23 2:23 ` Luca Miccio
2017-03-23 14:49 ` Julien Grall
2017-03-23 18:03 ` Luca Miccio [this message]
2017-03-28 17:30 ` Stefano Stabellini
2017-03-29 0:13 ` Stefano Stabellini
2017-03-30 18:14 ` Luca Miccio
2017-03-29 8:07 ` Julien Grall
2017-03-23 18:07 ` Stefano Stabellini
2017-03-23 14:42 ` Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2018-02-04 6:53 [GSOC] " Denis Obrezkov
2018-02-04 7:25 ` Denis Obrezkov
2018-02-05 17:53 ` Stefano Stabellini
2018-02-05 22:00 ` Denis Obrezkov
2018-02-07 0:08 ` Stefano Stabellini
2018-02-08 8:27 ` Denis Obrezkov
2018-02-08 16:26 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0095A93B-AC2C-4922-AD99-AA3F4277BAAD@gmail.com \
--to=lucmiccio@gmail.com \
--cc=Dario.faggioli@citrix.com \
--cc=Stefano@aporeto.com \
--cc=andre.przywara@arm.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).