subject:"\[Qemu\-devel\] \[Spice\-devel\] Vioserial of Windows guest OS on Qemu 0.15"

On Monday, March 19, 2012 08:29:41 AM Charles.Tsai-蔡清海-研究發展部 wrote:
Hi Vadim,

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?

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?

Here are a few of questions that I want to clarify for us.

1. Can the new VirIO driver be installed prior Qemu 1.0.50(the current
head branch)?
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

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,
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=750773
Hence, my question is whether your guest is SMP or UP?

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.
The DPC problem is completely new for me. Please post your qemu
configuration string and I'll try to reproduce it and investigate this problem.

Best regards,
Vadim.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Wednesday, February 08, 2012 3:47 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部 Subject: Re:
[Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

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.

Maybe someone from the SPICE team can comment on your question?

Best regards,
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex
Huang-黃必賢-研究發展部 alex.hu...@cloudena.com, Alon Levy
al...@redhat.com, qemu-devel qemu-devel@nongnu.org, Paul
Lu-盧偉智-研究發展部 paul...@cloudena.com Sent: Wednesday, February 8, 2012
4:39:22 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on
Qemu 0.15

Vadim,

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.

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.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Wednesday, February 08, 2012 3:06 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部 Subject: Re:
[Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

I have tried to reproduce the problem several times without success.

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

My guest info:
OS Name: Microsoft Windows 7 Enterprise
OS Version:6.1.7600 N/A Build 7600

QEMU command line

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-03-19 Thread Christophe Fergeau

Hey,

On Mon, Mar 19, 2012 at 02:29:41PM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
   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.

For what it's worth, Alon Levy also hit this particular bug a few months
ago, and I successfully reproduced at that time. I think I reported it to
Vadim back in the days, but I'm not 100% sure :)

Christophe


pgpxQ20RMnnkg.pgp
Description: PGP signature

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

On Monday, March 19, 2012 12:12:59 PM Christophe Fergeau wrote:
 Hey,
 
 On Mon, Mar 19, 2012 at 02:29:41PM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  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.
 
 For what it's worth, Alon Levy also hit this particular bug a few months
 ago, and I successfully reproduced at that time. I think I reported it to
 Vadim back in the days, but I'm not 100% sure :)
 
 Christophe
Thanks Christophe.
In your case (https://bugzilla.redhat.com/show_bug.cgi?id=750773)
an UP system hangs on shutdown. 
I'm not sure whether Charles is hitting the same problem.

Best,
Vadim.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-03-19 Thread Christophe Fergeau

On Mon, Mar 19, 2012 at 01:42:21PM +0200, Vadim Rozenfeld wrote:
 On Monday, March 19, 2012 12:12:59 PM Christophe Fergeau wrote:
  Hey,
  
  On Mon, Mar 19, 2012 at 02:29:41PM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 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.
  
  For what it's worth, Alon Levy also hit this particular bug a few months
  ago, and I successfully reproduced at that time. I think I reported it to
  Vadim back in the days, but I'm not 100% sure :)
  
  Christophe
 Thanks Christophe.
 In your case (https://bugzilla.redhat.com/show_bug.cgi?id=750773)
 an UP system hangs on shutdown. 

In my case, the hang was during boot even though it magically went away
sometimes in the last month

 I'm not sure whether Charles is hitting the same problem.

While trying to figure out what was going on with the bug above, I've
definitely hit a enabling/disabling vioserial in the device manager 3
times causes the VM to freeze bug.
For what it's worth, lately I've also been experiencing VM freezes when
installing vioserial in winxp or win7 UP VMs

Christophe


pgpHSgu7prD1B.pgp
Description: PGP signature

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

On Monday, March 19, 2012 01:56:03 PM Christophe Fergeau wrote:
 On Mon, Mar 19, 2012 at 01:42:21PM +0200, Vadim Rozenfeld wrote:
  On Monday, March 19, 2012 12:12:59 PM Christophe Fergeau wrote:
   Hey,
   
   On Mon, Mar 19, 2012 at 02:29:41PM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
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.
   
   For what it's worth, Alon Levy also hit this particular bug a few
   months ago, and I successfully reproduced at that time. I think I
   reported it to Vadim back in the days, but I'm not 100% sure :)
   
   Christophe
  
  Thanks Christophe.
  In your case (https://bugzilla.redhat.com/show_bug.cgi?id=750773)
  an UP system hangs on shutdown.
 
 In my case, the hang was during boot even though it magically went away
 sometimes in the last month
 
  I'm not sure whether Charles is hitting the same problem.
 
 While trying to figure out what was going on with the bug above, I've
 definitely hit a enabling/disabling vioserial in the device manager 3
 times causes the VM to freeze bug.
 For what it's worth, lately I've also been experiencing VM freezes when
 installing vioserial in winxp or win7 UP VMs
OK. It looks like the same race condition, which I'm going to fix. 
 
 Christophe

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Christophe,

Great!, we finally are at the same page.

-Original Message-
From: Christophe Fergeau [mailto:cferg...@redhat.com] 
Sent: Monday, March 19, 2012 6:13 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; qemu-devel; Michael Roth; Paul Lu-盧偉智-研究發展部; 
spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部
Subject: Re: [Spice-devel] [Qemu-devel] Vioserial of Windows guest OS on Qemu 
0.15

Hey,

On Mon, Mar 19, 2012 at 02:29:41PM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
   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.

For what it's worth, Alon Levy also hit this particular bug a few months ago, 
and I successfully reproduced at that time. I think I reported it to Vadim back 
in the days, but I'm not 100% sure :)

Christophe

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

My colleague will give you more  information we found here.
Qemu somehow in this particular case returns a wrong bar0 value.
In working case, the bar0 is 0xc140. But in failure case, the bar0 is changed 
to 0xC141.



-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Monday, March 19, 2012 8:03 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Monday, March 19, 2012 01:16:56 PM Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 What do you mean qemu configuration string? Is it the build 
 configuration or command line option? Please let me know it. Thanks.
 
 
Sorry, that was ambiguous.
I need the command line in order to reproduce the problem.

Cheers,
Vadim.

 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Monday, March 19, 2012 5:17 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; 
 Alex
 Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部 Subject: Re:
 [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
 On Monday, March 19, 2012 08:29:41 AM Charles.Tsai-蔡清海-研究發展部 wrote:
  Hi Vadim,
  
  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?
 
  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?
 
  Here are a few of questions that I want to clarify for us.
  
  1. Can the new VirIO driver be installed prior Qemu 1.0.50(the
  
  current head branch)?
 
 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
 
  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,
 
 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=750773
 Hence, my question is whether your guest is SMP or UP?
 
  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.
 The DPC problem is completely new for me. Please post your qemu 
 configuration string and I'll try to reproduce it and investigate this 
 problem.
 
 Best regards,
 Vadim.
 
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, February 08, 2012 3:47 PM
  To: Charles.Tsai-蔡清海-研究發展部
  Cc: Michael Roth; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org;
  Alex
  Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部 Subject: Re:
  [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
  0.15
  
  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.
  
  Maybe someone from the SPICE team can comment on your question?
  
  Best regards,
  Vadim.
  
  - Original Message -
  From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
  To: Vadim Rozenfeld vroze...@redhat.com
  Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi
  stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex
  Huang-黃必賢-研究發展部 alex.hu...@cloudena.com, Alon Levy
  al...@redhat.com, qemu-devel qemu-devel@nongnu.org, Paul
  Lu-盧偉智-研究發展部 paul...@cloudena.com Sent: Wednesday, February 8, 
  2012
  4:39:22 AM
  Subject: RE: [Qemu-devel] [Spice-devel] Vioserial

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Hi Vadim,

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.

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.

Here are a few of questions that I want to clarify for us.

1. Can the new VirIO driver be installed prior Qemu 1.0.50(the current 
head branch)?
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?

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, 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 youfind 
similar issues by you or your QA?

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Wednesday, February 08, 2012 3:47 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Maybe someone from the SPICE team can comment on your question?

Best regards,
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Wednesday, February 8, 2012 4:39:22 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Wednesday, February 08, 2012 3:06 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

I have tried to reproduce the problem several times without success.

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

My guest info:
OS Name:   Microsoft Windows 7 Enterprise 
OS Version:6.1.7600 N/A Build 7600

QEMU command line:
sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -m 
1024 -smp 1,sockets=1,cores=1,threads=1 -name SERIAL -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=localtime -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0 
-drive 
file=/home/vrozenfe/work/images/win7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2
 -device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev 
tap,id=hostnet0 -device 
e1000,netdev=hostnet0,id=net0,mac=22:3A:40:3F:2F:12,bus=pci.0,multifunction=on,addr=0x3.0x0
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

What do you mean qemu configuration string? Is it the build configuration or 
command line option?
Please let me know it. Thanks.




-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Monday, March 19, 2012 5:17 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Monday, March 19, 2012 08:29:41 AM Charles.Tsai-蔡清海-研究發展部 wrote:
 Hi Vadim,
 
   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? 
 
   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?
 
   Here are a few of questions that I want to clarify for us.
 
   1. Can the new VirIO driver be installed prior Qemu 1.0.50(the 
 current head branch)?
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
 
   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, 
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=750773
Hence, my question is whether your guest is SMP or UP? 
 
   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. 
The DPC problem is completely new for me. Please post your qemu configuration 
string and I'll try to reproduce it and investigate this problem.

Best regards,
Vadim.
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Wednesday, February 08, 2012 3:47 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; 
 Alex
 Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部 Subject: Re:
 [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
 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.
 
 Maybe someone from the SPICE team can comment on your question?
 
 Best regards,
 Vadim.
 
 - Original Message -
 From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
 To: Vadim Rozenfeld vroze...@redhat.com
 Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi
 stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex
 Huang-黃必賢-研究發展部 alex.hu...@cloudena.com, Alon Levy
 al...@redhat.com, qemu-devel qemu-devel@nongnu.org, Paul
 Lu-盧偉智-研究發展部 paul...@cloudena.com Sent: Wednesday, February 8, 2012
 4:39:22 AM
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15
 
 Vadim,
 
 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.
 
 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.
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Wednesday, February 08, 2012 3:06 AM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-07 Thread Charles . Tsai-蔡清海-研究發展部

On Monday, March 19, 2012 02:48:43 PM Paul Lu-???-? wrote:
 Hi Vadim,
 Here is the configuration:
 /usr/local/bin/qemu-system-x86_64 \
  -localtime \
  -boot order=c,menu=on \
  -drive file=/var/lib/libvirt/images/xxx.img \
  -vga qxl \
  -cdrom /home/paul/Downloads/ISO/virtio-win-0.1-15.iso \
  -chardev spicevmc,id=vdagent,name=vdagent \
  -spice port=5930,disable-ticketing \
  -device virtio-serial-pci \
  -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 \
  -smp 1,cores=1 -m 2048 \
  -enable-kvm \
  -usbdevice tablet \
  -net nic -net user \
  -tb-size 0 \
  -qmp tcp:localhost:,nowait,server \
  -D /home/paul/MyQemuLog/xxx/xxx.log \
  -trace events=/home/paul/MyTestCase/xxx/events
 
 QEMU Version: qemu-kvm commit 30c044521889195f54a9f2c21310894f545994e8
 
 
 I use qmp command, query-pci, to check virtio-serial-pci BAR0. It shows
 0xC140. However, pci_default_read_config in pci.c return 0xC141 to Guest.
 We also trace pci_default_wirte_config.
 
 At some point, the BAR0 will be overwritten to 0xC141. Here is the result,
 
 virtio_set_status vdev 0x7fbeaba594a0 val 0
 virtio_set_status vdev 0x7fbeaba594a0 val 0
 qemu-system-x86_64: 10:1,len=4
 qemu-system-x86_64: [WRITE]10:, len=4
 qemu-system-x86_64: 10:ffe1,len=4
 qemu-system-x86_64: [WRITE]10:1, len=4
 qemu-system-x86_64: [WRITE]10:c140, len=4
 virtio_set_status vdev 0x7fbeaba594a0 val 0
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 virtio_set_status vdev 0x7fbeaba594a0 val 0
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: [WRITE]10:, len=4
 qemu-system-x86_64: 10:ffe1,len=4
 qemu-system-x86_64: [WRITE]10:c141, len=4
 virtio_set_status vdev 0x7fbeaba594a0 val 0
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 qemu-system-x86_64: 10:c141,len=4
 
 I think the following code in pci_default_wirte_config cause the problem,
for (i = 0; i  l; val = 8, ++i) {
 uint8_t wmask = d-wmask[addr + i];
 uint8_t w1cmask = d-w1cmask[addr + i];
 assert(!(wmask  w1cmask));
 d-config[addr + i] = (d-config[addr + i]  ~wmask) | (val 
 wmask); d-config[addr + i] = ~(val  w1cmask); /* W1C: Write 1 to Clear
 */ }
 
 Could you elaborate it for us?
 
Hi Paul,
Give me a couple of days.
Best,
Vadim.
 
 Best Regards,
 Paul
 
 -Original Message-
 From: Charles.Tsai-???-?
 Sent: Mon 3/19/2012 8:32 PM
 To: Vadim Rozenfeld
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
 Huang-???-?; Alon Levy; qemu-devel; Paul Lu-???-? Subject: RE:
 [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
 Vadim,
 
 My colleague will give you more  information we found here.
 Qemu somehow in this particular case returns a wrong bar0 value.
 In working case, the bar0 is 0xc140. But in failure case, the bar0 is
 changed to 0xC141.
 
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Monday, March 19, 2012 8:03 PM
 To: Charles.Tsai-???-?
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
 Huang-???-?; Alon Levy; qemu-devel; Paul Lu-???-? Subject: Re:
 [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
 On Monday, March 19, 2012 01:16:56 PM Charles.Tsai-???-? wrote:
  Vadim,
  
  What do you mean qemu configuration string? Is it the build
  configuration or command line option? Please let me know it. Thanks.
 
 Sorry, that was ambiguous.
 I need the command line in order to reproduce the problem.
 
 Cheers,
 Vadim.
 
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Monday, March 19, 2012 5:17 PM
  To: Charles.Tsai-???-?
  Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
  Alex
  Huang-???-?; Alon Levy; qemu-devel; Paul Lu-???-? Subject: Re:
  [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
  
  On Monday, March 19, 2012 08:29:41 AM Charles.Tsai-???-? wrote:
   Hi Vadim,
   
 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?
  
 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?
  
 Here are a few of questions that I want

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-08 Thread David Jaša

Vadim Rozenfeld píše v St 08. 02. 2012 v 02:47 -0500:
 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.
 
 Maybe someone from the SPICE team can comment on your question?
 

We also focus our testing on RHEL components. We have done some new
feature testing on Fedora with virt-preview repo:
http://repos.fedorapeople.org/repos/jforbes/virt-preview/
but it still says nothing about qemu stability for your purposes and the
qemu version is still 1.0.

David

 Best regards,
 Vadim.
 
 - Original Message -
 From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
 To: Vadim Rozenfeld vroze...@redhat.com
 Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
 stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex 
 Huang-黃必賢-研究發展部 alex.hu...@cloudena.com, Alon Levy al...@redhat.com, 
 qemu-devel qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 
 paul...@cloudena.com
 Sent: Wednesday, February 8, 2012 4:39:22 AM
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 Vadim,
 
 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.
 
 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.
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
 Sent: Wednesday, February 08, 2012 3:06 AM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
 Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
 Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 I have tried to reproduce the problem several times without success.
 
 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
 
 My guest info:
 OS Name:   Microsoft Windows 7 Enterprise 
 OS Version:6.1.7600 N/A Build 7600
 
 QEMU command line:
 sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -m 
 1024 -smp 1,sockets=1,cores=1,threads=1 -name SERIAL -uuid 
 d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=localtime 
 -device 
 virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0 
 -drive 
 file=/home/vrozenfe/work/images/win7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2
  -device 
 ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 
 -netdev tap,id=hostnet0 -device 
 e1000,netdev=hostnet0,id=net0,mac=22:3A:40:3F:2F:12,bus=pci.0,multifunction=on,addr=0x3.0x0
  -chardev pty,id=charserial0 -device 
 isa-serial,chardev=charserial0,id=serial0 -chardev 
 spicevmc,id=charchannel0,name=vdagent -device 
 virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
  -usb -device usb-tablet,id=input0 -device 
 virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0 -cdrom 
 /home/vrozenfe/work/virtio-win-1.4.0.iso -snapshot -enable-kvm
 
 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). 
 
 
 
 - Original Message -
 From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
 To: Vadim Rozenfeld vroze...@redhat.com
 Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
 stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex 
 Huang-黃必賢-研究發展部 alex.hu...@cloudena.com, Alon Levy al...@redhat.com, 
 qemu-devel qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 
 paul...@cloudena.com
 Sent: Monday, February 6, 2012 3:08:55 PM
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 Vadim,
 
 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 the 
 test.
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Sunday, February 05, 2012 2:14 AM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
 Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
 Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 Thanks,
 I'll check this problem.
 Vadim.
 
 - Original Message -
 From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
 To: Charles.Tsai-蔡清海-研究發展部 charles.t

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-07 Thread Vadim Rozenfeld

I have tried to reproduce the problem several times without success.

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

My guest info:
OS Name:   Microsoft Windows 7 Enterprise
OS Version:6.1.7600 N/A Build 7600

QEMU command line:
sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -m 
1024 -smp 1,sockets=1,cores=1,threads=1 -name SERIAL -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=localtime -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0 
-drive 
file=/home/vrozenfe/work/images/win7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2
 -device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev 
tap,id=hostnet0 -device 
e1000,netdev=hostnet0,id=net0,mac=22:3A:40:3F:2F:12,bus=pci.0,multifunction=on,addr=0x3.0x0
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -usb -device usb-tablet,id=input0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0 -cdrom 
/home/vrozenfe/work/virtio-win-1.4.0.iso -snapshot -enable-kvm

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).



- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Monday, February 6, 2012 3:08:55 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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 the 
test.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Sunday, February 05, 2012 2:14 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Thanks,
I'll check this problem.
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com, Vadim Rozenfeld 
vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Saturday, February 4, 2012 5:39:26 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We tested the free build driver on 32-bit Windows 7 and the symptom was the 
same. In other words, the latest driver source from 
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.



-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February 03, 2012 12:01 PM
To: 'Vadim Rozenfeld'
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

This code is slightly buggy.
Please try Yan's repository
at github (https://github.com/YanVugenfirer/).
I believe

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Wednesday, February 08, 2012 3:06 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

I have tried to reproduce the problem several times without success.

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

My guest info:
OS Name:   Microsoft Windows 7 Enterprise 
OS Version:6.1.7600 N/A Build 7600

QEMU command line:
sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -m 
1024 -smp 1,sockets=1,cores=1,threads=1 -name SERIAL -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=localtime -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0 
-drive 
file=/home/vrozenfe/work/images/win7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2
 -device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev 
tap,id=hostnet0 -device 
e1000,netdev=hostnet0,id=net0,mac=22:3A:40:3F:2F:12,bus=pci.0,multifunction=on,addr=0x3.0x0
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -usb -device usb-tablet,id=input0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0 -cdrom 
/home/vrozenfe/work/virtio-win-1.4.0.iso -snapshot -enable-kvm

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). 



- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Monday, February 6, 2012 3:08:55 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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 the 
test.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Sunday, February 05, 2012 2:14 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Thanks,
I'll check this problem.
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com, Vadim Rozenfeld 
vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Saturday, February 4, 2012 5:39:26 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We tested the free build driver on 32-bit Windows 7 and the symptom was the 
same. In other words, the latest driver source from 
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.



-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February 03, 2012 12:01 PM
To: 'Vadim Rozenfeld'
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-07 Thread Vadim Rozenfeld

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.

Maybe someone from the SPICE team can comment on your question?

Best regards,
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Wednesday, February 8, 2012 4:39:22 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Wednesday, February 08, 2012 3:06 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

I have tried to reproduce the problem several times without success.

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

My guest info:
OS Name:   Microsoft Windows 7 Enterprise
OS Version:6.1.7600 N/A Build 7600

QEMU command line:
sudo /home/vrozenfe/work/upstream/qemu/x86_64-softmmu/qemu-system-x86_64 -m 
1024 -smp 1,sockets=1,cores=1,threads=1 -name SERIAL -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -monitor stdio -rtc base=localtime -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0 
-drive 
file=/home/vrozenfe/work/images/win7.qcow2,if=none,id=drive-ide0-0-0,format=qcow2
 -device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev 
tap,id=hostnet0 -device 
e1000,netdev=hostnet0,id=net0,mac=22:3A:40:3F:2F:12,bus=pci.0,multifunction=on,addr=0x3.0x0
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -usb -device usb-tablet,id=input0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0 -cdrom 
/home/vrozenfe/work/virtio-win-1.4.0.iso -snapshot -enable-kvm

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).



- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Monday, February 6, 2012 3:08:55 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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 the 
test.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Sunday, February 05, 2012 2:14 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Thanks,
I'll check this problem.
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com, Vadim Rozenfeld 
vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Saturday, February 4, 2012 5:39:26 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We tested

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-06 Thread Charles . Tsai-蔡清海-研究發展部

Vadim,

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 the 
test.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Sunday, February 05, 2012 2:14 AM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Thanks,
I'll check this problem.
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com, Vadim Rozenfeld 
vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Saturday, February 4, 2012 5:39:26 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We tested the free build driver on 32-bit Windows 7 and the symptom was the 
same. In other words, the latest driver source from 
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.



-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February 03, 2012 12:01 PM
To: 'Vadim Rozenfeld'
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Best regards,
Vadim. 
  

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-04 Thread Vadim Rozenfeld

Thanks,
I'll check this problem.
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com, Vadim Rozenfeld 
vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org, Paul Lu-盧偉智-研究發展部 paul...@cloudena.com
Sent: Saturday, February 4, 2012 5:39:26 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We tested the free build driver on 32-bit Windows 7 and the symptom was the 
same. In other words, the latest driver source from 
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.

-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February 03, 2012 12:01 PM
To: 'Vadim Rozenfeld'
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Best regards,
Vadim.

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 It is SMP system.
What about vioserial driver itself?
did you build it from sources or is
it one, available through RHEL channels?

 -Original Message

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-03 Thread Charles . Tsai-蔡清海-研究發展部

Vadim,

We tested the free build driver on 32-bit Windows 7 and the symptom was the 
same. In other words, the latest driver source from 
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.



-Original Message-
From: Charles.Tsai-蔡清海-研究發展部 
Sent: Friday, February 03, 2012 12:01 PM
To: 'Vadim Rozenfeld'
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel; Paul Lu-盧偉智-研究發展部
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Best regards,
Vadim. 
  

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15
 
 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  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

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-02-02 Thread Charles . Tsai-蔡清海-研究發展部

Vadim,

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.

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Best regards,
Vadim. 
  

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15
 
 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  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.
  
 On UP or SMP system?
  
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest 
  OS on Qemu 0.15
  
  On Mon, 2012-01-16 at 19:50

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-23 Thread Charles . Tsai-蔡清海-研究發展部

Vadim,

Thanks. We will download the code from Yan's repository.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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.

Best regards,
Vadim. 
  

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15
 
 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  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.
  
 On UP or SMP system?
  
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest 
  OS on Qemu 0.15
  
  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,
   
Thank you for your prompt reply. Here are the information for our test 
case.
   
   
1) we use the following command line to launch the guest OS
   
   
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,
se rv er,nowait -mon
chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,a
dd

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-20 Thread Vadim Rozenfeld

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.

Best regards,
Vadim.


- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Friday, January 20, 2012 3:25:51 AM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 It is SMP system.
What about vioserial driver itself?
did you build it from sources or is
it one, available through RHEL channels?


 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS
 on Qemu 0.15

 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
 
  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.
 
 On UP or SMP system?
 
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi;
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy;
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest
  OS on Qemu 0.15
 
  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,
   
Thank you for your prompt reply. Here are the information for our test 
case.
   
   
1) we use the following command line to launch the guest OS
   
   
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,
se rv er,nowait -mon
chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,a
dd
r=
0x5.0x0 -drive
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,form
at
=r
aw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,boot
in
de
x=1
-netdev tap,fd=17,id=hostnet0
-device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,
mu
lt
ifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

It is SMP system.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Thursday, January 19, 2012 3:58 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 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.

On UP or SMP system?

 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Wednesday, January 18, 2012 4:57 AM
 To: Michael Roth
 Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
 spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
 qemu-devel
 Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15

 On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
  On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
   Vadim,

   Thank you for your prompt reply. Here are the information for our test 
   case.

   1) we use the following command line to launch the guest OS

   /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
   1,sockets=1,cores=1,threads=1 -name win_xp -uuid
   d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
   -chardev 
   socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,se
   rv er,nowait -mon chardev=charmonitor,id=monitor,mode=readline
   -rtc base=localtime
   -device
   virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,add
   r=
   0x5.0x0 -drive
   file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format
   =r
   aw -device
   ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootin
   de
   x=1
   -netdev tap,fd=17,id=hostnet0
   -device
   rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,mu
   lt
   ifunction=on,addr=0x3.0x0
   -chardev pty,id=charserial0
   -device isa-serial,chardev=charserial0,id=serial0
   -chardev spicevmc,id=charchannel0,name=vdagent
   -device
   virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=c
   ha
   nnel0,name=com.redhat.spice.0
   -usb -device usb-tablet,id=input0
   -spice port=5900,addr=0.0.0.0,disable-ticketing
   -vga qxl -global qxl-vga.vram_size=67108864 -device
   virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4
   .0
   x0

   2). In Guest Windows XP OS

   When the following callback function of the vioserial device  is called 
   in guest OS. The allocated resources is empty.

   VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
   address of the vioserial device and map the physical address to the 
   logical address space.

   I added the following trace and the value of nListSize is ZERO.
   TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s 
   (nListSize=%d)\n, __FUNCTION__,nListSize);

   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.

  Hi Charles,

  What versions of the virtio-win drivers are you using?

  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 works 
  intermittently for me using RHEL6.0 virtio-win, as well as the 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).

  http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

  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).

  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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-19 Thread Vadim Rozenfeld

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
 Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  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.
  
 On UP or SMP system?
  
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
  on Qemu 0.15
  
  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,
   
Thank you for your prompt reply. Here are the information for our test 
case.
   
   
1) we use the following command line to launch the guest OS
   
   
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,se
rv er,nowait -mon chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,add
r=
0x5.0x0 -drive
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format
=r
aw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootin
de
x=1
-netdev tap,fd=17,id=hostnet0
-device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,mu
lt
ifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=c
ha
nnel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0
-spice port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4
.0
x0
   
   
   
