From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmUle-0003Ec-TO for qemu-devel@nongnu.org; Thu, 28 Jul 2011 13:53:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmUld-0000EM-Ug for qemu-devel@nongnu.org; Thu, 28 Jul 2011 13:53:06 -0400 Received: from fmmailgate03.web.de ([217.72.192.234]:36021) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmUld-0000Dy-Ie for qemu-devel@nongnu.org; Thu, 28 Jul 2011 13:53:05 -0400 Message-ID: <4E31A1DF.2050702@web.de> Date: Thu, 28 Jul 2011 19:52:31 +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> <4E317E49.5090708@web.de> <20110728143923.3183d349@doriath> <20110728144831.766fa270@doriath> In-Reply-To: <20110728144831.766fa270@doriath> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD096C3DEFC4BF9C10CC771E9" 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) --------------enigD096C3DEFC4BF9C10CC771E9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-07-28 19:48, Luiz Capitulino wrote: > On Thu, 28 Jul 2011 14:39:23 -0300 > Luiz Capitulino wrote: >=20 >> On Thu, 28 Jul 2011 17:20:41 +0200 >> Jan Kiszka wrote: >> >>> On 2011-07-28 17:18, Luiz Capitulino wrote: >>>> On Thu, 28 Jul 2011 16:19:19 +0200 >>>> Jan Kiszka wrote: >>>> >>>>> 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= very >>>>>>>> > permanent anymore, so the name would need adjusting. >>>>>>>> >>>>>>>> Currently, all kvm internal errors are recoverable by reset (an= d >>>>>>>> possibly by fiddling with memory/registers). >>>>>>> >>>>>>> Ok, but a poweroff in the guest isn't recoverable with system_res= et >>>>>>> right? Or does it depend on the guest? >>>>>> >>>>>> Right, it's not recoverable if you shut the power down where the t= ractor >>>>>> 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 con= sider >>>>> issuing this reset automatically on vm_start after "permant" vm_sto= p. >> >> The only permanent vm_stop we'd have is poweroff when -no-shutdown is = used. >> >> Are you saying that system_reset should be able to recover from that t= oo? >=20 > It already does, so we don't have permanent stops. Exactly. We just have stops over inconsistent states that require a reset to continue with anything useful. Jan --------------enigD096C3DEFC4BF9C10CC771E9 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/ iEYEARECAAYFAk4xoeIACgkQitSsb3rl5xTneACghV1HnaFNAL9SFW2N8kSwb68I a9sAnj7NuPI/GZBLWC7D47tK0KkLDVB4 =vX7o -----END PGP SIGNATURE----- --------------enigD096C3DEFC4BF9C10CC771E9--