From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sasha Levin <levinsasha928@gmail.com>
Subject: Re: Controlling (WinXP-Guest)- Textmode via chardev pipe broken?
Date: Tue, 20 Dec 2011 14:08:58 +0200
Message-ID: <1324382938.22797.16.camel@lappy>
References: <4EF05CE4.9090107@mglug.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Oliver Rath <rath@mglug.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-ww0-f44.google.com ([74.125.82.44]:41864 "EHLO
	mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750755Ab1LTMJC (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 20 Dec 2011 07:09:02 -0500
Received: by wgbdr13 with SMTP id dr13so12400804wgb.1
        for <kvm@vger.kernel.org>; Tue, 20 Dec 2011 04:09:01 -0800 (PST)
In-Reply-To: <4EF05CE4.9090107@mglug.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.