2). In Guest Windows XP OS
   
   
When the following callback function of the vioserial device  is called 
in guest OS. The allocated resources is empty.
   
   
VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
address of the vioserial device and map the physical address to the 
logical address space.
   
I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s 
(nListSize=%d)\n, __FUNCTION__,nListSize);
   
   
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.
   
   
   Hi Charles,
   
   What versions of the virtio-win drivers are you using?
   
   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 works 
   intermittently for me using RHEL6.0 virtio-win, as well as the 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).
  
   http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
   
   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).
   
   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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; 
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15

 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,

  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.

 On UP or SMP system?

  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest 
  OS on Qemu 0.15

  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,

Thank you for your prompt reply. Here are the information for our test 
case.

1) we use the following command line to launch the guest OS

/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,
se rv er,nowait -mon 
chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,a
dd
r=
0x5.0x0 -drive
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,form
at
=r
aw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,boot
in
de
x=1
-netdev tap,fd=17,id=hostnet0
-device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,
mu
lt
ifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id
=c
ha
nnel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0 -spice 
port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0
x4
.0
x0

2). In Guest Windows XP OS

When the following callback function of the vioserial device  is called 
in guest OS. The allocated resources is empty.

VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
address of the vioserial device and map the physical address to the 
logical address space.

I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s 
(nListSize=%d)\n, __FUNCTION__,nListSize);

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.

   Hi Charles,

   What versions of the virtio-win drivers are you using?

   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 
   works intermittently for me using RHEL6.0 virtio-win, as well as the 
   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).

   http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

   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

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-19 Thread Stefan Hajnoczi

