Author: arekm Date: Sat Nov 6 19:19:23 2010 GMT Module: PLDWWW URL: http://www.pld-linux.org/Docs/Vserver?action=diff&rev2=160&rev1=159 ---- Log message:
---- Page affected: Docs/Vserver ---- Diffs: ================================================================ You end with one interface on the host and one inside guest (virtually connected). Configure interfaces, routing as on normal system. Notes: - - this method is racy. post-start is running in parallel to init process inside of guest system. If guest is faster and tries to configure networking before post-start puts new iterface into guest you are doomed. Fortunately this is unlikely to happen as post-start is short and should always be first before networking is being configured by guest scripts. Race could be avoided by implementing proper netns interface moving support into util-vserver scripts. + * this method is racy. post-start is running in parallel to init process inside of guest system. If guest is faster and tries to configure networking before post-start puts new iterface into guest you are doomed. Fortunately this is unlikely to happen as post-start is short and should always be first before networking is being configured by guest scripts. Race could be avoided by implementing proper netns interface moving support into util-vserver scripts. + - - enabling pid namespace is likely to break post-start script (part with guest pid fetching for iproute2 netns use) + * enabling pid namespace is likely to break post-start script (part with guest pid fetching for iproute2 netns use) _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
