From: Avi Kivity <avi@redhat.com>
To: Michael Jinks <michael.jinks@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Newbie, struggling with graphics and qemu monitor
Date: Wed, 01 Jul 2009 11:43:09 +0300 [thread overview]
Message-ID: <4A4B219D.1040708@redhat.com> (raw)
In-Reply-To: <f02c30210906301133u387e74b6l42b7235c82ed8f30@mail.gmail.com>
On 06/30/2009 09:33 PM, Michael Jinks wrote:
> In an attempt to get past unrelated interference I just set up an X
> session with only an xterm, used that to launch VNC connecting to my
> KVM test host, and tried to launch my test guest again. Same
> behavior: Ctl-Alt patterns are ignored, as are any other keystrokes I
> try to send to the qemu console window, which won't release my mouse.
>
> I've looked but haven't found any way to attach a monitor process to
> an already-running guest. Is this possible? Or do we only get a
> monitor as a child process of the initial kvm invocation?
>
Look up the -monitor option.
> Given the way qemu and screen interact, using the same keystrokes to
> initiate commands, it would be really useful to have some other way to
> detach and re-attach to a kvm guest on the fly.
>
>
If you run qemu in screen, use -vnc. X and screen don't mix.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-01 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f02c30210906300835h49ac0a31xb28e538c7c0f0c4c@mail.gmail.com>
2009-06-30 16:18 ` Newbie, struggling with graphics and qemu monitor Avi Kivity
2009-06-30 16:44 ` Anthony Liguori
2009-06-30 17:11 ` Michael Jinks
2009-06-30 17:25 ` Michael Jinks
2009-06-30 18:33 ` Michael Jinks
2009-06-30 19:49 ` Charles Duffy
2009-07-01 8:43 ` Avi Kivity [this message]
2009-07-01 13:56 ` Michael Jinks
2009-07-01 14:50 ` Avi Kivity
2009-06-30 17:00 ` Michael Jinks
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=4A4B219D.1040708@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=michael.jinks@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox