From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmOTE-0007rC-0U for qemu-devel@nongnu.org; Sun, 15 Jan 2012 06:41:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RmOTC-0001HG-EC for qemu-devel@nongnu.org; Sun, 15 Jan 2012 06:41:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:64281) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RmOTB-0001Gz-In for qemu-devel@nongnu.org; Sun, 15 Jan 2012 06:41:54 -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> Content-Type: text/plain; charset="UTF-8" Date: Sun, 15 Jan 2012 13:41:38 +0200 Message-ID: <1326627698.2734.1.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: Stefan Hajnoczi Cc: spice-devel@lists.freedesktop.org, 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 , =?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?= On Sun, 2012-01-15 at 11:27 +0000, Stefan Hajnoczi wrote: > 2012/1/14 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 : > > I tested Qemu 0.15 for Windows XP guest OS. But I found that t= he Virtual Serial I/O driver failed in driver initialization. > > The root cause of this problem is because the hardware resourc= es(I/O in this device) is not allocated to the virtual serial I/O. > > When I debugged on the vioserial driver, no hardware resource = actually is allocated to this device. > > This bug seems to be in the area of Qemu. Do you know whom I c= an consult to fix this problem? Please let me know if you know the group = or the person. >=20 > I have CCed Vadim (virtio Windows driver) and the QEMU mailing list. >=20 > Please post your QEMU command-line so we can see how the guest is confi= gured. >=20 > You mentioned that you debugged the driver and hardware resources > weren't allocated. Do you have a virtio PCI device inside the guest > for this virtio-serial device? Were you able to tell which part of > driver initialization failed (finding the PCI device, mapping its > resources (BARs), etc)? >=20 > Stefan Could you post "pci info" output? thanks, Vadim.