In the mean time I have reproduced the event where a copy/paste
operation from host to guest generates
agent: no
in status bar of spicy window (but services.msc in windows xp says
that the agent is running??? what is the exact meaning of the status
bar information?)
These are the latest lines pro
On Thu, 2012-01-19 at 10:49 +0200, Arnon Gilboa wrote:
> Gianluca Cecchi wrote:
> > Just to inform that as the host is a laptop, this morning I booted it
> > again and now the w7 vm works, even if not so stably (sometimes in
> > minutes I have to restart agent because it is seen as running by
> >
Gianluca Cecchi wrote:
Just to inform that as the host is a laptop, this morning I booted it
again and now the w7 vm works, even if not so stably (sometimes in
minutes I have to restart agent because it is seen as running by
windows but copy/paste doesn't work any more).
Please send the qemu
Just to inform that as the host is a laptop, this morning I booted it
again and now the w7 vm works, even if not so stably (sometimes in
minutes I have to restart agent because it is seen as running by
windows but copy/paste doesn't work any more).
And in winobj indeed I can see the device yesterd
- Original Message -
From: "Arnon Gilboa"
To: "Vadim Rozenfeld"
Cc: "Gianluca Cecchi" ,
spice-devel@lists.freedesktop.org
Sent: Wednesday, January 18, 2012 4:34:27 PM
Subject: Re: [Spice-devel] spice vdagent in windows 7 32bit doesn't start on
f16
On Wed, Jan 18, 2012 at 04:06:51PM +0100, Gianluca Cecchi wrote:
> On Wed, Jan 18, 2012 at 3:52 PM, Alon Levy wrote:
> > Can you, as administrator in the guest:
> > 1.
> > net stop vdservice
> > rm c:\windows\temp\vd*.log
> > net start vdservice
> > # I assume it fails here
> > type c:\window
On Wed, Jan 18, 2012 at 3:52 PM, Alon Levy wrote:
> Can you, as administrator in the guest:
> 1.
> net stop vdservice
> rm c:\windows\temp\vd*.log
> net start vdservice
> # I assume it fails here
> type c:\windows\temp\vdservice.log | find "CreateFile"
>
> 2.
> Can you get winobj
> (http://te
This seems like a different bug, which was already encountered by others
in the list.
I will continue trying to repro/fix both bugs, and update you accordingly.
Vadim - please update regarding the driver.
Gianluca Cecchi wrote:
On Wed, Jan 18, 2012 at 3:41 PM, Arnon Gilboa wrote:
Hi Gianlu
On Wed, Jan 18, 2012 at 03:07:37PM +0100, Gianluca Cecchi wrote:
> On Wed, Jan 18, 2012 at 2:21 PM, Arnon Gilboa wrote:
> > Thanks for the update. Few questions:
> > 1. Looking at windows device manager, is there any error reported for the
> > virtio-serial driver?
> > 2. Is the error reproduced o
Hi Gianluca,
Can you please try to reproduce on win xp guest?
CC'ing Vadim (virtio-serial windows driver) to the thread.
On Wed, Jan 18, 2012 at 2:21 PM, Arnon Gilboa wrote:
Thanks for the update. Few questions:
1. Looking at windows device manager, is there any error reported for the
virtio
Vadim,
I think you have reproduced the same (VirtioVDIPort::init::CreateFile()
failed: 2).
Do you have any idea? it is not repro on linux guests.
Thanks,
Arnon
Gianluca Cecchi wrote:
After today updates on my F16 host it seems I'm not able to start
vdagent inside my 32bit windows 7.
One releva
Vadim,
I think you have reproduced the same (VirtioVDIPort::init::CreateFile()
failed: 2).
Do you have any idea? it is not repro on linux guests.
Thanks,
Arnon
Gianluca Cecchi wrote:
After today updates on my F16 host it seems I'm not able to start
vdagent inside my 32bit windows 7.
One releva
On Wed, Jan 18, 2012 at 2:21 PM, Arnon Gilboa wrote:
> Thanks for the update. Few questions:
> 1. Looking at windows device manager, is there any error reported for the
> virtio-serial driver?
> 2. Is the error reproduced only on startup, or also when you start the
> vdservice ("RHEV Spice Agent")
Thanks for the update. Few questions:
1. Looking at windows device manager, is there any error reported for
the virtio-serial driver?
2. Is the error reproduced only on startup, or also when you start the
vdservice ("RHEV Spice Agent") manually when the machine is up?
3. Is it reproduced for ot
After today updates on my F16 host it seems I'm not able to start
vdagent inside my 32bit windows 7.
One relevant update was for kernel, from 3.1.7-1.fc16.x86_64 to to
3.1.9-1.fc16.x86_64
no updates for libvirt/qemu/spice
agent is from windows-32-2024
on host:
$ rpm -qa|egrep "virt|spice|qemu
15 matches
Mail list logo