On Thu, Jan 19, 2012 at 09:41:15AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 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.

If you need to reproduce the installation hang I suggest using qemu
-snapshot or qemu -drive ...,snapshot=on.  These options prevent changes
made by the guest to the disk image from being permanent.

Once you terminate QEMU the changes will be gone and your disk image
will be unchanged - useful for repeatedly testing these types of issues!

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-19 Thread Alon Levy

On Thu, Jan 19, 2012 at 08:09:57AM +, Stefan Hajnoczi wrote:
 On Thu, Jan 19, 2012 at 09:41:15AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  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.
 
 If you need to reproduce the installation hang I suggest using qemu
 -snapshot or qemu -drive ...,snapshot=on.  These options prevent changes
 made by the guest to the disk image from being permanent.
 
 Once you terminate QEMU the changes will be gone and your disk image
 will be unchanged - useful for repeatedly testing these types of issues!
 

There is an additional trick I use, if you add -no-shutdown then if
you find yourself wanting to save the changes anyway (say you started
with -snapshot but decided you want to keep the changes you have done),
which you can do with commit virtio0 or commit ide0 (depending on
the block device), it will allow you to do the commit after you shutdown
the guest, which is easier then trying to get it to unmount the disks.

 Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-19 Thread Vadim Rozenfeld

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 It is SMP system.
What about vioserial driver itself?
did you build it from sources or is
it one, available through RHEL channels?

 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS
 on Qemu 0.15

 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,

  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.

 On UP or SMP system?

  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi;
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy;
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest
  OS on Qemu 0.15

  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,

Thank you for your prompt reply. Here are the information for our test 
case.

1) we use the following command line to launch the guest OS

/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,
se rv er,nowait -mon
chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,a
dd
r=
0x5.0x0 -drive
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,form
at
=r
aw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,boot
in
de
x=1
-netdev tap,fd=17,id=hostnet0
-device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,
mu
lt
ifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id
=c
ha
nnel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0 -spice
port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0
x4
.0
x0

2). In Guest Windows XP OS

When the following callback function of the vioserial device  is called 
in guest OS. The allocated resources is empty.

VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
address of the vioserial device and map the physical address to the 
logical address space.

I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s
(nListSize=%d)\n, __FUNCTION__,nListSize);

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.

   Hi Charles,

   What versions of the virtio-win drivers are you using?

   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

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Alon,

Thank you for your information and we will use it if we need to find the bug 
next time.

-Original Message-
From: Alon Levy [mailto:al...@redhat.com] 
Sent: Thursday, January 19, 2012 7:26 PM
To: Stefan Hajnoczi
Cc: Charles.Tsai-蔡清海-研究發展部; qemu-devel; Michael Roth; Vadim Rozenfeld; 
spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, Jan 19, 2012 at 08:09:57AM +, Stefan Hajnoczi wrote:
 On Thu, Jan 19, 2012 at 09:41:15AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  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.

 If you need to reproduce the installation hang I suggest using qemu 
 -snapshot or qemu -drive ...,snapshot=on.  These options prevent 
 changes made by the guest to the disk image from being permanent.

 Once you terminate QEMU the changes will be gone and your disk image 
 will be unchanged - useful for repeatedly testing these types of issues!

