[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] automation: document vsyscall=emulate for old glibc
> -----Original Message----- > From: Xen-devel <xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of Wei > Liu > Sent: 25 February 2020 12:11 > To: Xen Development List <xen-devel@xxxxxxxxxxxxxxxxxxxx> > Cc: Doug Goldstein <cardoe@xxxxxxxxxx>; Wei Liu <wl@xxxxxxx> > Subject: [Xen-devel] [PATCH] automation: document vsyscall=emulate for old > glibc > > Signed-off-by: Wei Liu <wl@xxxxxxx> > --- > automation/build/README.md | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/automation/build/README.md b/automation/build/README.md > index 476f82cf45..8cda2b65a5 100644 > --- a/automation/build/README.md > +++ b/automation/build/README.md > @@ -58,6 +58,16 @@ understands. > - XEN_CONFIG_EXPERT: If this is defined in your shell it will be > automatically passed through to the container. > > +If your docker host has Linux kernel > 4.11, and you want to use > containers > +that run old glibc (for example, CentOS 6 or SLES11SP4), you may need to > add > + > +``` > +vsyscall=emulate > +``` > + > +to the host kernel command line. That enables a legacy interface that is > used > +by old glibc. > + I can vouch that it is indeed necessary. Reviewed-by: Paul Durrant <pdurrant@xxxxxxxxxx> > > Building a container > -------------------- > -- > 2.20.1 > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxxx > https://lists.xenproject.org/mailman/listinfo/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |