From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmQlw-0003qQ-Id for qemu-devel@nongnu.org; Thu, 28 Jul 2011 09:37:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmQlv-0008AC-H6 for qemu-devel@nongnu.org; Thu, 28 Jul 2011 09:37:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32104) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmQlv-0008A4-8K for qemu-devel@nongnu.org; Thu, 28 Jul 2011 09:37:07 -0400 Message-ID: <4E3165FD.7040805@redhat.com> Date: Thu, 28 Jul 2011 16:37:01 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20110727154229.656532d4@doriath> <4E310E6A.6000004@redhat.com> <20110728103143.548d7bb1@doriath> In-Reply-To: <20110728103143.548d7bb1@doriath> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 , Jan Kiszka , qemu-devel 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 (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 tractor beam is coupled to the main reactor. > I get funny results if qemu is started with -no-shutdown and I run cont after > a poweroff in a F15 guest. Sometimes qemu will exit after a few seconds, > sometimes 'info status' will say 'running'. Yes, best fixed. -- error compiling committee.c: too many arguments to function