There is an additional trick I use, if you add -no-shutdown then if you find 
yourself wanting to save the changes anyway (say you started with -snapshot but 
decided you want to keep the changes you have done), which you can do with 
commit virtio0 or commit ide0 (depending on the block device), it will 
allow you to do the commit after you shutdown the guest, which is easier then 
trying to get it to unmount the disks.

 Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-18 Thread Charles . Tsai-蔡清海-研究發展部

Vadim,

We downloaded the driver source from the following website.
===
wget --no-check-certificate 
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip

-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Thursday, January 19, 2012 8:25 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

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?

- Original Message -
From: Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com
To: Vadim Rozenfeld vroze...@redhat.com
Cc: Michael Roth mdr...@linux.vnet.ibm.com, Stefan Hajnoczi 
stefa...@gmail.com, spice-de...@lists.freedesktop.org, Alex Huang-黃必賢-研究發展部 
alex.hu...@cloudena.com, Alon Levy al...@redhat.com, qemu-devel 
qemu-devel@nongnu.org
Sent: Thursday, January 19, 2012 12:06:16 PM
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

Vadim,

We built it from the driver source. Up to this moment, we always use the same 
binary to test Qemu.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Thu, 2012-01-19 at 16:33 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 It is SMP system.
What about vioserial driver itself? 
did you build it from sources or is
it one, available through RHEL channels?

 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
 Sent: Thursday, January 19, 2012 3:58 PM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org;
 Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: RE: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS 
 on Qemu 0.15
 
 On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  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.
  
 On UP or SMP system?
  
  -Original Message-
  From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
  Sent: Wednesday, January 18, 2012 4:57 AM
  To: Michael Roth
  Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
  spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; 
  qemu-devel
  Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest 
  OS on Qemu 0.15
  
  On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
   On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
Vadim,
   
Thank you for your prompt reply. Here are the information for our test 
case.
   
   
1) we use the following command line to launch the guest OS
   
   
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,
se rv er,nowait -mon
chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,a
dd
r=
0x5.0x0 -drive
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,form
at
=r
aw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,boot
in
de
x=1
-netdev tap,fd=17,id=hostnet0
-device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,
mu
lt
ifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id
=c
ha
nnel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0 -spice 
port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0
x4
.0
x0
   
   
   
2). In Guest Windows XP OS
   
   
When the following callback function of the vioserial device  is called 
in guest OS. The allocated resources is empty.
   
   
VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
address of the vioserial device and map

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Vadim,

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.


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Wednesday, January 18, 2012 4:57 AM
To: Michael Roth
Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; 
Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
0.15

On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
 On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
 
  Thank you for your prompt reply. Here are the information for our test case.
 
 
  1) we use the following command line to launch the guest OS
 
 
  /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
  1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
  d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
  -chardev 
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,serv
  er,nowait -mon chardev=charmonitor,id=monitor,mode=readline
  -rtc base=localtime
  -device 
  virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=
  0x5.0x0 -drive 
  file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=r
  aw -device 
  ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootinde
  x=1
  -netdev tap,fd=17,id=hostnet0
  -device 
  rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,mult
  ifunction=on,addr=0x3.0x0
  -chardev pty,id=charserial0
  -device isa-serial,chardev=charserial0,id=serial0
  -chardev spicevmc,id=charchannel0,name=vdagent
  -device 
  virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=cha
  nnel0,name=com.redhat.spice.0
  -usb -device usb-tablet,id=input0
  -spice port=5900,addr=0.0.0.0,disable-ticketing
  -vga qxl -global qxl-vga.vram_size=67108864 -device 
  virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0
  x0
 
 
 
  2). In Guest Windows XP OS
 
 
  When the following callback function of the vioserial device  is called in 
  guest OS. The allocated resources is empty.
 
 
  VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
  address of the vioserial device and map the physical address to the logical 
  address space.
 
  I added the following trace and the value of nListSize is ZERO.
  TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
  __FUNCTION__,nListSize);
 
 
  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.
 
 
 Hi Charles,
 
 What versions of the virtio-win drivers are you using?
 
 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 works 
 intermittently for me using RHEL6.0 virtio-win, as well as the 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).

 http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
 
 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).
 
 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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-18 Thread Vadim Rozenfeld

