* xen-image-minimal testing @ 2017-05-02 6:33 Pello Heriz 2017-05-02 9:16 ` [meta-xilinx] " Jason Wu 0 siblings, 1 reply; 9+ messages in thread From: Pello Heriz @ 2017-05-02 6:33 UTC (permalink / raw) To: meta-xilinx, meta-xilinx-request, meta-virtualization, yocto [-- Attachment #1: Type: text/plain, Size: 517 bytes --] 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? 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? Any answer will be welcome, Best regards, Pello [-- Attachment #2: Type: text/html, Size: 736 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 6:33 xen-image-minimal testing Pello Heriz @ 2017-05-02 9:16 ` Jason Wu 2017-05-02 16:04 ` Alistair Francis 2017-05-02 16:47 ` Manjukumar Harthikote Matha 0 siblings, 2 replies; 9+ messages in thread From: Jason Wu @ 2017-05-02 9:16 UTC (permalink / raw) To: Pello Heriz, meta-xilinx, meta-xilinx-request, meta-virtualization, yocto 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 > > > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 9:16 ` [meta-xilinx] " Jason Wu @ 2017-05-02 16:04 ` Alistair Francis 2017-05-02 16:47 ` Manjukumar Harthikote Matha 1 sibling, 0 replies; 9+ messages in thread From: Alistair Francis @ 2017-05-02 16:04 UTC (permalink / raw) To: Jason Wu Cc: meta-xilinx-request, yocto, meta-virtualization, meta-xilinx, Pello Heriz On Tue, May 2, 2017 at 2:16 AM, Jason Wu <jason.wu.misc@gmail.com> wrote: > > > 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. You can also look at this, it is a little out of date though. http://www.wiki.xilinx.com/Xen+Hypervisor+through+Yocto+Flow Thanks, Alistair > >> >> 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 >> >> >> > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing @ 2017-05-02 16:04 ` Alistair Francis 0 siblings, 0 replies; 9+ messages in thread From: Alistair Francis @ 2017-05-02 16:04 UTC (permalink / raw) To: Jason Wu; +Cc: meta-xilinx-request, yocto, meta-virtualization, meta-xilinx On Tue, May 2, 2017 at 2:16 AM, Jason Wu <jason.wu.misc@gmail.com> wrote: > > > 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. You can also look at this, it is a little out of date though. http://www.wiki.xilinx.com/Xen+Hypervisor+through+Yocto+Flow Thanks, Alistair > >> >> 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 >> >> >> > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 9:16 ` [meta-xilinx] " Jason Wu 2017-05-02 16:04 ` Alistair Francis @ 2017-05-02 16:47 ` Manjukumar Harthikote Matha 2017-05-02 17:23 ` Nathan Rossi 1 sibling, 1 reply; 9+ messages in thread From: Manjukumar Harthikote Matha @ 2017-05-02 16:47 UTC (permalink / raw) To: Jason Wu, Pello Heriz, meta-xilinx, meta-xilinx-request, meta-virtualization, yocto > -----Original Message----- > From: meta-xilinx-bounces@yoctoproject.org [mailto:meta-xilinx- > bounces@yoctoproject.org] On Behalf Of Jason Wu > Sent: Tuesday, May 02, 2017 2:16 AM > 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 > > > > 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. > Is there a way to stop inittab from doing this? Tried few options for initiab, for ex: using "once" instead of "spawn" Any other good ideas on how we can disable it? Or what is a better approach to resolve this issue during runtime Thanks Manju > Jason > > > > Any answer will be welcome, > > > > Best regards, > > Pello > > > > > > > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 16:47 ` Manjukumar Harthikote Matha @ 2017-05-02 17:23 ` Nathan Rossi 0 siblings, 0 replies; 9+ messages in thread From: Nathan Rossi @ 2017-05-02 17:23 UTC (permalink / raw) To: Manjukumar Harthikote Matha Cc: meta-virtualization, Pello Heriz, yocto, meta-xilinx, Jason Wu, meta-xilinx-request On 3 May 2017 at 02:47, Manjukumar Harthikote Matha <manjukumar.harthikote-matha@xilinx.com> wrote: > > >> -----Original Message----- >> From: meta-xilinx-bounces@yoctoproject.org [mailto:meta-xilinx- >> bounces@yoctoproject.org] On Behalf Of Jason Wu >> Sent: Tuesday, May 02, 2017 2:16 AM >> 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 >> >> >> >> 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. >> > > Is there a way to stop inittab from doing this? > Tried few options for initiab, for ex: using "once" instead of "spawn" > > Any other good ideas on how we can disable it? Or what is a better approach to resolve this issue during runtime Change the sysvinit-inittab bbappend in meta-virtualization use start_getty instead of just getty, start_getty does a 'test -c' before starting getty on the device. This is how sysvinit-inittab handles SERIAL_CONSOLES. Alternatively the meta-virtualization bbappend could just expand SERIAL_CONSOLES. Regards, Nathan ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing @ 2017-05-02 17:23 ` Nathan Rossi 0 siblings, 0 replies; 9+ messages in thread From: Nathan Rossi @ 2017-05-02 17:23 UTC (permalink / raw) To: Manjukumar Harthikote Matha Cc: meta-virtualization, yocto, meta-xilinx, Jason Wu, meta-xilinx-request On 3 May 2017 at 02:47, Manjukumar Harthikote Matha <manjukumar.harthikote-matha@xilinx.com> wrote: > > >> -----Original Message----- >> From: meta-xilinx-bounces@yoctoproject.org [mailto:meta-xilinx- >> bounces@yoctoproject.org] On Behalf Of Jason Wu >> Sent: Tuesday, May 02, 2017 2:16 AM >> 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 >> >> >> >> 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. >> > > Is there a way to stop inittab from doing this? > Tried few options for initiab, for ex: using "once" instead of "spawn" > > Any other good ideas on how we can disable it? Or what is a better approach to resolve this issue during runtime Change the sysvinit-inittab bbappend in meta-virtualization use start_getty instead of just getty, start_getty does a 'test -c' before starting getty on the device. This is how sysvinit-inittab handles SERIAL_CONSOLES. Alternatively the meta-virtualization bbappend could just expand SERIAL_CONSOLES. Regards, Nathan ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 17:23 ` Nathan Rossi (?) @ 2017-05-02 18:28 ` Manjukumar Harthikote Matha 2017-05-02 19:48 ` Leonardo Sandoval -1 siblings, 1 reply; 9+ messages in thread From: Manjukumar Harthikote Matha @ 2017-05-02 18:28 UTC (permalink / raw) To: Nathan Rossi Cc: meta-virtualization, Pello Heriz, yocto, meta-xilinx, Jason Wu, meta-xilinx-request > -----Original Message----- > From: Nathan Rossi [mailto:nathan@nathanrossi.com] > Sent: Tuesday, May 02, 2017 10:23 AM > To: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com> > Cc: Jason Wu <jason.wu.misc@gmail.com>; 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 > > On 3 May 2017 at 02:47, Manjukumar Harthikote Matha <manjukumar.harthikote- > matha@xilinx.com> wrote: > > > > > >> -----Original Message----- > >> From: meta-xilinx-bounces@yoctoproject.org [mailto:meta-xilinx- > >> bounces@yoctoproject.org] On Behalf Of Jason Wu > >> Sent: Tuesday, May 02, 2017 2:16 AM > >> 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 > >> > >> > >> > >> 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. > >> > > > > Is there a way to stop inittab from doing this? > > Tried few options for initiab, for ex: using "once" instead of "spawn" > > > > Any other good ideas on how we can disable it? Or what is a better > > approach to resolve this issue during runtime > > Change the sysvinit-inittab bbappend in meta-virtualization use start_getty instead > of just getty, start_getty does a 'test -c' before starting getty on the device. This is > how sysvinit-inittab handles SERIAL_CONSOLES. Alternatively the meta-virtualization > bbappend could just expand SERIAL_CONSOLES. > Something like this? https://github.com/Xilinx/meta-virtualization/commit/610887495c01f0b17db6084e1426cc55a3f806ea We still see initab looking for console even after this change Thanks Manju > Regards, > Nathan This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [meta-xilinx] xen-image-minimal testing 2017-05-02 18:28 ` Manjukumar Harthikote Matha @ 2017-05-02 19:48 ` Leonardo Sandoval 0 siblings, 0 replies; 9+ messages in thread From: Leonardo Sandoval @ 2017-05-02 19:48 UTC (permalink / raw) To: Manjukumar Harthikote Matha Cc: meta-virtualization, Pello Heriz, yocto, meta-xilinx, Jason Wu, meta-xilinx-request On Tue, 2017-05-02 at 18:28 +0000, Manjukumar Harthikote Matha wrote: > > > -----Original Message----- > > From: Nathan Rossi [mailto:nathan@nathanrossi.com] > > Sent: Tuesday, May 02, 2017 10:23 AM > > To: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com> > > Cc: Jason Wu <jason.wu.misc@gmail.com>; 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 > > > > On 3 May 2017 at 02:47, Manjukumar Harthikote Matha <manjukumar.harthikote- > > matha@xilinx.com> wrote: > > > > > > > > >> -----Original Message----- > > >> From: meta-xilinx-bounces@yoctoproject.org [mailto:meta-xilinx- > > >> bounces@yoctoproject.org] On Behalf Of Jason Wu > > >> Sent: Tuesday, May 02, 2017 2:16 AM > > >> 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 > > >> > > >> > > >> > > >> 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. > > >> > > > > > > Is there a way to stop inittab from doing this? > > > Tried few options for initiab, for ex: using "once" instead of "spawn" > > > > > > Any other good ideas on how we can disable it? Or what is a better > > > approach to resolve this issue during runtime > > > > Change the sysvinit-inittab bbappend in meta-virtualization use start_getty instead > > of just getty, start_getty does a 'test -c' before starting getty on the device. This is > > how sysvinit-inittab handles SERIAL_CONSOLES. Alternatively the meta-virtualization > > bbappend could just expand SERIAL_CONSOLES. > > > Something like this? > https://github.com/Xilinx/meta-virtualization/commit/610887495c01f0b17db6084e1426cc55a3f806ea > > We still see initab looking for console even after this change another approach, including the following into your local.conf SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}" or if you are using qemu, the following poky commit id can be cherry-picked 86d6b790eb7 which avoids the entry on inittab for ttyS1. Leo > > Thanks > Manju > > > > Regards, > > Nathan > > > This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. > ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-05-02 19:41 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-05-02 6:33 xen-image-minimal testing Pello Heriz 2017-05-02 9:16 ` [meta-xilinx] " Jason Wu 2017-05-02 16:04 ` 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
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.