Re: [Spice-devel] VirtIO bug (Mouse & Keyboard fail to work after opeining an non-exist serial port)

Please ignore my question. It is my fault. From: Charles.Tsai-蔡清海-研究發展部 Sent: Thursday, June 21, 2012 5:56 PM To: 'spice-devel@lists.freedesktop.org' Subject: VirtIO bug (Mouse & Keyboard fail to work after opeining an non-exist serial port) We implemented an virt IO port for printing channel.

[Spice-devel] VirtIO bug (Mouse & Keyboard fail to work after opeining an non-exist serial port)

We implemented an virt IO port for printing channel. It works without any problem if Qemu command options specify our printing device. However, we found a bug in virtio serial driver when a VM is launched without specifying the “printing device” from the qemu command line. In this case, mouse cl

[Spice-devel] VirtIO Net driver for Ubuntu 11.10

Alon, We recently ran an Ubuntu 11.10 VM which was installed with VirtIO NIC driver. The VirtIO net driver came from the Ubuntu's default package. The VM we installed was configured as a bridge mode. When we ran the Iperf test against the VM, the network interface of the VM was fairl

Re: [Spice-devel] A sever bug found in 64-bit WIndows 7 VM

Vadim, Our mail server limits the file size to send. Tell me the other ways to send you the files, for instance FTP. -Original Message- From: Vadim Rozenfeld [mailto:vroze...@redhat.com] Sent: Tuesday, May 29, 2012 7:23 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: Alon Levy; spice-devel@lists.freed

Re: [Spice-devel] A sever bug found in 64-bit WIndows 7 VM

Vadim, It is very easy to reproduce the bug. Memory dump and PDB file must go in pair. Let me know if you need my memory dump file and PDB file. -Original Message- From: Vadim Rozenfeld [mailto:vroze...@redhat.com] Sent: Tuesday, May 29, 2012 5:23 PM To: Alon Levy Cc: Charles.Tsai-蔡清海-研

Re: [Spice-devel] A sever bug found in 64-bit WIndows 7 VM

I disabled power saving mode. Will check if it is the root cause. I did try to remove qxl driver and the VM could run without crash. From: wangfeng wangfeng [mailto:wangfeng.v1.1...@gmail.com] Sent: Tuesday, May 29, 2012 12:07 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org; J

Re: [Spice-devel] A sever bug found in 64-bit WIndows 7 VM

Thank you for your prompt reply. We will double check power option. Are you saying that VM must turn off power saving mode? -Original Message- From: Andrew Cathrow [mailto:acath...@redhat.com] Sent: Tuesday, May 29, 2012 11:13 AM To: Charles.Tsai-蔡清海-研究發展部 Cc: Jonah.Wu-吳君勉-研究發展部; spice-d

[Spice-devel] A sever bug found in 64-bit WIndows 7 VM

Bug description: A sever bug was found on 64-bit Windows 7 VM which crashed after running idle for a while(~ 2-3 hours). When we checked the kvm process, it was killed from the system. Drivers installed: Qxl, Virtioserail Vdagent Qemu & Spice:

Re: [Spice-devel] Image size of the instance VM (qcow2 format)

Alon, No, our running VM does nothing and it simply just stays in idle. That is the reason we do not know why the image size of the instance VM keeps growing. I posted this issue to qemu-devel for helpful opinions. Thanks. -Original Message- From: Alon Levy [mailto:al...@redhat.com] S

Re: [Spice-devel] Image size of the instance VM (qcow2 format)

Hi Alon, Do you have any idea about this issue? We doubt this issue is caused by the Windows swap file(virtual memory) that Windows OS pages the memory contents to it during the run-time. However, we did disable the swap file setting from Windows. The image size of the instance VM still keeps g

Re: [Spice-devel] Qemu repository