On Thu, 2012-01-19 at 09:41 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 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.
 
On UP or SMP system?
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
 Sent: Wednesday, January 18, 2012 4:57 AM
 To: Michael Roth
 Cc: Charles.Tsai-蔡清海-研究發展部; Stefan Hajnoczi; 
 spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
 Subject: Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 
 0.15
 
 On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
  On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
   Vadim,
  
   Thank you for your prompt reply. Here are the information for our test 
   case.
  
  
   1) we use the following command line to launch the guest OS
  
  
   /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
   1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
   d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults 
   -chardev 
   socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,serv
   er,nowait -mon chardev=charmonitor,id=monitor,mode=readline
   -rtc base=localtime
   -device 
   virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=
   0x5.0x0 -drive 
   file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=r
   aw -device 
   ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootinde
   x=1
   -netdev tap,fd=17,id=hostnet0
   -device 
   rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,mult
   ifunction=on,addr=0x3.0x0
   -chardev pty,id=charserial0
   -device isa-serial,chardev=charserial0,id=serial0
   -chardev spicevmc,id=charchannel0,name=vdagent
   -device 
   virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=cha
   nnel0,name=com.redhat.spice.0
   -usb -device usb-tablet,id=input0
   -spice port=5900,addr=0.0.0.0,disable-ticketing
   -vga qxl -global qxl-vga.vram_size=67108864 -device 
   virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0
   x0
  
  
  
   2). In Guest Windows XP OS
  
  
   When the following callback function of the vioserial device  is called 
   in guest OS. The allocated resources is empty.
  
  
   VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
   address of the vioserial device and map the physical address to the 
   logical address space.
  
   I added the following trace and the value of nListSize is ZERO.
   TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
   __FUNCTION__,nListSize);
  
  
   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.
  
  
  Hi Charles,
  
  What versions of the virtio-win drivers are you using?
  
  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 works 
  intermittently for me using RHEL6.0 virtio-win, as well as the 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).
 
  http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
  
  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).
  
  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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-17 Thread Vadim Rozenfeld

On Tue, 2012-01-17 at 10:03 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 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 taken 
 over by another device already.
 Thank you for your help and I learned a lot about how a hardware device is 
 virtualized by Qemu.
 

You're welcome.
Vadim.
 
 
 -Original Message-
 From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
 Sent: Tuesday, January 17, 2012 5:28 AM
 To: Charles.Tsai-蔡清海-研究發展部
 Cc: Stefan Hajnoczi; Alon Levy; spice-de...@lists.freedesktop.org; Alex 
 Huang-黃必賢-研究發展部; qemu-devel
 Subject: RE: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
 On Mon, 2012-01-16 at 17:17 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
  
  I just ran the Qemu monitor to get the PCI information. The information is 
  listed belowe.
  From the listed information, I did not see anything wrong with the BAR0.
  ---
 Thank you.
 
   
   2). In Guest Windows XP OS
  
 SP3?
 Can you try reproducing this problem on Win7?
 
 Best regards,
 Vadim.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-17 Thread Vadim Rozenfeld

On Mon, 2012-01-16 at 19:50 -0600, Michael Roth wrote:
 On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:
  Vadim,
 
  Thank you for your prompt reply. Here are the information for our test case.
 
 
  1) we use the following command line to launch the guest OS
 
 
  /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
  1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
  d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=readline
  -rtc base=localtime
  -device 
  virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0
  -drive 
  file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
  -device 
  ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
  -netdev tap,fd=17,id=hostnet0
  -device 
  rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multifunction=on,addr=0x3.0x0
  -chardev pty,id=charserial0
  -device isa-serial,chardev=charserial0,id=serial0
  -chardev spicevmc,id=charchannel0,name=vdagent
  -device 
  virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
  -usb -device usb-tablet,id=input0
  -spice port=5900,addr=0.0.0.0,disable-ticketing
  -vga qxl -global qxl-vga.vram_size=67108864 -device 
  virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0
 
 
 
  2). In Guest Windows XP OS
 
 
  When the following callback function of the vioserial device  is called in 
  guest OS. The allocated resources is empty.
 
 
  VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
  address of the vioserial device and map the physical address to the logical 
  address space.
 
  I added the following trace and the value of nListSize is ZERO.
  TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
  __FUNCTION__,nListSize);
 
 
  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.
 
 
 Hi Charles,
 
 What versions of the virtio-win drivers are you using?
 
 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 works intermittently for 
 me using RHEL6.0 virtio-win, as well as the 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).

 http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
 
 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).
 
 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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

 at 0xc020 [0xc03f]
bus: usb.0
  type USB
  dev: usb-tablet, id input0
bus-prop: port = null
addr 0.1, port 1, speed 12, name QEMU USB Tablet, attached
  dev: piix3-ide, id 
bus-prop: addr = 01.1
bus-prop: romfile = null
bus-prop: rombar = 1
bus-prop: multifunction = off
bus-prop: command_serr_enable = on
class IDE controller, addr 00:01.1, pci id 8086:7010 (sub 1af4:1100)
bar 4: i/o at 0xc000 [0xc00f]
bus: ide.1
  type IDE
bus: ide.0
  type IDE
  dev: ide-drive, id ide0-0-0
dev-prop: drive = drive-ide0-0-0
dev-prop: logical_block_size = 512
dev-prop: physical_block_size = 512
dev-prop: min_io_size = 0
dev-prop: opt_io_size = 0
dev-prop: bootindex = 1
dev-prop: discard_granularity = 0
dev-prop: ver = 0.15.0
dev-prop: serial = QM1
bus-prop: unit = 0
  dev: qxl-vga, id 
dev-prop: ram_size = 67108864
dev-prop: vram_size = 67108864
dev-prop: revision = 3
dev-prop: debug = 0
dev-prop: guestdebug = 0
dev-prop: cmdlog = 0
bus-prop: addr = 02.0
bus-prop: romfile = vgabios-qxl.bin
bus-prop: rombar = 1
bus-prop: multifunction = off
bus-prop: command_serr_enable = on
class VGA controller, addr 00:02.0, pci id 1b36:0100 (sub 1af4:1100)
bar 0: mem at 0xf000 [0xf3ff]
bar 1: mem at 0xf400 [0xf7ff]
bar 2: mem at 0xf800 [0xf8001fff]
bar 3: i/o at 0xc040 [0xc05f]
bar 6: mem at 0x [0xfffe]
  dev: PIIX3, id 
bus-prop: addr = 01.0
bus-prop: romfile = null
bus-prop: rombar = 1
bus-prop: multifunction = on
bus-prop: command_serr_enable = on
class ISA bridge, addr 00:01.0, pci id 8086:7000 (sub 1af4:1100)
bus: isa.0
  type ISA
  dev: isa-serial, id serial0
