From: Oliver Rath <rath@mglug.de>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org
Subject: SOLVED [was Re: Controlling (WinXP-Guest)- Textmode via chardev pipe broken?]
Date: Thu, 22 Dec 2011 16:37:34 +0100 [thread overview]
Message-ID: <4EF34EBE.6050204@mglug.de> (raw)
In-Reply-To: <1324382938.22797.16.camel@lappy>
Am 20.12.2011 13:08, schrieb Sasha Levin:
> [..]
> Whats wrong?
> Are you sure that windows is using the serial device at all?
>
> You're not emulating a keyboard there, you're emulating input from a
> serial device.
>
HI Sasha,
Ive found a better solution:
It is possible to pipe the qemu-monitor:
qemu ... -monitor pipe:.winpipe/path
so Im able to send commands through the path.in pipe via
sendkey-kommand, i.e.
echo "sendkey r" > .winpipe/path.in
echo "sendkey d" > .winpipe/path.in
echo "sendkey shift-dot" > .winpipe/path.in
echo "sendkey ret" > .winpipe/path.in
Its not very komfortable, but does its job :-)
Tfh!
Regards,
Oliver
prev parent reply other threads:[~2011-12-22 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 10:01 Controlling (WinXP-Guest)- Textmode via chardev pipe broken? Oliver Rath
2011-12-20 12:08 ` Sasha Levin
2011-12-22 15:37 ` Oliver Rath [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=4EF34EBE.6050204@mglug.de \
--to=rath@mglug.de \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@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;
as well as URLs for NNTP newsgroup(s).