Hans, There is no output. It simply just exits. Is there any way to get the log of Qemu? I tried to find the log in /var/log/libvirt/qemu but found nothing there. -Original Message- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: Friday, May 18, 2012 2:39 PM To: Charles.Tsai-蔡清海-

Re: [Spice-devel] Qemu repository

Hi Hans, Thank you for your suggestion. I tried your Qemu code. But I found my qemu script which is only coded with simple qemu command options. Before using your Qemu code, my VM could be launched by running the following script without any problem. But it failed to launch the

[Spice-devel] Image size of the instance VM (qcow2 format)

Hi Alon, We created a qcow2 based-image for a VM whose size is bigger when it is created. When a VM is launched, it is a instance VM image which refers to the based-image. Initially, the image size of instance VM is smaller than that of the based-mage. But we found the image siz

[Spice-devel] Qemu repository

Hi Alon, We decide to get the latest stable build for Qemu as our code base. However there are many public repositories for Qemu available. Which repository do you recommend for Qemu so that we can get latest code without any hassle? Thanks. _

Re: [Spice-devel] Memory leak in spice server

Alon, Yonit gave us a patch and we are verifying it. Will let you know if this patch fixes this issue. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Thursday, May 10, 2012 1:46 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org Subje

Re: [Spice-devel] Memory leak in spice server

Yonit, I will let you know after we verify it. Thanks. -Original Message- From: Yonit Halperin [mailto:yhalp...@redhat.com] Sent: Thursday, May 10, 2012 5:31 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: Alon Levy; spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] Memory l

[Spice-devel] Memory leak in spice server

Alon, Recently, we found a severe memory leak in Spice server when we kept playing video on guest OS. After several days, memory was totally used and Spice server crashed. I am not sure whether your team found the similar problem before or not. The current Spice

Re: [Spice-devel] [Spice-devil] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Hans, I don't know why there is a step 5 there. But it does hit the key point of the issue that I encountered. -Original Message- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: Friday, April 06, 2012 4:31 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.o

Re: [Spice-devel] [Spice-devil] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Hans, The core issue is that the "printing channel" is brought up too late and the spice client miss the timing window to initialize the printing channel. All of what you said are being implemented in our code. Can you scroll back to my previous message to get the full picture of the problem? Th

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Hans, This approach did not work and I gave it up already. -Original Message- From: Hans de Goede [mailto:hdego...@redhat.com] Sent: Friday, April 06, 2012 3:50 PM To: Charles.Tsai-蔡清海-研究發展部; spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] [RFC] register vmc interface early

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, Thanks. I will take a look at it and see how to make it work. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Thursday, April 05, 2012 2:33 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: Hans de Goede; spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] [RFC] regist

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, Can you tell me more specific point what you meant " bottomhalf"? I am testing my modified code to send a message thru the main channel and it works for me. However, if there is a better approach to fix this problem, I will take it. -Original Message- Fr

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, Your suggested approach does not work since the call of " vmc_register_interface" is too early before spice server is initialized. Please see function "qemu_spice_add_interface(SpiceBaseInstance *sin)" for the following Ooops message. "Oops: spice configured but not active" ==

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, All right. I got it. Thanks. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Tuesday, April 03, 2012 9:33 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: Hans de Goede; spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] [RFC] register vmc interface early for name !=

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, >>when " spice_chr_guest_open" is called, it is ignored if subtype == vdprint. >>chr->chr_guest_open = spice_chr_guest_open; Here, I just want to avoid "vdprint" from being created twice when "chr->chr_guest_open" is called. "chr->chr_guest_open" is still called when gust OS open the print

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, After I read the code, I got some idea on how to modify the code. For the printing channel, I will call "spice_chr_guest_open" early than it supposed to be. As such, the spice client can see the printing channel and initialize it. when " spice_chr_guest_ope

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, I am sorry. I don't see your patch. I will take a look at the following code and see how I can apply it for printing channel. > diff --git a/spice-qemu-char.c b/spice-qemu-char.c index > 1e735ff..d3ae0b7 100644 > --- a/spice-qemu-char.c > +++ b/spice-qe

