Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Capabilities, Anybody?
Date: Fri, 15 Mar 2024 21:14:49 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <ut2do9$2fd1e$6@dont-email.me>
References: <usg40i$1udfo$3@dont-email.me> <ussqji$12vjp$1@dont-email.me>
	<03159371a8f3251ced2cd3be21505896@www.novabbs.org>
	<usta7f$16buu$2@dont-email.me>
	<7bd273d4426dbdecfb3c3569506e8fe9@www.novabbs.org>
	<ustepe$17drt$2@dont-email.me>
	<98c115566bd98cef502d3c29cb9d2e71@www.novabbs.org>
	<ustlmu$18ma1$3@dont-email.me>
	<185db17a6fbfc62a1cbba4da890ad84d@www.novabbs.org>
	<usvuq5$1so4m$2@dont-email.me> <ut04aa$1tppl$1@dont-email.me>
	<ut08eu$1ugmi$2@dont-email.me> <Y4ZIN.418306$vFZa.399078@fx13.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 15 Mar 2024 21:14:49 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="923cb71133c4c2bd336d691e5929520c";
	logging-data="2602030"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/AOSHIXjNsZqOas/kjrtSv"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:vmhz5NW4Pxv9JjWWfNYYr5JQQns=
Bytes: 2274

On Fri, 15 Mar 2024 14:39:52 GMT, Scott Lurndal wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>
>>Event-driven would be more efficient and more responsive than periodic
>>polling.
> 
> That assumes that an event can be generated, which may not be possible
> with a guest os crash (if, for example, it was in an infinite loop with
> interrupts disabled).

It wouldn’t be a “guest OS”, it would be a “guest container”. Remember, 
the processes in the container are isolated from the host, but the host 
continues to have full visibility into the guest.

For a container, guest termination is synonymous with termination of its 
guest-specific “init” (container-internal PID 1) process. A host watcher 
process can monitor several of these at once via the Linux pidfd mechanism
<https://manpages.debian.org/2/pidfd_open.en.html>.