From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40643) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnG8I-0004DU-Tc for qemu-devel@nongnu.org; Tue, 17 Jan 2012 15:59:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RnG8H-0001gi-Qp for qemu-devel@nongnu.org; Tue, 17 Jan 2012 15:59:54 -0500 Received: from mx1.redhat.com ([209.132.183.28]:16504) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RnG8G-0001ga-VQ for qemu-devel@nongnu.org; Tue, 17 Jan 2012 15:59:53 -0500 From: Vadim Rozenfeld In-Reply-To: References: <20120101114514.GC20432@garlic.redhat.com> <20120101141928.GE20432@garlic.redhat.com> <20120102101855.GH20432@garlic.redhat.com> <20120102114919.GJ20432@garlic.redhat.com> <1326627698.2734.1.camel@vadimr.dell> <1326698016.2734.13.camel@vadimr.dell> <1326749266.2734.32.camel@vadimr.dell> Content-Type: text/plain; charset="UTF-8" Date: Tue, 17 Jan 2012 22:59:39 +0200 Message-ID: <1326833979.5467.6.camel@vadimr.dell> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Charles=2ETsai-=E8=94=A1=E6=B8=85=E6=B5=B7-=E7=A0=94=E7=A9=B6?= =?UTF-8?Q?=E7=99=BC=E5=B1=95=E9=83=A8?= Cc: Stefan Hajnoczi , Alex =?UTF-8?Q?Huang-=E9=BB=83=E5=BF=85=E8=B3=A2-=E7=A0=94=E7=A9=B6=E7=99=BC?= =?UTF-8?Q?=E5=B1=95=E9=83=A8?= , Alon Levy , qemu-devel , spice-devel@lists.freedesktop.org On Tue, 2012-01-17 at 10:03 +0800, Charles.Tsai-=E8=94=A1=E6=B8=85=E6=B5=B7= -=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 wrote: > Vadim, >=20 > I am sorry that it was my mistake because I did not see there was a PIC= device which was created with no device driver installed. > Instead of updating the driver, I ran the hardware installation wizard = to install the Vioserial driver. > As such, the system could not install the device for me since it was t= aken over by another device already. > Thank you for your help and I learned a lot about how a hardware device= is virtualized by Qemu. >=20 You're welcome. Vadim. =20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com]=20 > Sent: Tuesday, January 17, 2012 5:28 AM > To: Charles.Tsai-=E8=94=A1=E6=B8=85=E6=B5=B7-=E7=A0=94=E7=A9=B6=E7=99=BC= =E5=B1=95=E9=83=A8 > Cc: Stefan Hajnoczi; Alon Levy; spice-devel@lists.freedesktop.org; Alex= Huang-=E9=BB=83=E5=BF=85=E8=B3=A2-=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9= =83=A8; qemu-devel > Subject: RE: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > On Mon, 2012-01-16 at 17:17 +0800, Charles.Tsai-=E8=94=A1=E6=B8=85=E6=B5= =B7-=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 wrote: > > Vadim, > >=20 > > I just ran the Qemu monitor to get the PCI information. The informati= on is listed belowe. > > From the listed information, I did not see anything wrong with the BA= R0. > > ----------- > Thank you. >=20 > > >=20 > > > 2). In Guest Windows XP OS > > > > SP3? > Can you try reproducing this problem on Win7? >=20 > Best regards, > Vadim.=20 >=20 >=20