dev-prop: index = 0
dev-prop: iobase = 0x3f8
dev-prop: irq = 4
dev-prop: chardev = charserial0
isa irq 4
  dev: isa-fdc, id 
dev-prop: driveA = null
dev-prop: driveB = null
dev-prop: bootindexA = -1
dev-prop: bootindexB = -1
isa irq 6
  dev: port92, id 
  dev: vmmouse, id 
  dev: vmport, id 
  dev: i8042, id 
isa irqs 1,12
  dev: isa-pit, id 
dev-prop: irq = 0
dev-prop: iobase = 0x40
  dev: mc146818rtc, id 
dev-prop: base_year = 2000
  dev: i440FX, id 
bus-prop: addr = 00.0
bus-prop: romfile = null
bus-prop: rombar = 1
bus-prop: multifunction = off
bus-prop: command_serr_enable = on
class Host bridge, addr 00:00.0, pci id 8086:1237 (sub 1af4:1100)
  dev: ioapic, id 
gpio-in 24
irq 0
mmio fec0/1000
  dev: fw_cfg, id 
dev-prop: ctl_iobase = 0x510
dev-prop: data_iobase = 0x511
irq 0
mmio /0002
mmio /0002
  dev: kvmclock, id 
irq 0
  dev: apic, id 
dev-prop: id = 0
irq 0
mmio fee0/0010


-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com] 
Sent: Monday, January 16, 2012 3:14 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Stefan Hajnoczi; Alon Levy; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; qemu-devel
Subject: RE: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

On Mon, 2012-01-16 at 10:02 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 Thank you for your prompt reply. Here are the information for our test case.
 
 
 1) we use the following command line to launch the guest OS
 
 
 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
 1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
 d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
 socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server
 ,nowait -mon chardev=charmonitor,id=monitor,mode=readline
 -rtc base=localtime
 -device 
 virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x
 5.0x0 -drive 
 file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
 -device 
 ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=
 1
 -netdev tap,fd=17,id=hostnet0
 -device 
 rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multif
 unction=on,addr=0x3.0x0
 -chardev pty,id=charserial0
 -device isa-serial,chardev=charserial0,id=serial0
 -chardev spicevmc,id=charchannel0,name=vdagent
 -device 
 virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann
 el0,name=com.redhat.spice.0
 -usb -device usb-tablet,id=input0
 -spice port=5900,addr=0.0.0.0,disable-ticketing
 -vga qxl

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Stefan Hajnoczi

On Mon, Jan 16, 2012 at 10:02:22AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 Thank you for your prompt reply. Here are the information for our test case.
 
 
 1) we use the following command line to launch the guest OS
 
 
 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
 1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
 d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
 socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=readline
 -rtc base=localtime
 -device 
 virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0
 -drive file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
 -device 
 ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
 -netdev tap,fd=17,id=hostnet0
 -device 
 rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multifunction=on,addr=0x3.0x0
 -chardev pty,id=charserial0
 -device isa-serial,chardev=charserial0,id=serial0
 -chardev spicevmc,id=charchannel0,name=vdagent
 -device 
 virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0

I tried the virtio-serial pieces with qemu.git and a RHEL6 guest.  The
guest was able to see the com.redhat.spice.0 port.  This suggests the
problem was either fixed since QEMU 0.15 or that it only affects the
Windows virtio drivers.

 -usb -device usb-tablet,id=input0
 -spice port=5900,addr=0.0.0.0,disable-ticketing
 -vga qxl -global qxl-vga.vram_size=67108864 -device 
 virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0
 
 
 
 2). In Guest Windows XP OS
 
 
 When the following callback function of the vioserial device  is called in 
 guest OS. The allocated resources is empty.
 
 
 VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
 address of the vioserial device and map the physical address to the logical 
 address space.
 
 I added the following trace and the value of nListSize is ZERO.
 TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
 __FUNCTION__,nListSize); 
 
 
 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.

I suggest trying qemu-kvm 1.0 or qemu-kvm.git because the issue may have
been fixed since 0.15.

If the issue is still present, you could use git-bisect(1) to find the
commit that caused behavior to change between 0.14 and 0.15.

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Stefan,

We need  the spice support in Qemu. Does qemu-kvm 1.0 support for spice?

-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com] 
Sent: Monday, January 16, 2012 4:37 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; Alon Levy; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; qemu-devel
Subject: Re: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

On Mon, Jan 16, 2012 at 10:02:22AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,

 Thank you for your prompt reply. Here are the information for our test case.

 1) we use the following command line to launch the guest OS

 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
 1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
 d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
 socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server
 ,nowait -mon chardev=charmonitor,id=monitor,mode=readline
 -rtc base=localtime
 -device 
 virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x
 5.0x0 -drive 
 file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
 -device 
 ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=
 1
 -netdev tap,fd=17,id=hostnet0
 -device 
 rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multif
 unction=on,addr=0x3.0x0
 -chardev pty,id=charserial0
 -device isa-serial,chardev=charserial0,id=serial0
 -chardev spicevmc,id=charchannel0,name=vdagent
 -device 
 virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann
 el0,name=com.redhat.spice.0

I tried the virtio-serial pieces with qemu.git and a RHEL6 guest.  The guest 
was able to see the com.redhat.spice.0 port.  This suggests the problem was 
either fixed since QEMU 0.15 or that it only affects the Windows virtio drivers.

 -usb -device usb-tablet,id=input0
 -spice port=5900,addr=0.0.0.0,disable-ticketing
 -vga qxl -global qxl-vga.vram_size=67108864 -device 
 virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0

 2). In Guest Windows XP OS

 When the following callback function of the vioserial device  is called in 
 guest OS. The allocated resources is empty.

 VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
 address of the vioserial device and map the physical address to the logical 
 address space.

 I added the following trace and the value of nListSize is ZERO.
 TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
 __FUNCTION__,nListSize);

 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.

I suggest trying qemu-kvm 1.0 or qemu-kvm.git because the issue may have been 
fixed since 0.15.

If the issue is still present, you could use git-bisect(1) to find the commit 
that caused behavior to change between 0.14 and 0.15.

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Stefan Hajnoczi

2012/1/16 Charles.Tsai-蔡清海-研究發展部 charles.t...@cloudena.com:
 We need  the spice support in Qemu. Does qemu-kvm 1.0 support for spice?

I believe so.

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Dominique Rodrigues



  
  
I currently use qemu-1.0 and I confirm that this version works fine
with SPICE.

Regards,

  
Dominique Rodrigues

  


8, rue Lemercier
75017 Paris
France
standard : +33 1 77 69 64 38
529 002 743 R.C.S. Paris
  


Le 16/01/2012 10:32, Charles.Tsai-蔡清海-研究發展部 a écrit :

  Stefan,

We need  the spice support in Qemu. Does qemu-kvm 1.0 support for spice?

-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com] 
Sent: Monday, January 16, 2012 4:37 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; Alon Levy; spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; qemu-devel
Subject: Re: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

On Mon, Jan 16, 2012 at 10:02:22AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:

  
Vadim,

Thank you for your prompt reply. Here are the information for our test case.


