From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM Management : Paused stauts Date: Sun, 05 Oct 2008 16:18:35 +0200 Message-ID: <48E8CCBB.6060106@redhat.com> References: <828702.37143.qm@web35806.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , KVM List To: jdsw2002@yahoo.com Return-path: Received: from mx2.redhat.com ([66.187.237.31]:46744 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753645AbYJEOSl (ORCPT ); Sun, 5 Oct 2008 10:18:41 -0400 In-Reply-To: <828702.37143.qm@web35806.mail.mud.yahoo.com> Sender: kvm-owner@vger.kernel.org List-ID: jd wrote: >> "halted" actually means the vcpu is idle >> (executing a hlt instruction), >> not that the vm is halted. >> > > > Can u please elaborate a bit on this ? when does guest get in to executing 'hlt' Vs in to 'VM halt' > > My understanding is that when guest executes shutdown sequence, eventually it will execute hlt. > > No, hlt is part of the guest idle loop. It will execute hlt whenever the processor has nothing to do. During shutdown it will execute an ACPI sequence that results in qemu exiting. > When you give stop via the monitor/console, what happens ? (and on continue) > Qemu no longer allows the vcpu to execute. If it was in halted state, it stays that way, and if it wasn't it also stays that way. When you continue, the vcpu gets more cpu time and can proceed. -- error compiling committee.c: too many arguments to function