From: Sasha Levin <levinsasha928@gmail.com>
To: Oliver Rath <rath@mglug.de>
Cc: kvm@vger.kernel.org
Subject: Re: Controlling (WinXP-Guest)- Textmode via chardev pipe broken?
Date: Tue, 20 Dec 2011 14:08:58 +0200 [thread overview]
Message-ID: <1324382938.22797.16.camel@lappy> (raw)
In-Reply-To: <4EF05CE4.9090107@mglug.de>
On Tue, 2011-12-20 at 11:01 +0100, Oliver Rath wrote:
> Hi List,
>
> Im trying to control a winxp installation process (esp. the text-mode
> part) via pipe through kvm. Im using the git-version of kvm from
> yesterday (2011-12-19), build with these parameters:
>
> ~/qemu-kvm$ ./configure --enable-sdl
> ~/qemu-kvm$ make
> ~/qemu-kvm$ sudo make install
>
> What works:
>
> 1. Generating ~/.winpipe/path.{in,out}via mkdir .winpipe; mkfifo
> .winpipe/path.in; mkfifo .winpipe/path.out
> 2. Creating emty image via qemu-img create win.img 20G
> 3. Starting kvm via: qemu-system-x86_64 -m 1G -hda win.img -cdrom
> winxpsp3.iso -chardev pipe,id=mywinpipe,path=.winpipe/path
>
> What doesn't:
>
> 1. Piping some text via echo "R" > .winpipe/path.in (i.e. for starting
> repair console in winxp-textmode) doesnt have any effect
> 2. Reading from path.out via cat ~/.winpipe/path.out (nothing happens
> except the vm ends, then the command "cat .winpipe/path.out" ends, too)
> has no result, only waiting
> 3. There is no .pipe/ directory inside winxp, wether on C: nor on D:
> (looked in via starting repair-console with "R")
>
>
> 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.
--
Sasha.
next prev parent reply other threads:[~2011-12-20 12:09 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 [this message]
2011-12-22 15:37 ` SOLVED [was Re: Controlling (WinXP-Guest)- Textmode via chardev pipe broken?] Oliver Rath
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=1324382938.22797.16.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=rath@mglug.de \
/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.