From: jd <jdsw2002@yahoo.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>, KVM List <kvm@vger.kernel.org>
Subject: Re: KVM Management : Paused stauts
Date: Tue, 7 Oct 2008 10:09:42 -0700 (PDT) [thread overview]
Message-ID: <905421.892.qm@web35805.mail.mud.yahoo.com> (raw)
In-Reply-To: <48EB76FA.3040306@redhat.com>
I would request to get new info command in.
I am sure you realize that remembering the state is not complete solution. When the management tool comes up, it needs to query the VMs and know its current state and sync it with what it knows.
Thanks
/Jd
--- On Tue, 10/7/08, Avi Kivity <avi@redhat.com> wrote:
> From: Avi Kivity <avi@redhat.com>
> Subject: Re: KVM Management : Paused stauts
> To: jdsw2002@yahoo.com
> Cc: "Anthony Liguori" <anthony@codemonkey.ws>, "KVM List" <kvm@vger.kernel.org>
> Date: Tuesday, October 7, 2008, 7:49 AM
> jd wrote:
> > Thanks for clarifying.
> >
> > So back to my original question, how do I determine
> (via monitor/console) if the guest is in
> "halted"/stop state ?
> >
>
> No idea. Presumably a new info subcommand.
>
> But if you're issuing the stop and cont command, you
> can simply remember
> the last command you sent.
>
> --
> 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 majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-07 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 2:04 KVM Management : Paused stauts jd
2008-08-09 15:40 ` Anthony Liguori
2008-08-09 21:12 ` jd
2008-10-03 22:04 ` jd
2008-10-04 12:46 ` Avi Kivity
2008-10-04 22:37 ` jd
2008-10-05 14:18 ` Avi Kivity
2008-10-06 13:04 ` jd
2008-10-07 14:49 ` Avi Kivity
2008-10-07 17:09 ` jd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=905421.892.qm@web35805.mail.mud.yahoo.com \
--to=jdsw2002@yahoo.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.