Thanks for clarifying. So back to my original question, how do I determine (via monitor/console) if the guest is in "halted"/stop state ?
/Jd --- On Sun, 10/5/08, Avi Kivity <[EMAIL PROTECTED]> wrote: > From: Avi Kivity <[EMAIL PROTECTED]> > Subject: Re: KVM Management : Paused stauts > To: [EMAIL PROTECTED] > Cc: "Anthony Liguori" <[EMAIL PROTECTED]>, "KVM List" <[email protected]> > Date: Sunday, October 5, 2008, 7:18 AM > 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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
