From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DNX34-0001Ir-Uw
	for qemu-devel@nongnu.org; Mon, 18 Apr 2005 10:16:27 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DNX2z-0001GL-K6
	for qemu-devel@nongnu.org; Mon, 18 Apr 2005 10:16:25 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DNX2z-00019d-67
	for qemu-devel@nongnu.org; Mon, 18 Apr 2005 10:16:21 -0400
Received: from [64.233.184.199] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DNWxF-0002Mf-L1
	for qemu-devel@nongnu.org; Mon, 18 Apr 2005 10:10:25 -0400
Received: by wproxy.gmail.com with SMTP id 71so2329043wra
	for <qemu-devel@nongnu.org>; Mon, 18 Apr 2005 07:08:51 -0700 (PDT)
Message-ID: <46d6db6605041807085a8493cd@mail.gmail.com>
Date: Mon, 18 Apr 2005 16:08:50 +0200
From: Christian MICHON <christian.michon@gmail.com>
Subject: Re: [Qemu-devel] qemu osdep.c kqemu.c
In-Reply-To: <4262DF7B.6010001@bellard.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <E1DNEaZ-0005kP-00@savannah.gnu.org>
	<2ad73a05041712204b47591f@mail.gmail.com>
	<46d6db6605041713351b7f22a6@mail.gmail.com>
	<4262DF7B.6010001@bellard.org>
Reply-To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org, qvm86-devel@nongnu.org

understood. Yet, I discovered some preliminary qvm86 support for
win hosts. I tried it, and I can see linux or xp guests unable to
complete their boot sequences.

I can see more time is needed. I can also confirm based on qvm86
experiments you've to be admin to at least do "net start qvm86".

to the qvm86 users mailing list, my host did not reboot as I'm running
qemu as a std user (only "net start qvm86" as admin).

Christian

On 4/18/05, Fabrice Bellard <fabrice@bellard.org> wrote:
>  > Can it be run as simple user, or power user, or administrator?
>  > I expect you must be admin on XP to be able to launch some service.
>  > I'll try tomorrow anyway :)
>=20
> The kqemu kernel module for Windows is not yet available, but it will
> come soon.
>=20
> Fabrice.
>=20
>=20
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>=20


--=20
Christian