1) we use the following command line to launch the guest OS


/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server
,nowait -mon chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x
5.0x0 -drive 
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
-device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=
1
-netdev tap,fd=17,id=hostnet0
-device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multif
unction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann
el0,name=com.redhat.spice.0

  
  
I tried the virtio-serial pieces with qemu.git and a RHEL6 guest.  The guest was able to see the "com.redhat.spice.0" port.  This suggests the problem was either fixed since QEMU 0.15 or that it only affects the Windows virtio drivers.


  
-usb -device usb-tablet,id=input0
-spice port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0



2). In Guest Windows XP OS


When the following callback function of the vioserial device  is called in guest OS. The allocated resources is empty.


VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O address of the vioserial device and map the physical address to the logical address space.

I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, "%s (nListSize=%d)\n", 
__FUNCTION__,nListSize);


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.

  
  
I suggest trying qemu-kvm 1.0 or qemu-kvm.git because the issue may have been fixed since 0.15.

If the issue is still present, you could use git-bisect(1) to find the commit that caused behavior to change between 0.14 and 0.15.

Stefan
___
Spice-devel mailing list
spice-de...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel


  

attachment: dominique_rodrigues.vcf

smime.p7s
Description: S/MIME Cryptographic Signature

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Charles . Tsai-蔡清海-研究�l展部

Dominique,

 

Thank you for your information and we will try it here.

 

From: Dominique Rodrigues [mailto:dominique.rodrig...@nanocloud.com] 
Sent: Monday, January 16, 2012 5:51 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; 
Vadim Rozenfeld; qemu-devel
Subject: Re: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

 

I currently use qemu-1.0 and I confirm that this version works fine with SPICE.

Regards,


Dominique Rodrigues


  http://www.nanocloud.com 
8, rue Lemercier
75017 Paris
France
standard : +33 1 77 69 64 38
529 002 743 R.C.S. Paris


Le 16/01/2012 10:32, Charles.Tsai-蔡清海-研究發展部 a écrit : 

Stefan,
 
We need  the spice support in Qemu. Does qemu-kvm 1.0 support for spice?
 
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com] 
Sent: Monday, January 16, 2012 4:37 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; Alon Levy; spice-de...@lists.freedesktop.org; Alex 
Huang-黃必賢-研究發展部; qemu-devel
Subject: Re: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15
 
On Mon, Jan 16, 2012 at 10:02:22AM +0800, Charles.Tsai-蔡清海-研究發展部 wrote:

Vadim,
 
Thank you for your prompt reply. Here are the information for our test 
case.
 
 
1) we use the following command line to launch the guest OS
 
 
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server
,nowait -mon chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x
5.0x0 -drive 
file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
-device 
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=
1
-netdev tap,fd=17,id=hostnet0
-device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multif
unction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann
el0,name=com.redhat.spice.0

 
I tried the virtio-serial pieces with qemu.git and a RHEL6 guest.  The guest 
was able to see the com.redhat.spice.0 port.  This suggests the problem was 
either fixed since QEMU 0.15 or that it only affects the Windows virtio drivers.
 

-usb -device usb-tablet,id=input0
-spice port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0
 
 
 
2). In Guest Windows XP OS
 
 
When the following callback function of the vioserial device  is called 
in guest OS. The allocated resources is empty.
 
 
VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O 
address of the vioserial device and map the physical address to the logical 
address space.
 
I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
__FUNCTION__,nListSize);
 
 
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.

 
I suggest trying qemu-kvm 1.0 or qemu-kvm.git because the issue may have been 
fixed since 0.15.
 
If the issue is still present, you could use git-bisect(1) to find the commit 
that caused behavior to change between 0.14 and 0.15.
 
Stefan
___
Spice-devel mailing list
spice-de...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
image001.jpg

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

Stefan,

Can I replace both vireo-pci.c virtio-serial.h files from Qemu 1.0 source tree?
Both files are to initialize the vioserial device when launching a VM.

-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com] 
Sent: Monday, January 16, 2012 5:49 PM
To: Charles.Tsai-蔡清海-研究�l展部
Cc: Vadim Rozenfeld; Alon Levy; spice-de...@lists.freedesktop.org; Alex 
Huang-�S必�t-研究�l展部; qemu-devel
Subject: Re: [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012/1/16 Charles.Tsai-蔡清海-研究�l展部 charles.t...@cloudena.com:
 We need  the spice support in Qemu. Does qemu-kvm 1.0 support for spice?

I believe so.

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Stefan Hajnoczi

2012/1/16 Charles.Tsai-蔡清海-研究�l展部 charles.t...@cloudena.com:
 Can I replace both vireo-pci.c virtio-serial.h files from Qemu 1.0 source 
 tree?
 Both files are to initialize the vioserial device when launching a VM.

I suspect that will not work due to larger scale refactoring and
changes that have affected the codebase.  It's probably best to
recompile the full qemu-kvm 1.0 source release.

Stefan

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Vadim Rozenfeld

On Mon, 2012-01-16 at 17:17 +0800, Charles.Tsai-蔡清海-研究發展部 wrote:
 Vadim,
 
 I just ran the Qemu monitor to get the PCI information. The information is 
 listed belowe.
 From the listed information, I did not see anything wrong with the BAR0.
 ---
Thank you.

  
  2). In Guest Windows XP OS
 
SP3?
Can you try reproducing this problem on Win7?

Best regards,
Vadim.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15

2012-01-16 Thread Michael Roth


On 01/15/2012 08:02 PM, Charles.Tsai-蔡清海-研究發展部 wrote:

Vadim,

Thank you for your prompt reply. Here are the information for our test case.


1) we use the following command line to launch the guest OS


/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 
1,sockets=1,cores=1,threads=1 -name win_xp -uuid 
d9388815-ddd3-c38e-33c2-a9d5fcc7a775 -nodefconfig -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win_xp.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime
-device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x5.0x0
-drive file=/media/Images/Windows-XP.img,if=none,id=drive-ide0-0-0,format=raw
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-netdev tap,fd=17,id=hostnet0
-device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:e8:dc:b1,bus=pci.0,multifunction=on,addr=0x3.0x0
-chardev pty,id=charserial0
-device isa-serial,chardev=charserial0,id=serial0
-chardev spicevmc,id=charchannel0,name=vdagent
-device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0
-spice port=5900,addr=0.0.0.0,disable-ticketing
-vga qxl -global qxl-vga.vram_size=67108864 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x4.0x0



2). In Guest Windows XP OS


When the following callback function of the vioserial device  is called in 
guest OS. The allocated resources is empty.


VIOSerialEvtDevicePrepareHardware() ---This function is to get the I/O address 
of the vioserial device and map the physical address to the logical address 
space.

I added the following trace and the value of nListSize is ZERO.
TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, %s (nListSize=%d)\n, 
__FUNCTION__,nListSize);


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.



Hi Charles,

What versions of the virtio-win drivers are you using?

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 works intermittently for 
me using RHEL6.0 virtio-win, as well as the drivers at:


http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

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).


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.

Re: [Qemu-devel] [Spice-devel] Vioserial of Windows guest OS on Qemu 0.15