From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53040) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmSOK-0000tk-LK for qemu-devel@nongnu.org; Thu, 28 Jul 2011 11:20:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmSOJ-0008TX-Dv for qemu-devel@nongnu.org; Thu, 28 Jul 2011 11:20:52 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:33353) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmSOJ-0008TQ-2y for qemu-devel@nongnu.org; Thu, 28 Jul 2011 11:20:51 -0400 Message-ID: <4E317E49.5090708@web.de> Date: Thu, 28 Jul 2011 17:20:41 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20110727154229.656532d4@doriath> <4E310E6A.6000004@redhat.com> <20110728103143.548d7bb1@doriath> <4E3165FD.7040805@redhat.com> <4E316FE7.6030005@web.de> <20110728121811.11dc8434@doriath> In-Reply-To: <20110728121811.11dc8434@doriath> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFEB3C6B5FC1FE41AFA801D3A" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [RFC] Introduce vm_stop_permanent() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Blue Swirl , Avi Kivity , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFEB3C6B5FC1FE41AFA801D3A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-07-28 17:18, Luiz Capitulino wrote: > On Thu, 28 Jul 2011 16:19:19 +0200 > Jan Kiszka wrote: >=20 >> On 2011-07-28 15:37, Avi Kivity wrote: >>> On 07/28/2011 04:31 PM, Luiz Capitulino wrote: >>>> On Thu, 28 Jul 2011 10:23:22 +0300 >>>> Avi Kivity wrote: >>>> >>>>> On 07/28/2011 12:44 AM, Blue Swirl wrote: >>>>> > On Wed, Jul 27, 2011 at 9:42 PM, Luiz >>>> Capitulino wrote: >>>>> > > This function should be used when the VM is not supposed to= >>>> resume >>>>> > > execution (eg. by issuing 'cont' monitor command). >>>>> > > >>>>> > > Today, we allow the user to resume execution even when: >>>>> > > >>>>> > > o the guest shuts down and -no-shutdown is used >>>>> > > o there's a kvm internal error >>>>> > > o loading the VM state with -loadvm or "loadvm" in the >>>> monitor fails >>>>> > > >>>>> > > I think only badness can happen from the cases above. >>>>> > >>>>> > I'd suppose a system_reset should bring the system back to >>>> sanity and >>>>> > then clear vm_permanent_stopped (where's -ly?) >>>> >>>> What's -ly? >>>> >>> >>> permanent-ly. >>> >>>>> > except maybe for KVM >>>>> > internal error if that can't be recovered. Then it would not ve= ry >>>>> > permanent anymore, so the name would need adjusting. >>>>> >>>>> Currently, all kvm internal errors are recoverable by reset (and >>>>> possibly by fiddling with memory/registers). >>>> >>>> Ok, but a poweroff in the guest isn't recoverable with system_reset >>>> right? Or does it depend on the guest? >>> >>> Right, it's not recoverable if you shut the power down where the trac= tor >>> beam is coupled to the main reactor. >> >> system_reset will bring all emulated devices back into their power-on >> state - unless we have remaining bugs to fix. Actually, one may consid= er >> issuing this reset automatically on vm_start after "permant" vm_stop. >=20 > I'm going to abandon the vm_stop_permanent() idea. >=20 > I'm thinking something towards having a stop_kind argument to vm_stop()= , > which could be temporary (which is what we have today), only with > system_reset or permanent. >=20 > Or maybe vm_stop_opt(), which allows for fine grained control of stop > (vm_stop() would default to today's behavior)... But the right point for reset is start, not stop. Otherwise we loose the state before the stop. Jam --------------enigFEB3C6B5FC1FE41AFA801D3A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAk4xflAACgkQitSsb3rl5xTEwgCgsZH4cGsKP/861NtQt04krzkr 9a0AmKS2oYKNWVx8x3Qdhu1S7eKrkGc= =ohCw -----END PGP SIGNATURE----- --------------enigFEB3C6B5FC1FE41AFA801D3A--