From: Jason Wu <jason.wu.misc@gmail.com>
To: Pello Heriz <pello.heriz@alumni.mondragon.edu>,
meta-xilinx@yoctoproject.org,
meta-xilinx-request@yoctoproject.org,
meta-virtualization@yoctoproject.org, yocto@yoctoproject.org
Subject: Re: [meta-xilinx] xen-image-minimal testing
Date: Tue, 2 May 2017 19:16:21 +1000 [thread overview]
Message-ID: <b383700f-54c5-7ff1-92a7-89916c413f1a@gmail.com> (raw)
In-Reply-To: <CAFL6qn5czUYrKRLPxhZbj7EEAgMu_dFr89WNsDBaYxVWKppM_w@mail.gmail.com>
On 2/05/2017 4:33 PM, Pello Heriz wrote:
> Hi all,
>
> I have built an image using "xen-image-minimal" command with Yocto and I
> would want to know how can I test if xen functionalities are correct or
> not with Zynq MPSoC QEMU. How can I do this?
http://www.wiki.xilinx.com/Building+the+Xen+Hypervisor+with+PetaLinux+2016.4+and+newer
have look at the "TFTP Booting Xen and Dom0 2016.4" section and hope
that helps.
>
> Anyway, I have seen that sometimes in the QEMU terminal appears the next
> message when the mentioned image is launched by "runqemu zcu102".
>
> INIT: Id "X0" respawning too fast: disabled for 5 minutes
>
> What's the meaning of the message? Is it critical?
It is not critical if you don't need it. The reason you are getting this
error message is because the your inittab trying spawn a console when
the device node (e.g. hvc0) for Id "X0" does not exists.
Jason
>
> Any answer will be welcome,
>
> Best regards,
> Pello
>
>
>
next prev parent reply other threads:[~2017-05-02 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:33 xen-image-minimal testing Pello Heriz
2017-05-02 9:16 ` Jason Wu [this message]
2017-05-02 16:04 ` [meta-xilinx] " Alistair Francis
2017-05-02 16:04 ` Alistair Francis
2017-05-02 16:47 ` Manjukumar Harthikote Matha
2017-05-02 17:23 ` Nathan Rossi
2017-05-02 17:23 ` Nathan Rossi
2017-05-02 18:28 ` Manjukumar Harthikote Matha
2017-05-02 19:48 ` Leonardo Sandoval
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=b383700f-54c5-7ff1-92a7-89916c413f1a@gmail.com \
--to=jason.wu.misc@gmail.com \
--cc=meta-virtualization@yoctoproject.org \
--cc=meta-xilinx-request@yoctoproject.org \
--cc=meta-xilinx@yoctoproject.org \
--cc=pello.heriz@alumni.mondragon.edu \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.