On Monday, April 09, 2012 06:00:59 AM Paul Lu-?R-?l wrote:
> Hi Vadim,
>
> The driver works properly on my machine. Is it possible send us the source
> code of the driver? We'd like to build it on our environment. Thanks a
> ton.
>
> BR
> Paul
http://people.redhat.com/vrozenfe/build-2
Hi Vadim,
The driver works properly on my machine. Is it possible send us the source code
of the driver? We'd like to build it on our environment.
Thanks a ton.
BR
Paul
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Monday, April 09, 2012 2:33 AM
To: Paul Lu
On Monday, March 19, 2012 10:31:16 PM Vadim Rozenfeld wrote:
> 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/im
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-1
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-1
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.
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:
> >
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 p
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 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
> >
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
@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 o
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 Le
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
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
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?
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: "
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.
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:
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-蔡清海-研究發展部
Thanks,
I'll check this problem.
Vadim.
- Original Message -
From: "Charles.Tsai-蔡清海-研究發展部"
To: "Charles.Tsai-蔡清海-研究發展部" , "Vadim Rozenfeld"
Cc: "Michael Roth" , "Stefan Hajnoczi"
, spice-devel@lists.freedesktop.org, "Alex Huang-黃必賢-研究發展部"
, "Alon Levy" , "qemu-devel"
, "Paul Lu-盧偉智-
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,
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
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-黃必賢-研
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,
Vadi
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
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;
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-蔡清海-研究發展部"
To: "Vadim Rozenfeld"
Cc: "Michael Roth" , "Stefan Hajnoczi"
, spice-devel@lists.
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]
>
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
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 hun
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, t
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
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
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
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
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_x
37 matches
Mail list logo
