On Tue, 2017-05-02 at 18:28 +0000, Manjukumar Harthikote Matha wrote:
>
> > -----Original Message-----
> > From: Nathan Rossi [mailto:[email protected]]
> > Sent: Tuesday, May 02, 2017 10:23 AM
> > To: Manjukumar Harthikote Matha <[email protected]>
> > Cc: Jason Wu <[email protected]>; Pello Heriz
> > <[email protected]>; [email protected];
> > meta-xilinx-
> > [email protected]; [email protected];
> > [email protected]
> > Subject: Re: [meta-xilinx] xen-image-minimal testing
> >
> > On 3 May 2017 at 02:47, Manjukumar Harthikote Matha <manjukumar.harthikote-
> > [email protected]> wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: [email protected] [mailto:meta-xilinx-
> > >> [email protected]] On Behalf Of Jason Wu
> > >> Sent: Tuesday, May 02, 2017 2:16 AM
> > >> To: Pello Heriz <[email protected]>; meta-
> > >> [email protected]; [email protected]; meta-
> > >> [email protected]; [email protected]
> > >> 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.
>
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
