On Tue, Jan 22, 2013 at 02:24:28PM +0100, Han Pilmeyer wrote:
On 22/01/2013 13:50, Christophe Fergeau wrote:
On Tue, Jan 22, 2013 at 01:36:33PM +0100, Han Pilmeyer wrote:
Gal was kind enough to take a look at the crash dump and determined
I was running into an issue that was already fixed.
On 23/01/2013 11:01, Christophe Fergeau wrote:
Hrm, this means we'll need yet another update for
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ :(
I'm afraid so Christophe.
For what it's worth, Cole Robinson was kind enough to respin a virtio-win
ISO with updated
On Wed, Jan 23, 2013 at 01:10:15PM +0100, Han Pilmeyer wrote:
On 23/01/2013 11:01, Christophe Fergeau wrote:
Hrm, this means we'll need yet another update for
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ :(
I'm afraid so Christophe.
For what it's worth, Cole
On 17/01/2013 09:12, Gal Hammer wrote:
Hi Han,
The easiest way to help contributing with the virtio-serial crashes
debug is to provide the system failure information when a BSOD occurs.
You should copy the PDB (debug symbols) file (vioser.pdb) in the
C:\Windows\system32\drivers directory
On Tue, Jan 22, 2013 at 01:36:33PM +0100, Han Pilmeyer wrote:
Gal was kind enough to take a look at the crash dump and determined
I was running into an issue that was already fixed. He provided the
61.64.104.5100 vioser.sys driver (replacing the 61.64.104.4900 from
spice-guest-tools-0.3) and
On 22/01/2013 13:50, Christophe Fergeau wrote:
On Tue, Jan 22, 2013 at 01:36:33PM +0100, Han Pilmeyer wrote:
Gal was kind enough to take a look at the crash dump and determined
I was running into an issue that was already fixed. He provided the
61.64.104.5100 vioser.sys driver (replacing the
On Tue, Jan 22, 2013 at 02:24:28PM +0100, Han Pilmeyer wrote:
I'm afraid so Christophe. I'm sure that many people would be
grateful.
I forgot to say in my previous email, but thanks for getting to the bottom
of this!
One thing I noticed is that the pdb files for the drivers
were much older
Hi Han,
The easiest way to help contributing with the virtio-serial crashes
debug is to provide the system failure information when a BSOD occurs.
You should copy the PDB (debug symbols) file (vioser.pdb) in the
C:\Windows\system32\drivers directory (it where the vioser.sys driver
file
Hi,
On Sun, Dec 02, 2012 at 09:23:56AM +0200, Arnon Gilboa wrote:
Lots of virtio-serial driver bugs, which are very relevant to
cut/paste, were recently fixed.
The driver on the above link seem to be outdated. I'll try to find a
link for an updated upstream version.
I'm unfortunately not
Thanks for your efforts Arnon,
On 02/12/2012 08:23, Arnon Gilboa wrote:
Lots of virtio-serial driver bugs, which are very relevant to
cut/paste, were recently fixed.
The driver on the above link seem to be outdated. I'll try to find a
link for an updated upstream version.
Note that the
Han Pilmeyer wrote:
Thanks for your efforts Arnon,
On 02/12/2012 08:23, Arnon Gilboa wrote:
Lots of virtio-serial driver bugs, which are very relevant to
cut/paste, were recently fixed.
The driver on the above link seem to be outdated. I'll try to find a
link for an updated upstream version.
Hi Han,
Han Pilmeyer wrote:
Where would you like me to report back? Here or on the list?
list, cc'ed
What I'm mainly concerned about is losing accenot sure it's thess to
the mouse. If that happens, I can not easily fix the guest image.
can you send the logs from this scenario? you can
Han Pilmeyer wrote:
On 29/11/2012 13:58, Christophe Fergeau wrote:
On Thu, Nov 29, 2012 at 12:56:49PM +0200, Arnon Gilboa wrote:
Han Pilmeyer wrote:
However both yesterday and today, the guest refuses to do
cut/paste between the guest and host. Below I have the relevant
portion of the
Hi,
This last Tuesday I had a full day when cut/paste between my Windows 7
guest and Fedora 17 KVM host worked flawlessly. So I had high hopes that
the spice-guest-0.2.exe drivers had indeed fixed my issues.
However both yesterday and today, the guest refuses to do cut/paste
between the
Han Pilmeyer wrote:
Hi,
This last Tuesday I had a full day when cut/paste between my Windows 7
guest and Fedora 17 KVM host worked flawlessly. So I had high hopes
that the spice-guest-0.2.exe drivers had indeed fixed my issues.
However both yesterday and today, the guest refuses to do
On 29/11/2012 11:56, Arnon Gilboa wrote:
was it a large paste? this patch seem to fix it.
http://cgit.freedesktop.org/spice/win32/vd_agent/commit/?id=a69af07d
build vdagent vdservice, update yours and use newer virtio-serial
driver.
No, it was a small paste, a URL (around 30 characters I
On Thu, Nov 29, 2012 at 12:56:49PM +0200, Arnon Gilboa wrote:
Han Pilmeyer wrote:
Hi,
This last Tuesday I had a full day when cut/paste between my
Windows 7 guest and Fedora 17 KVM host worked flawlessly. So I had
high hopes that the spice-guest-0.2.exe drivers had indeed fixed
my issues.
17 matches
Mail list logo
