From owner-freebsd-virtualization@freebsd.org Mon Mar 11 17:09:48 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2625B15268B4 for ; Mon, 11 Mar 2019 17:09:48 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C135C7088D for ; Mon, 11 Mar 2019 17:09:47 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CAC6D254E8 for ; Mon, 11 Mar 2019 13:09:46 -0400 (EDT) Received: from imap3 ([10.202.2.53]) by compute6.internal (MEProxy); Mon, 11 Mar 2019 13:09:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=corrupted.io; h= message-id:in-reply-to:references:date:from:to:subject :content-type; s=mesmtp; bh=A3W3eU8fcMn8ud6MI3A3vLiB1CAR/AGB4ETE CZwF7+E=; b=Kz7mTumKiMMdgDPvCDq8+xylk9MTTfRb5G89CVS1ZcGMzBOogD6U yclw2J459XiuXFA6Fx4rzrt5TGSBeJ26qxdd25vdAqLZhZRpUNAtTobXgqIWwLuf JPJWrUJ1pdduF8nsG3gnEng9m9KFQyZyLxLL+OZYk5oZPXXqYdhrrWo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=A3W3eU8fcMn8ud6MI 3A3vLiB1CAR/AGB4ETECZwF7+E=; b=UKWguJNAKuv4Jy0hXHPQfxmEZlCk+uX2E kegOZS6qFDsxHHARVgFWnrEzRHXCjQZ+z+bfxmCpW7jXXw2LblrQnzYSm8B0AFEq +SmZ91GERLZFqOSsEa4x5mQQwHNL92peT5+fcvobswxVpH1ispGeTT1arpWtiMF+ aqGiJE4PBXp+dPjJntlyLGpQ0IyzDvCKEjVH5sjTRTCFRBUDx43cYZUM94VGJk9+ XssWuX+Yjlgwd7YCy2DFngXpa/apMHeUIdixG/8XzI7xt7bZNoM/zQRLVdvHDZG1 mEIAOj/UkUl/Kx1eEEbOuReerHm6c3Z8fPZ7DMsD02DbA4WfbEbsg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgeeigdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfkfgjfhffhffvufgtsehttdertd erredtnecuhfhrohhmpedflfgrshhonhcuuegrrhgsihgvrhdfuceojhgrshhonhestgho rhhruhhpthgvugdrihhoqeenucffohhmrghinhepphhrohhmvghthhgvuhhsrdhiohdpih hojehmrdgtohhmnecurfgrrhgrmhepmhgrihhlfhhrohhmpehjrghsohhnsegtohhrrhhu phhtvggurdhiohenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4A0FC7C16B; Mon, 11 Mar 2019 13:09:46 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5 X-Me-Personality: 64405576 Message-Id: <09d8981f-6dae-4c84-a1e4-0c9f4aa5cc41@www.fastmail.com> In-Reply-To: <20190311170420.61bd34c6@almond.int.arc7.info> References: <20190311170420.61bd34c6@almond.int.arc7.info> Date: Mon, 11 Mar 2019 13:09:45 -0400 From: "Jason Barbier" To: freebsd-virtualization@freebsd.org Subject: Re: bhyve: Detecting that a guest kernel has booted Content-Type: text/plain X-Rspamd-Queue-Id: C135C7088D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.989,0] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 17:09:48 -0000 None I know off the top of my head nor would that be really something easily done without some sort of agent. We could probably make some sort of inference based calls to the emulated registers but even then that wouldn't be that correct. --- Jason Barbier | E: jason@corrupted.io On Mon, Mar 11, 2019, at 10:05 AM, Mark Raynsford via freebsd-virtualization wrote: > Hello! > > Leaving aside userland monitoring tools such as Prometheus[0], is there > any way to detect on the host that a guest kernel running in bhyve has > booted? I'm assuming "booted" in this sense to mean "PID 1 has probably > started". I'm guessing that there probably isn't, but I thought I'd > better ask anyway. "Not booted" would mean something like "Is sitting > at the Grub prompt doing nothing". > > [0] https://prometheus.io/ > > -- > Mark Raynsford | http://www.io7m.com > > > Attachments: > * null