From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrCOM-0000vE-KM for qemu-devel@nongnu.org; Mon, 15 Mar 2010 11:39:42 -0400 Received: from [199.232.76.173] (port=53756 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrCOL-0000v3-6Y for qemu-devel@nongnu.org; Mon, 15 Mar 2010 11:39:41 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NrCOK-0006yP-2i for qemu-devel@nongnu.org; Mon, 15 Mar 2010 11:39:40 -0400 Received: from smtp2-g21.free.fr ([212.27.42.2]:33182) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NrCO6-0006sA-5P for qemu-devel@nongnu.org; Mon, 15 Mar 2010 11:39:39 -0400 Received: from smtp2-g21.free.fr (localhost [127.0.0.1]) by smtp2-g21.free.fr (Postfix) with ESMTP id 05D3C4B01FB for ; Mon, 15 Mar 2010 16:37:32 +0100 (CET) Received: from laptop (vaf26-2-82-244-111-82.fbx.proxad.net [82.244.111.82]) by smtp2-g21.free.fr (Postfix) with ESMTP id 13B494B00F4 for ; Mon, 15 Mar 2010 16:37:30 +0100 (CET) In-Reply-To: <201003151526.24615.paul@codesourcery.com> Subject: Re: [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Mon, 15 Mar 2010 16:37:37 +0100 CET Message-Id: <4548325200-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Le Mon, 15 Mar 2010 15:26:24 +0000, Paul Brook a =C3=A9crit : > > Ideally this would evolve into supporting IPMI, which would allow > > managing VMs exactly like physical servers without concern, appart > > launching the actual process first. > > cf. > > http://en.wikipedia.org/wiki/Intelligent=5FPlatform=5FManagement=5FInterface > > > > http://openipmi.sourceforge.net/ > > > > Anyone interested in this =3F > > Anyone tried already =3F > > TBH I don't really see the point. > > This definitely seems like something that should be handled by your > your > mangement app (via libvirt, or whatever). i.e. have that implement > whatever > remote protocol you want, and just talk to qemu over the normal > monitor > interface. Hmm for IPMI that might probably indeed be a better way, moreover since they use a parallel subnet on the primary ethernet card... Though it would require the implementation to listen to the same virtual card, which are mapped differently to the host depending on the VM (-net user, ...). As for WOL, it would still be handy to have I think... btw, do we support suspending the emulation via ACPI =3F VirtualBox has something called "Pause" mode, which I'm not sure actually if it's reflected to ACPI, which allows to avoid wasting cpu when not usign the guest, though it requires support from the Guest Additions to avoid clock drifts. Fran=C3=A7ois.