From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39586) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S9YiI-0003mm-U3 for qemu-devel@nongnu.org; Mon, 19 Mar 2012 05:17:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S9Yhq-0007y8-Ly for qemu-devel@nongnu.org; Mon, 19 Mar 2012 05:17:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65350) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S9Yhq-0007y1-BO for qemu-devel@nongnu.org; Mon, 19 Mar 2012 05:16:46 -0400 From: Vadim Rozenfeld Date: Mon, 19 Mar 2012 11:16:32 +0200 References: <6d86f570-8783-4a28-8772-e83a306923c4@zmail09.collab.prod.int.phx2.redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201203191116.32919.vrozenfe@redhat.com> 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 , qemu-devel , Michael Roth , Alon Levy , Paul =?utf-8?q?Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0=94=E7=A9=B6=E7=99=BC?= =?utf-8?q?=E5=B1=95=E9=83=A8?= , spice-devel@lists.freedesktop.org, Alex =?utf-8?q?Huang-=E9=BB=83=E5=BF=85=E8=B3=A2-=E7=A0=94?= =?utf-8?q?=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8?= On Monday, March 19, 2012 08:29:41 AM 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: > Hi Vadim, >=20 > We recently encountered with many issues with new Windows Virio driver > running on Qemu 1.0 and Qemu 1.0.50. My initial investigation was found > that the new Viro driver could not be installed before Qemu 1.0.50. But > my colleague right now can install the new Virio driver on Qemu 1.0. Such > a finding is quite a bit surprise to me. Does Windows refuse to install a new driver or just stuck?=20 >=20 > When we tested the new Virio driver on both Qemu 1.0 and 1.0.50, we found > the Virio driver failed to work after disabling and enabling the driver a > few times. However, the failure case largely depends on the type of > machine. On my machine, I did not see such a problem. Are you running SMP or UP guest? What about others? >=20 > Here are a few of questions that I want to clarify for us. >=20 > 1. Can the new VirIO driver be installed prior Qemu 1.0.50(the current > head branch)?=20 Yes, as far as I know. > 2. Does your QA team verify the new VirtIo driver prior Qemu > 1.0.50? Do you recommend us to do such a test or debugging? Our QA test our drivers on top of RHEL only. I don't know exactly what is the difference between our latest qemu-kvm and upstream >=20 > 3. When we disable and enable the new VirtIO driver several times on > either Qemu 1.0 or Qemu 1.0.50, VirtIo driver failed to work after > enabling the new VirtIO driver. What we found in this particular case is > that the VirtIO driver was blocked inside the DPC routine where the driver > tried to ACK the interrupt. Based on my colleague's observation,=20 the > I/O read from DPC was not trapped by the front-end driver(a Linux driver > implemented for VirtIO)? Do you have any idea why this could happen? Also, > did you find similar issues by you or your QA? I know for sure that we have at least one race condition described here: https://bugzilla.redhat.com/show_bug.cgi?id=3D750773 Hence, my question is whether your guest is SMP or UP?=20 >=20 > Please let us know these as soon as possible since we have a big trouble > to make the Virio driver(new and old driver) work stably in any Qemu > official release including Qemu 1.0.50. I'm going to push some changes, mostly related to the above bug.=20 The DPC problem is completely new for me. Please post your qemu=20 configuration string and I'll try to reproduce it and investigate this prob= lem. Best regards, Vadim. >=20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Wednesday, February 08, 2012 3:47 PM > 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel; Paul Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0= =94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 Subject: Re: > [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > I'm afraid to give you any recommendations regarding QEMU stability. > I usually work with qemu-kvm repository. But we are always doing WHQL > process on RHEL platform only. >=20 > Maybe someone from the SPICE team can comment on your question? >=20 > Best regards, > Vadim. >=20 > ----- Original Message ----- > From: "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" > To: "Vadim Rozenfeld" > Cc: "Michael Roth" , "Stefan Hajnoczi" > , 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" , "Alon Levy" > , "qemu-devel" , "Paul > Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83= =A8" Sent: Wednesday, February 8, 2012 > 4:39:22 AM > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on > Qemu 0.15 >=20 > Vadim, >=20 > Thanks. I tested Windows guest OS driver the over qemu-kvm-devel 1.0.50 > from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git and it worked. The > latest Windows guest driver from (https://github.com/YanVugenfirer/) seems > to have to work with Qemu 1.0.50. My previous test ran over Qemu 1.0 and > that was why it failed to work. >=20 > As you mentioned, the latest driver from > (https://github.com/YanVugenfirer/) is much more stable than the old one. > But those drivers must work with Qemu 1.0.50 which was not verified to be > stable. Do you think Qemu 1.0.50 is stable to be used? Please give us a > recommendation. >=20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Wednesday, February 08, 2012 3:06 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel; Paul Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0= =94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 Subject: Re: > [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > I have tried to reproduce the problem several times without success. >=20 > QEMU: > QEMU 1.0.50 from git://git.qemu.org/qemu.git ,and qemu-kvm-devel 1.0.50 > from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git >=20 > My guest info: > OS Name: Microsoft Windows 7 Enterprise > OS Version: 6.1.7600 N/A Build 7600 >=20 > QEMU command line: > sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 = =2Dm > 1024 -smp 1,sockets=3D1,cores=3D1,threads=3D1 -name SERIAL -uuid > d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=3Dlocaltime > -device > virtio-serial-pci,id=3Dvirtio-serial0,bus=3Dpci.0,multifunction=3Don,addr= =3D0x5.0x > 0 -drive > file=3D/home/vrozenfe/work/images/win7.qcow2,if=3Dnone,id=3Ddrive-ide0-0-= 0,forma > t=3Dqcow2 -device > ide-drive,bus=3Dide.0,unit=3D0,drive=3Ddrive-ide0-0-0,id=3Dide0-0-0,booti= ndex=3D1 > -netdev tap,id=3Dhostnet0 -device > e1000,netdev=3Dhostnet0,id=3Dnet0,mac=3D22:3A:40:3F:2F:12,bus=3Dpci.0,mul= tifunctio > n=3Don,addr=3D0x3.0x0 -chardev pty,id=3Dcharserial0 -device > isa-serial,chardev=3Dcharserial0,id=3Dserial0 -chardev > spicevmc,id=3Dcharchannel0,name=3Dvdagent -device > virtserialport,bus=3Dvirtio-serial0.0,nr=3D1,chardev=3Dcharchannel0,id=3D= channel0, > name=3Dcom.redhat.spice.0 -usb -device usb-tablet,id=3Dinput0 -device > virtio-balloon-pci,id=3Dballoon0,bus=3Dpci.0,multifunction=3Don,addr=3D0x= 4.0x0 > -cdrom /home/vrozenfe/work/virtio-win-1.4.0.iso -snapshot -enable-kvm >=20 > Drivers: > Both, MS signed from RHEL6.2 virtio-win RPM, as well as compiled by myself > with the sources from our internal repository (which contains absolutely > the same code as in Yan's repository). >=20 >=20 >=20 > ----- Original Message ----- > From: "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" > To: "Vadim Rozenfeld" > Cc: "Michael Roth" , "Stefan Hajnoczi" > , 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" , "Alon Levy" > , "qemu-devel" , "Paul > Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83= =A8" Sent: Monday, February 6, 2012 > 3:08:55 PM > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on > Qemu 0.15 >=20 > Vadim, >=20 > I did the same test again today and no luck to made it work. > Let us what you find since we might have missed some points when we did t= he > test. >=20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Sunday, February 05, 2012 2:14 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel; Paul Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0= =94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 Subject: Re: > [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > Thanks, > I'll check this problem. > Vadim. >=20 > ----- Original Message ----- > From: "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" > 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" , "Vadim Rozenfeld" > Cc: "Michael Roth" , > "Stefan Hajnoczi" , 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" , "Alon Levy" > , "qemu-devel" , "Paul > Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0=94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83= =A8" Sent: Saturday, February 4, 2012 > 5:39:26 AM > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on > Qemu 0.15 >=20 > Vadim, >=20 > We tested the free build driver on 32-bit Windows 7 and the symptom was t= he > same. In other words, the latest driver source from > https://github.com/YanVugenfirer/ is buggy and it was not workable at all. >=20 >=20 >=20 > -----Original Message----- > From: 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 > Sent: Friday, February 03, 2012 12:01 PM > To: 'Vadim Rozenfeld' > Cc: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel; Paul Lu-=E7=9B=A7=E5=81=89=E6=99=BA-=E7=A0= =94=E7=A9=B6=E7=99=BC=E5=B1=95=E9=83=A8 Subject: RE: > [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > Vadim, >=20 > I downloaded the latest Windows guest driver code from > (https://github.com/YanVugenfirer/) and built the test binary driver code. > When I tested the release build Vioserial driver on 64-bit Windows 7, the > driver seemed to wait for something to happen and the update driver > Windows dialog simply just stayed in busy state. Finally, the Windows > system entered a busy loop. However, if I tested the debugging build > driver, the driver could be installed. But it took for a long time to > complete. >=20 > Our installed Qemu is 1.0. Is there Qemu build requirement so that we can > verify the vioserial driver? From my test, the latest code from > (https://github.com/YanVugenfirer/) seemed to be worst than the one we > tested before. Let me know if we did anything wrong. >=20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Friday, January 20, 2012 8:48 PM > 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel Subject: Re: [Qemu-devel] > [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > This code is slightly buggy. > Please try Yan's repository > at github (https://github.com/YanVugenfirer/). > I believe that the most critical changes have been merged already by Yan > into this public repository. I will ask to update binaries and sources at > fedoraproject site as well. >=20 > Best regards, > Vadim. >=20 >=20 > ----- Original Message ----- > From: "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" > To: "Vadim Rozenfeld" > Cc: "Michael Roth" , "Stefan Hajnoczi" > , 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" , "Alon Levy" > , "qemu-devel" Sent: Friday, > January 20, 2012 3:25:51 AM > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on > Qemu 0.15 >=20 > Vadim, >=20 > We downloaded the driver source from the following website. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > wget --no-check-certificate > https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio- > win-prewhql-0.1-15-sources.zip >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Thursday, January 19, 2012 8:25 PM > 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel Subject: Re: [Qemu-devel] > [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > Just to be sure that we are on the same page: > could you tell me about the origin of the source? > Is it the latest from the Yan's repository at github.com? >=20 > ----- Original Message ----- > From: "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" > To: "Vadim Rozenfeld" > Cc: "Michael Roth" , "Stefan Hajnoczi" > , 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" , "Alon Levy" > , "qemu-devel" Sent: Thursday, > January 19, 2012 12:06:16 PM > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on > Qemu 0.15 >=20 > Vadim, >=20 > We built it from the driver source. Up to this moment, we always use the > same binary to test Qemu. >=20 >=20 > -----Original Message----- > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > Sent: Thursday, January 19, 2012 5:39 PM > 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel Subject: RE: [Qemu-devel] > [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15 >=20 > On Thu, 2012-01-19 at 16:33 +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 > > It is SMP system. >=20 > What about vioserial driver itself? > did you build it from sources or is > it one, available through RHEL channels? >=20 > > -----Original Message----- > > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > > Sent: Thursday, January 19, 2012 3:58 PM > > 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: Michael Roth; Stefan Hajnoczi; 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; Alon Levy; qemu-devel > > Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS > > on Qemu 0.15 > >=20 > > On Thu, 2012-01-19 at 09:41 +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 tested on Qemu 1.0.50. and found the VioSerial driver had problem to > > > install on 64-bit Win7 guest. During the driver installation, the > > > system hung after the driver being installed. After I rebooted the > > > guest OS, the Vioserial driver work. The hang system seemed to be > > > found only during the driver installation. > >=20 > > On UP or SMP system? > >=20 > > > -----Original Message----- > > > From: Vadim Rozenfeld [mailto:vrozenfe@redhat.com] > > > Sent: Wednesday, January 18, 2012 4:57 AM > > > To: Michael Roth > > > Cc: 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; Stefan Hajnoczi; > > > 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; Alon Levy; > > > qemu-devel > > > Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest > > > OS on Qemu 0.15 > > >=20 > > > On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote: > > > > On 01/15/2012 08:02 PM, 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 > > > > > Thank you for your prompt reply. Here are the information for our > > > > > test case. > > > > >=20 > > > > >=20 > > > > > 1) we use the following command line to launch the guest OS > > > > >=20 > > > > >=20 > > > > > /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp > > > > > 1,sockets=3D1,cores=3D1,threads=3D1 -name win_xp -uuid > > > > > d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults > > > > > -chardev > > > > > socket,id=3Dcharmonitor,path=3D/var/lib/libvirt/qemu/win_xp.monit= or, > > > > > se rv er,nowait -mon > > > > > chardev=3Dcharmonitor,id=3Dmonitor,mode=3Dreadline > > > > > -rtc base=3Dlocaltime > > > > > -device > > > > > virtio-serial-pci,id=3Dvirtio-serial0,bus=3Dpci.0,multifunction= =3Don,a > > > > > dd > > > > > r=3D > > > > > 0x5.0x0 -drive > > > > > file=3D/media/Images/Windows-XP.img,if=3Dnone,id=3Ddrive-ide0-0-0= ,form > > > > > at > > > > > =3Dr > > > > > aw -device > > > > > ide-drive,bus=3Dide.0,unit=3D0,drive=3Ddrive-ide0-0-0,id=3Dide0-0= =2D0,boot > > > > > in > > > > > de > > > > > x=3D1 > > > > > -netdev tap,fd=3D17,id=3Dhostnet0 > > > > > -device > > > > > rtl8139,netdev=3Dhostnet0,id=3Dnet0,mac=3D52:54:00:e8:dc:b1,bus= =3Dpci.0, > > > > > mu > > > > > lt > > > > > ifunction=3Don,addr=3D0x3.0x0 > > > > > -chardev pty,id=3Dcharserial0 > > > > > -device isa-serial,chardev=3Dcharserial0,id=3Dserial0 > > > > > -chardev spicevmc,id=3Dcharchannel0,name=3Dvdagent > > > > > -device > > > > > virtserialport,bus=3Dvirtio-serial0.0,nr=3D1,chardev=3Dcharchanne= l0,id > > > > > =3Dc > > > > > ha > > > > > nnel0,name=3Dcom.redhat.spice.0 > > > > > -usb -device usb-tablet,id=3Dinput0 -spice > > > > > port=3D5900,addr=3D0.0.0.0,disable-ticketing > > > > > -vga qxl -global qxl-vga.vram_size=3D67108864 -device > > > > > virtio-balloon-pci,id=3Dballoon0,bus=3Dpci.0,multifunction=3Don,a= ddr=3D0 > > > > > x4 > > > > > .0 > > > > > x0 > > > > >=20 > > > > >=20 > > > > >=20 > > > > > 2). In Guest Windows XP OS > > > > >=20 > > > > >=20 > > > > > When the following callback function of the vioserial device is > > > > > called in guest OS. The allocated resources is empty. > > > > >=20 > > > > >=20 > > > > > VIOSerialEvtDevicePrepareHardware() ---This function is to get the > > > > > I/O address of the vioserial device and map the physical address > > > > > to the logical address space. > > > > >=20 > > > > > I added the following trace and the value of nListSize is ZERO. > > > > > TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, "%s > > > > > (nListSize=3D%d)\n", __FUNCTION__,nListSize); > > > > >=20 > > > > >=20 > > > > > So far, we have tested Qemu 0.14 without any problem but Qemu 0.15 > > > > > seemed to be broken in vioserial device. Let me know if you need > > > > > further information. Thanks. > > > >=20 > > > > Hi Charles, > > > >=20 > > > > What versions of the virtio-win drivers are you using? > > > >=20 > > > > I've been testing virtio-serial on windows using the latest > > > > qemu.git (1.0). Linux guests work fine, but I've been having > > > > various issues with Windows 7, XP SP3, and Server 2008 R1. XP SP3 > > >=20 > > > > works intermittently for me using RHEL6.0 virtio-win, as well as th= e=20 drivers at: > > > I have seen some virtio serial port initialization problems on 1.0.50. > > > Will try to look into this problem in the following week(s). > > >=20 > > > > http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ > > > >=20 > > > > But I've been getting a mix of issues such as guest hangs, > > > > vioser-test failing to enumerate any virtio-serial devices, or > > > > various non-critical error messages from qemu that seem to > > > > coincide with the channel being open/closed (occasionally resulting > > > > in the channel becoming unresponsive). > > > >=20 > > > > Do any of these seem similar to the behaviour you're seeing? If so > > > > I'll see if the issues go away on 0.14.0 and follow-up with a git > > > > bisect.