Re: [Spice-devel] [RFC] register vmc interface early for name != vdagent [was: Re: Read data out of the Virtqueue]

Alon, Do you recommend us to use the new spice client code from "http://www.spice-space.org/downloads.html"; link? I will try to use it latter on to see what it is difference. You are right. The printing channel is created when the guest OS opens the virtIO printing chan

Re: [Spice-devel] Read data out of the Virtqueue

Alon, Our Windows client code is based on 0.10.1 release and that is, I believe, the latest one. "spice-gtk" is running in LINUX and I believe it is not applicable to Windows platform. Please refer to the following trace to understand what I said. As you can see, printing channel is register

Re: [Spice-devel] Read data out of the Virtqueue

Alon, In spice client, the creation of the channel is based on "init->num_of_channels" that is returned from the spice server. Please see the following function to create the spice channel from the client void RedClient::handle_channels(RedPeer::InMessage* message) { Spice

Re: [Spice-devel] Read data out of the Virtqueue

Alon, It is a bug that I modified for printing channel. BTW, can a spice channel be brought up or down based on a request from a spice client? The reason that I am asking for such a question is because the printing channel might be brought up based on a configuration policy. I would like to know

Re: [Spice-devel] Read data out of the Virtqueue

Alon, Forget my previous mail. When I dig into the vdservice, I found there was one bug to check the overlay I/O status after calling the VirtIO write function. After I fixed the bug, I can see more printing raw data inside the Qemu now. Although I still find some issues, hopefully I can fix it

[Spice-devel] Read data out of the Virtqueue

Alon, My printer driver can write the printing raw data into virtIO driver. But I cannot see the found the printing raw data in the spice server. For the vdagent, I found the following code segment which is a callback to read the data from the vdi_port. Do I need to add a similar code to read t

Re: [Spice-devel] SPICE_CHANNEL_TUNNEL

Hi Yonit, I am currently implementing a printing redirect based on the Virio framework. Can I use tunnel channel to forward printing file from the guest OS to the client? If I can do it, is there any API that I can call from the guest OS to inject the printing data into the tunnel channel? Rig

[Spice-devel] SPICE_CHANNEL_TUNNEL

Alon, I read the spice code and found a spice tunnel channel there. What is the purpose of the tunnel channel? Is it for network tunneling? What is the use case for tunnel channel in spice? ___ Spice-devel mailing list Spice-devel@lists

Re: [Spice-devel] Fail to create a printing channel

Alon, Thank you for information. In order isolate the issue, I simply just ran the following script to create the printing channel. Initially, I disable the Virio serial adapter. When I enable the Virtio serial adapter, the Windows is totally locked up. I am going to debug the Windows virtio

Re: [Spice-devel] Fail to create a printing channel

Alon, In Windows, driver name is provided by the device driver. In this case , "com.redhat.print.0" is the device visible to application. Because device "com.redhat.print.0" is created by the Qemu which is in Linux, how the Linux passes the driver information to Windows So that Windows applicati

Re: [Spice-devel] Fail to create a printing channel

Alon, I will put some traces in Qemu to see if I can find out where the code is stuck. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Thursday, March 22, 2012 10:22 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org Subject: Re: Fail to cre

Re: [Spice-devel] Fail to create a printing channel

Alon, I did all of what you mentioned before. Nothing is missed in my checklist. Function "spice_server_char_device_add_interface" in fact is not called at all. Qemu somehow is blocked somewhere. For now, I still do not know the root cause. -Original Message- From: Alon Levy [mailto:al..

[Spice-devel] Fail to create a printing channel

Alon, I am running the following script to create the printing channel based on the virtio device framework. When the VM is launched, it seems to block somewhere in Qemu. If I remove the following two lines, the VM can be launched without any problem.

Re: [Spice-devel] [Qemu-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.

Re: [Spice-devel] [Qemu-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

Re: [Spice-devel] [Qemu-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-devel@lists.freedesktop.

Re: [Spice-devel] [Qemu-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 Vir

Re: [Spice-devel] Access local network printer from guest OS

Thanks. Otherwise, I cannot get it when I read Windows service code. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Tuesday, March 13, 2012 7:09 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] Access local network printer

Re: [Spice-devel] Access local network printer from guest OS

Thanks. I got it now. How come the code is still there. I believe that CreateFile API fails definitely because there is no such a device in the system. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Tuesday, March 13, 2012 6:17 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice

Re: [Spice-devel] Access local network printer from guest OS

Alon, Yes, I did see these. But I think this device is no longer used by the service. That is why I want to clarify my puzzle. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Tuesday, March 13, 2012 5:27 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.

Re: [Spice-devel] Access local network printer from guest OS

Alon, Thank you for your clarification. I did not see VDI_PORT_DEV_NAME is being used in the service. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Tuesday, March 13, 2012 4:06 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org Subject: Re: [Spice

Re: [Spice-devel] Access local network printer from guest OS

Alon, I am reading the source code of the vdservice for Windows guest OS. "vdservice" if fact is a proxy software between Windows application and VirIO serial driver. I was suppressed to find that " vdservice" open two Windows kernel driver. In Windows, I only find one VirtIO P

Re: [Spice-devel] Access local network printer from guest OS

Alon, Thanks. Your additional information will help me a lot when I debug the code. I don't expect my code to work without tracing and debugging the code. -Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Monday, March 12, 2012 6:08 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: sp

Re: [Spice-devel] Access local network printer from guest OS

Alon, Here is a little bit confusion to me and you might be able to clear my puzzle. If launching a VM by adding the following options can create a separate VirIO for virtual printer driver, how the Qemu maps this logical channel to printing channel? In other words, Win

Re: [Spice-devel] Access local network printer from guest OS

-Original Message- From: Alon Levy [mailto:al...@redhat.com] Sent: Monday, March 12, 2012 3:17 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: spice-devel@lists.freedesktop.org Subject: Re: [Spice-devel] Access local network printer from guest OS On Mon, Mar 12, 2012 at 10:16:37AM +0800, Charles.Tsai-蔡

Re: [Spice-devel] Access local network printer from guest OS

Alon, Thank you for your prompt response. Please see my comments below inside the pair tag "Charles <

Re: [Spice-devel] Access local network printer from guest OS

Alon, I am implementing the code for the printing redirection for spice client. In the windows client, I know how to do it. Basically, I just follow the footprint of the playbackchannel. However, I still have a question regarding how my virtual printer driver delivers the printing r

Re: [Spice-devel] [Qemu-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.

Re: [Spice-devel] [Qemu-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-蔡清海-研究發展部

Re: [Spice-devel] [Qemu-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,

Re: [Spice-devel] [Qemu-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 s

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

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-devel@lists.freedesktop.org; Alex Huang-黃必賢-研

Re: [Spice-devel] [Qemu-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: Vad

Re: [Spice-devel] [Qemu-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;

Re: [Spice-devel] [Qemu-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-d

Re: [Spice-devel] [Qemu-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-devel@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Alon Levy; qemu-devel Subject: R

Re: [Spice-devel] [Qemu-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

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

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

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

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-devel@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部; Vadim Roz

Re: [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-devel@lists.freedesktop.org; Alex

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

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. --- INFO: Bus 0, device 0, function 0: Host bridge: PCI device 8086:1237 id "" Bus 0, device 1, f

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

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 -nodefconf

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

Alon, I tested Qemu 0.15 for Windows XP guest OS. But I found that the Virtual Serial I/O driver failed in driver initialization. The root cause of this problem is because the hardware resources(I/O in this device) is not allocated to the virtual serial I/O. When I debugg