No keyboard with Spice/qxl...

[Georgios Petasis]

Hi all,

I am facing a problem with Spice: if I enable spice as the display 
model, everything works (display, mouse), but the keyboard does not 
work. If I use VNC as the model, the keyboard works, but the display has 
a slow refresh rate.

Any ideas on what it may be wrong?

Running fedora 16, will updates installed.

Regards,

George

[Alon Levy]

On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
>  Hi all,
>  
>  I am facing a problem with Spice: if I enable spice as the display
>  model, everything works (display, mouse), but the keyboard does not
>  work. If I use VNC as the model, the keyboard works, but the display
>  has a slow refresh rate.
>   
No idea. How are you launching qemu, with virt-manager? can you post the
qemu command line? If not virt-manager then what client are you using?
what are the various versions?

rpm -q spice-server qemu-kvm spice-client spice-gtk virt-manager

What guest are you running?

Can you create a network capture where you:
1. close any spice connections (important, current limitation of wireshark
dissector)
2. start capture
3. connect client (if it's virt-manager, open the window)
4. press some keys on the keyboard
5. stop capture

>  Any ideas on what it may be wrong?
>  
>  Running fedora 16, will updates installed.
>  
>  Regards,
>  
>  George
>  _______________________________________________
>  virt mailing list
>  virt(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/virt

[Georgios Petasis]

Dear Alon,

Στις 7/3/2012 21:13, ο/η Alon Levy έγραψε:
>  On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
> > Hi all,
> >
> > I am facing a problem with Spice: if I enable spice as the display
> > model, everything works (display, mouse), but the keyboard does not
> > work. If I use VNC as the model, the keyboard works, but the display
> > has a slow refresh rate.
> >
>  No idea. How are you launching qemu, with virt-manager? 
Yes. I haven't used
anything from the command line.
>    can you post the
>  qemu command line? 
I found this in the log:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=spice 
/usr/bin/qemu-kvm -S -M pc-0.14 -cpu 
core2duo,+lahf_lm,+rdtscp,+pdpe1gb,+aes,+popcnt,+x2apic,+sse4.2,+sse4.1,+dca,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds

-enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -name 
Windows-7-64 -uuid 868b4585-dfc5-7007-ae94-cf636dd05ac8 -nodefconfig 
-nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows-7-64.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive 
file=/var/lib/libvirt/images/Windows-7-64.img,if=none,id=drive-virtio-disk0,format=raw 
-device 
virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
-drive file=/free/setup/Microsoft/VM 
dirvers/virtio-win-0.1-22.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw

-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 
-netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:28:cd:67,bus=pci.0,addr=0x3 
-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=127.0.0.1,disable-ticketing -vga qxl -global 
qxl-vga.vram_size=67108864 -device 
intel-hda,id=sound0,bus=pci.0,addr=0x4 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
>    If not virt-manager then what client are you using? 
I am
using the virt-manager client.
>  what are the various versions?
>
>  rpm -q spice-server qemu-kvm spice-client spice-gtk virt-manager
spice-server-0.10.1-1.fc16.x86_64
qemu-kvm-0.15.1-4.fc16.x86_64
spice-client-0.10.1-1.fc16.x86_64
spice-gtk-0.9-1.fc16.x86_64
virt-manager-0.9.1-2.fc16.noarch
>  What guest are you running? 
I am running Windows 7 (64 bit). The host is Fedora 16
(64 bit), on an 
intel sandy bridge-E (3930).
>  Can you create a network capture where you:
>  1. close any spice connections (important, current limitation of wireshark
>  dissector) 
How to do this?
>  2. start capture 
How to do this? What is capture?
>  3. connect client (if it's virt-manager, open the window)
>  4. press some keys on the keyboard
>  5. stop capture 
Thank you very much for your time,

George
> > Any ideas on what it may be wrong?
> >
> > Running fedora 16, will updates installed.
> >
> > Regards,
> >
> > George
> > _______________________________________________
> > virt mailing list
> > virt(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/virt

[Alon Levy]

On Wed, Mar 07, 2012 at 09:50:20PM +0200, Georgios Petasis wrote:
>  Dear Alon,
>  
>  Στις 7/3/2012 21:13, ο/η Alon Levy έγραψε:
>  >On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
>  >>Hi all,
>  >>
>  >>I am facing a problem with Spice: if I enable spice as the display
>  >>model, everything works (display, mouse), but the keyboard does not
>  >>work. If I use VNC as the model, the keyboard works, but the display
>  >>has a slow refresh rate.
>  >>
>  >No idea. How are you launching qemu, with virt-manager?
>  Yes. I haven't used anything from the command line.
>  >  can you post the
>  >qemu command line?
>  I found this in the log:
>  LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=spice
>  /usr/bin/qemu-kvm -S -M pc-0.14 -cpu
> core2duo,+lahf_lm,+rdtscp,+pdpe1gb,+aes,+popcnt,+x2apic,+sse4.2,+sse4.1,+dca,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds
>  -enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -name
>  Windows-7-64 -uuid 868b4585-dfc5-7007-ae94-cf636dd05ac8 -nodefconfig
>  -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows-7-64.monitor,server,nowait
>  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
>  -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7
>  -drive
> file=/var/lib/libvirt/images/Windows-7-64.img,if=none,id=drive-virtio-disk0,format=raw
>  -device
> virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>  -drive file=/free/setup/Microsoft/VM
> dirvers/virtio-win-0.1-22.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
>  -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
>  -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:28:cd:67,bus=pci.0,addr=0x3
>  -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=127.0.0.1,disable-ticketing -vga qxl -global
>  qxl-vga.vram_size=67108864 -device
>  intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>  hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
>  virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
>  >  If not virt-manager then what client are you using?
>  I am using the virt-manager client.
>  >what are the various versions?
>  >
>  >rpm -q spice-server qemu-kvm spice-client spice-gtk virt-manager
>  spice-server-0.10.1-1.fc16.x86_64
>  qemu-kvm-0.15.1-4.fc16.x86_64
>  spice-client-0.10.1-1.fc16.x86_64
>  spice-gtk-0.9-1.fc16.x86_64
>  virt-manager-0.9.1-2.fc16.noarch
>  >
>  >What guest are you running?
>  I am running Windows 7 (64 bit). The host is Fedora 16 (64 bit), on
>  an intel sandy bridge-E (3930).
>  >Can you create a network capture where you:
>  >1. close any spice connections (important, current limitation of wireshark
>  >dissector)
>  How to do this?
>  >2. start capture
>  How to do this? What is capture?
>  >3. connect client (if it's virt-manager, open the window)
>  >4. press some keys on the keyboard
>  >5. stop capture
>  Thank you very much for your time, 
sudo yum install tcpdump
sudo tcpdump -i lo -w /tmp/spice.cap

hopefully that file will be small (you only need a few seconds of
capture for the key presses and virt-manager spice connection, i.e.
window open). compress it if it's too large.

>  
>  George
>  >>Any ideas on what it may be wrong?
>  >>
>  >>Running fedora 16, will updates installed.
>  >>
>  >>Regards,
>  >>
>  >>George
>  >>_______________________________________________
>  >>virt mailing list
>  >>virt(a)lists.fedoraproject.org
>  >>https://admin.fedoraproject.org/mailman/listinfo/virt
>

[Georgios Petasis]

Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
>  sudo yum install tcpdump
>  sudo tcpdump -i lo -w /tmp/spice.cap
>
>  hopefully that file will be small (you only need a few seconds of
>  capture for the key presses and virt-manager spice connection, i.e.
>  window open). compress it if it's too large. 
Dear Alon,

I have placed the results here:

http://server.intellitech.gr/spice.cap

It does look like a binary file. Is it supposed to be this way?

Regards,

George

[Alon Levy]

On Wed, Mar 07, 2012 at 11:49:53PM +0200, Georgios Petasis wrote:
>  Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
>  >sudo yum install tcpdump
>  >sudo tcpdump -i lo -w /tmp/spice.cap
>  >
>  >hopefully that file will be small (you only need a few seconds of
>  >capture for the key presses and virt-manager spice connection, i.e.
>  >window open). compress it if it's too large.
>  Dear Alon,
>  
>  I have placed the results here:
>  
>  http://server.intellitech.gr/spice.cap
>  
>  It does look like a binary file. Is it supposed to be this way? 
Yes. Actually the file ending should have been pcap. It's a standard
format for network captures which I can read with wireshark with the
spice dissector and look for the key presses, just trying to figure out
if it's a problem at the client side or server/qemu side.

>  
>  Regards,
>  
>  George

[Alon Levy]

On Thu, Mar 08, 2012 at 08:35:56AM +0200, Alon Levy wrote:
>  On Wed, Mar 07, 2012 at 11:49:53PM +0200, Georgios Petasis wrote:
>  > Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
>  > >sudo yum install tcpdump
>  > >sudo tcpdump -i lo -w /tmp/spice.cap
>  > >
>  > >hopefully that file will be small (you only need a few seconds of
>  > >capture for the key presses and virt-manager spice connection, i.e.
>  > >window open). compress it if it's too large.
>  > Dear Alon,
>  > 
>  > I have placed the results here:
>  > 
>  > http://server.intellitech.gr/spice.cap
>  > 
>  > It does look like a binary file. Is it supposed to be this way?
>  
>  Yes. Actually the file ending should have been pcap. It's a standard
>  format for network captures which I can read with wireshark with the
>  spice dissector and look for the key presses, just trying to figure out
>  if it's a problem at the client side or server/qemu side.
>   
So, that dump contains only vnc traffic. Perhaps you recorded the wrong
vm?

>  > 
>  > Regards,
>  > 
>  > George
>  _______________________________________________
>  virt mailing list
>  virt(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/virt

[Alon Levy]

On Thu, Mar 08, 2012 at 08:35:56AM +0200, Alon Levy wrote:
>  On Wed, Mar 07, 2012 at 11:49:53PM +0200, Georgios Petasis wrote:
>  > Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
>  > >sudo yum install tcpdump
>  > >sudo tcpdump -i lo -w /tmp/spice.cap
>  > >
>  > >hopefully that file will be small (you only need a few seconds of
>  > >capture for the key presses and virt-manager spice connection, i.e.
>  > >window open). compress it if it's too large.
>  > Dear Alon,
>  > 
>  > I have placed the results here:
>  > 
>  > http://server.intellitech.gr/spice.cap
>  > 
>  > It does look like a binary file. Is it supposed to be this way?
>  
>  Yes. Actually the file ending should have been pcap. It's a standard
>  format for network captures which I can read with wireshark with the
>  spice dissector and look for the key presses, just trying to figure out
>  if it's a problem at the client side or server/qemu side.
>   
Sorry, wrong conclusion, it's probably spice but you didn't start the
capture *before* the virt-manager connection.

Perhaps an easier way to achieve that would be:

destroy the vm. (stop it from virt-manager)
start the capture (tcpdump -i ...)
start the vm.
do some key presses where you can see they don't have any affects.
stop the capture.
compress it this time - will save on the transport:
 bzip2 spice.cap

Thanks,
Alon

>  > 
>  > Regards,
>  > 
>  > George
>  _______________________________________________
>  virt mailing list
>  virt(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/virt

[Georgios Petasis]

Στις 8/3/2012 08:49, ο/η Alon Levy έγραψε:
>  On Thu, Mar 08, 2012 at 08:35:56AM +0200, Alon Levy wrote:
> > On Wed, Mar 07, 2012 at 11:49:53PM +0200, Georgios Petasis wrote:
> >> Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
> >>> sudo yum install tcpdump
> >>> sudo tcpdump -i lo -w /tmp/spice.cap
> >>>
> >>> hopefully that file will be small (you only need a few seconds of
> >>> capture for the key presses and virt-manager spice connection, i.e.
> >>> window open). compress it if it's too large.
> >> Dear Alon,
> >>
> >> I have placed the results here:
> >>
> >> http://server.intellitech.gr/spice.cap
> >>
> >> It does look like a binary file. Is it supposed to be this way?
> > Yes. Actually the file ending should have been pcap. It's a standard
> > format for network captures which I can read with wireshark with the
> > spice dissector and look for the key presses, just trying to figure out
> > if it's a problem at the client side or server/qemu side.
> >
>  Sorry, wrong conclusion, it's probably spice but you didn't start the
>  capture *before* the virt-manager connection.
>
>  Perhaps an easier way to achieve that would be:
>
>  destroy the vm. (stop it from virt-manager)
>  start the capture (tcpdump -i ...)
>  start the vm.
>  do some key presses where you can see they don't have any affects.
>  stop the capture.
>  compress it this time - will save on the transport:
>    bzip2 spice.cap
>
>  Thanks,
>  Alon
>  
Dear Alon,

The VM runs on a headless pc, that I access through VNC.
I did the following:

a) Installed wireshark, run as root (couldn't manage to run it as a 
normal user, even after adding the user to the wireshark group - perhaps 
a selinux denial).
b) Started capture on lo. I waited for a while, nothing got captured.
c) I started virt-manager, and then started the VM. Nothing captured.
d) I displayed the VM in virt-manager viewer, and capture started. I 
waited until the capture log stopped having new entries.
e) I verified that each time I move the mouse, packets were captured.
f) I verified that when I press keys, again packets are logged.

I have saved the capture from inside wireshark here: 
http://server.intellitech.gr/spice.cap.bz2

Towards the end of the capture, is only key presses, and the mouse 
movement outside the VM viewer, to stop capturing.

I haven't managed to find the spice dissector in wireshark (I got 
through yum).

Regards,

George

[Alon Levy]

On Thu, Mar 08, 2012 at 11:00:18AM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 08:49, ο/η Alon Levy έγραψε:
>  >On Thu, Mar 08, 2012 at 08:35:56AM +0200, Alon Levy wrote:
>  >>On Wed, Mar 07, 2012 at 11:49:53PM +0200, Georgios Petasis wrote:
>  >>>Στις 7/3/2012 22:13, ο/η Alon Levy έγραψε:
>  >>>>sudo yum install tcpdump
>  >>>>sudo tcpdump -i lo -w /tmp/spice.cap
>  >>>>
>  >>>>hopefully that file will be small (you only need a few seconds of
>  >>>>capture for the key presses and virt-manager spice connection, i.e.
>  >>>>window open). compress it if it's too large.
>  >>>Dear Alon,
>  >>>
>  >>>I have placed the results here:
>  >>>
>  >>>http://server.intellitech.gr/spice.cap
>  >>>
>  >>>It does look like a binary file. Is it supposed to be this way?
>  >>Yes. Actually the file ending should have been pcap. It's a standard
>  >>format for network captures which I can read with wireshark with the
>  >>spice dissector and look for the key presses, just trying to figure out
>  >>if it's a problem at the client side or server/qemu side.
>  >>
>  >Sorry, wrong conclusion, it's probably spice but you didn't start the
>  >capture *before* the virt-manager connection.
>  >
>  >Perhaps an easier way to achieve that would be:
>  >
>  >destroy the vm. (stop it from virt-manager)
>  >start the capture (tcpdump -i ...)
>  >start the vm.
>  >do some key presses where you can see they don't have any affects.
>  >stop the capture.
>  >compress it this time - will save on the transport:
>  >  bzip2 spice.cap
>  >
>  >Thanks,
>  >Alon
>  >
>  Dear Alon,
>  
>  The VM runs on a headless pc, that I access through VNC.
>  I did the following:
>  
>  a) Installed wireshark, run as root (couldn't manage to run it as a
>  normal user, even after adding the user to the wireshark group -
>  perhaps a selinux denial). 
Yes, wireshark works just as well. I run it as root too.

>  b) Started capture on lo. I waited for a while, nothing got captured.
ok, if the VM runs on a separate pc, of course it doesn't work - I
wrongly assumed it was on the same pc as virt-manager. You need to
capture the interface that the spice connection is on - so the network
connection, which would be em1 / eth0. Wireshark has a neat mode where
it shows you the packets per interface before starting a capture on a
specific interface (menu->capture->interfaces, or ctrl-i).

>  c) I started virt-manager, and then started the VM. Nothing
> captured.
>  d) I displayed the VM in virt-manager viewer, and capture started. I
>  waited until the capture log stopped having new entries.
>  e) I verified that each time I move the mouse, packets were captured.
>  f) I verified that when I press keys, again packets are logged.
>  
>  I have saved the capture from inside wireshark here:
>  http://server.intellitech.gr/spice.cap.bz2
>  
>  Towards the end of the capture, is only key presses, and the mouse
>  movement outside the VM viewer, to stop capturing.
>  
>  I haven't managed to find the spice dissector in wireshark (I got
>  through yum). 
It isn't in fedora yet, but it's in upstream.

>  
>  Regards,
>  
>  George

[Georgios Petasis]

Στις 8/3/2012 11:30, ο/η Alon Levy έγραψε:
>  ok, if the VM runs on a separate pc, of course it doesn't work -
> I 
>  wrongly assumed it was on the same pc as virt-manager. You need to 
>  capture the interface that the spice connection is on - so the network 
>  connection, which would be em1 / eth0. Wireshark has a neat mode where 
>  it shows you the packets per interface before starting a capture on a 
>  specific interface (menu->capture->interfaces, or ctrl-i). 
Dear Alon,

I am a little confused.
I have a PC. I have started a VNC server on the pc. I run virt-manager 
inside this vnc server. I run the VM from this virt-manager (so 
virt-manager & VM run in the pc that the vnc server runs).
And from a second pc, I have a vnc client, that I see all these.

I have uploaded a capture from em1 here: 
http://server.intellitech.gr/spice-em1.cap.bz2

Regards,

George

[Alon Levy]

On Thu, Mar 08, 2012 at 01:23:02PM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 11:30, ο/η Alon Levy έγραψε:
>  >ok, if the VM runs on a separate pc, of course it doesn't work - I
>  >wrongly assumed it was on the same pc as virt-manager. You need to
>  >capture the interface that the spice connection is on - so the
>  >network connection, which would be em1 / eth0. Wireshark has a
>  >neat mode where it shows you the packets per interface before
>  >starting a capture on a specific interface
>  >(menu->capture->interfaces, or ctrl-i).
>  Dear Alon,
>  
>  I am a little confused.
>  I have a PC. I have started a VNC server on the pc. I run
>  virt-manager inside this vnc server. I run the VM from this
>  virt-manager (so virt-manager & VM run in the pc that the vnc server
>  runs).
>  And from a second pc, I have a vnc client, that I see all these. 
OK, I didn't understand correctly, thanks for the patience.

>  
>  I have uploaded a capture from em1 here:
>  http://server.intellitech.gr/spice-em1.cap.bz2
>   
So this one will be pointless since the spice connection is over
loopback on your headless pc.

So you are using wireshark on the headless PC via VNC? I don't see any
TCP connections being created, as I would expect if virt-manager starter
the spice connection after the capture is started. Can you please make
sure virt-manager is closed before you start the capture?

>  Regards,
>  
>  George

[Georgios Petasis]

Στις 8/3/2012 13:47, ο/η Alon Levy έγραψε:
>  On Thu, Mar 08, 2012 at 01:23:02PM +0200, Georgios Petasis wrote:
> > Στις 8/3/2012 11:30, ο/η Alon Levy έγραψε:
> >> ok, if the VM runs on a separate pc, of course it doesn't work - I
> >> wrongly assumed it was on the same pc as virt-manager. You need to
> >> capture the interface that the spice connection is on - so the
> >> network connection, which would be em1 / eth0. Wireshark has a
> >> neat mode where it shows you the packets per interface before
> >> starting a capture on a specific interface
> >> (menu->capture->interfaces, or ctrl-i).
> > Dear Alon,
> >
> > I am a little confused.
> > I have a PC. I have started a VNC server on the pc. I run
> > virt-manager inside this vnc server. I run the VM from this
> > virt-manager (so virt-manager&  VM run in the pc that the vnc server
> > runs).
> > And from a second pc, I have a vnc client, that I see all these.
>  OK, I didn't understand correctly, thanks for the patience.
>
> > I have uploaded a capture from em1 here:
> > http://server.intellitech.gr/spice-em1.cap.bz2
> >
>  So this one will be pointless since the spice connection is over
>  loopback on your headless pc.
>
>  So you are using wireshark on the headless PC via VNC? 
Yes, wireshark runs on the
same pc as the vnc server, virt-manager & the VM.
I control it through a vnc client, from another pc.
>    I don't see any
>  TCP connections being created, as I would expect if virt-manager starter
>  the spice connection after the capture is started. Can you please make
>  sure virt-manager is closed before you start the capture? 
I have rebooted the pc, I
have started wireshark, and then started 
virt-manager & the VM. The VM booted (windows 7 64 bit), I pressed a few 
keys, then I opened the start menu, some more key presses, and finally I 
stopped the VM (normal shutdown from windows).

All this interaction is here: 
http://server.intellitech.gr/spice-wholevm.cap.bz2

If something is still missing, I think that it is possible it does not 
exist.

Regards,

George

[Darryl L. Pierce]

On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
>  Hi all,
>  
>  I am facing a problem with Spice: if I enable spice as the display
>  model, everything works (display, mouse), but the keyboard does not
>  work. If I use VNC as the model, the keyboard works, but the display
>  has a slow refresh rate.
>  
>  Any ideas on what it may be wrong?
>  
>  Running fedora 16, will updates installed. 
I have a similiar problem, except for me its the mouse that seems to be
adjusting to the geometry of the host desktop; i.e., when inside of the
viewing window the mouse pointer might be at (100,100) but clicking
takes place at (200, 200) in the window because that's approximately
where it is on the phyiscla desktop.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

[Georgios Petasis]

Στις 8/3/2012 15:07, ο/η Darryl L. Pierce έγραψε:
>  On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
> > Hi all,
> >
> > I am facing a problem with Spice: if I enable spice as the display
> > model, everything works (display, mouse), but the keyboard does not
> > work. If I use VNC as the model, the keyboard works, but the display
> > has a slow refresh rate.
> >
> > Any ideas on what it may be wrong?
> >
> > Running fedora 16, will updates installed.
>  I have a similiar problem, except for me its the mouse that seems to be
>  adjusting to the geometry of the host desktop; i.e., when inside of the
>  viewing window the mouse pointer might be at (100,100) but clicking
>  takes place at (200, 200) in the window because that's approximately
>  where it is on the phyiscla desktop.
>  
Have you tried adding the "EvTouch USB Graphics Tablet" input device, 
along with the normal mouse?

George

[Alon Levy]

On Thu, Mar 08, 2012 at 02:44:40PM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 13:47, ο/η Alon Levy έγραψε:
>  >On Thu, Mar 08, 2012 at 01:23:02PM +0200, Georgios Petasis wrote:
>  >>Στις 8/3/2012 11:30, ο/η Alon Levy έγραψε:
>  >>>ok, if the VM runs on a separate pc, of course it doesn't work - I
>  >>>wrongly assumed it was on the same pc as virt-manager. You need to
>  >>>capture the interface that the spice connection is on - so the
>  >>>network connection, which would be em1 / eth0. Wireshark has a
>  >>>neat mode where it shows you the packets per interface before
>  >>>starting a capture on a specific interface
>  >>>(menu->capture->interfaces, or ctrl-i).
>  >>Dear Alon,
>  >>
>  >>I am a little confused.
>  >>I have a PC. I have started a VNC server on the pc. I run
>  >>virt-manager inside this vnc server. I run the VM from this
>  >>virt-manager (so virt-manager&  VM run in the pc that the vnc server
>  >>runs).
>  >>And from a second pc, I have a vnc client, that I see all these.
>  >OK, I didn't understand correctly, thanks for the patience.
>  >
>  >>I have uploaded a capture from em1 here:
>  >>http://server.intellitech.gr/spice-em1.cap.bz2
>  >>
>  >So this one will be pointless since the spice connection is over
>  >loopback on your headless pc.
>  >
>  >So you are using wireshark on the headless PC via VNC?
>  Yes, wireshark runs on the same pc as the vnc server, virt-manager & the VM.
>  I control it through a vnc client, from another pc.
>  >  I don't see any
>  >TCP connections being created, as I would expect if virt-manager starter
>  >the spice connection after the capture is started. Can you please make
>  >sure virt-manager is closed before you start the capture?
>  I have rebooted the pc, I have started wireshark, and then started
>  virt-manager & the VM. The VM booted (windows 7 64 bit), I pressed a
>  few keys, then I opened the start menu, some more key presses, and
>  finally I stopped the VM (normal shutdown from windows).
>  
>  All this interaction is here:
>  http://server.intellitech.gr/spice-wholevm.cap.bz2
>  
>  If something is still missing, I think that it is possible it does
>  not exist.
>   
It's there, just the dissector thinks it VNC, but the initial bytes say
REDQ. Looking into it, thanks for the trouble.

>  Regards,
>  
>  George

[Georgios Petasis]

Στις 8/3/2012 15:29, ο/η Alon Levy έγραψε:
>  It's there, just the dissector thinks it VNC, but the initial
> bytes 
>  say REDQ. Looking into it, thanks for the trouble. 
Dear Alon,

Hm, I am sorry, I didn't mean to cause any trouble...

Regards,

George

[Darryl L. Pierce]

On Thu, Mar 08, 2012 at 03:13:54PM +0200, Georgios Petasis wrote:
>  Have you tried adding the "EvTouch USB Graphics Tablet"
> input
>  device, along with the normal mouse? 
No, I haven't, but will give it a shot.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

[Alon Levy]

On Thu, Mar 08, 2012 at 03:29:42PM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 15:29, ο/η Alon Levy έγραψε:
>  >It's there, just the dissector thinks it VNC, but the initial
>  >bytes say REDQ. Looking into it, thanks for the trouble.
>  Dear Alon,
>  
>  Hm, I am sorry, I didn't mean to cause any trouble... 
You misunderstand me: I didn't say you caused trouble, I was thanking
you for going through all the trouble to get three different captures
for me.

>  
>  Regards,
>  
>  George

[Darryl L. Pierce]

On Thu, Mar 08, 2012 at 03:13:54PM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 15:07, ο/η Darryl L. Pierce έγραψε:
>  >On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
>  >>Hi all,
>  >>
>  >>I am facing a problem with Spice: if I enable spice as the display
>  >>model, everything works (display, mouse), but the keyboard does not
>  >>work. If I use VNC as the model, the keyboard works, but the display
>  >>has a slow refresh rate.
>  >>
>  >>Any ideas on what it may be wrong?
>  >>
>  >>Running fedora 16, will updates installed.
>  >I have a similiar problem, except for me its the mouse that seems to be
>  >adjusting to the geometry of the host desktop; i.e., when inside of the
>  >viewing window the mouse pointer might be at (100,100) but clicking
>  >takes place at (200, 200) in the window because that's approximately
>  >where it is on the phyiscla desktop.
>  >
>  Have you tried adding the "EvTouch USB Graphics Tablet" input
>  device, along with the normal mouse? 
I'm sorry, I mispoke. My problem is with VNC, not Spice, and the mouse.
Setting things to Spice fixes it but is suboptimal since I have no use
for audio support, etc.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

[Darryl L. Pierce]

On Thu, Mar 08, 2012 at 03:13:54PM +0200, Georgios Petasis wrote:
>  Στις 8/3/2012 15:07, ο/η Darryl L. Pierce έγραψε:
>  >On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
>  >>Hi all,
>  >>
>  >>I am facing a problem with Spice: if I enable spice as the display
>  >>model, everything works (display, mouse), but the keyboard does not
>  >>work. If I use VNC as the model, the keyboard works, but the display
>  >>has a slow refresh rate.
>  >>
>  >>Any ideas on what it may be wrong?
>  >>
>  >>Running fedora 16, will updates installed.
>  >I have a similiar problem, except for me its the mouse that seems to be
>  >adjusting to the geometry of the host desktop; i.e., when inside of the
>  >viewing window the mouse pointer might be at (100,100) but clicking
>  >takes place at (200, 200) in the window because that's approximately
>  >where it is on the phyiscla desktop.
>  >
>  Have you tried adding the "EvTouch USB Graphics Tablet" input
>  device, along with the normal mouse? 
This seems to have fixed the problem with VNC. Thanks. :)

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

[Georgios Petasis]

Στις 8/3/2012 15:54, ο/η Darryl L. Pierce έγραψε:
>  On Thu, Mar 08, 2012 at 03:13:54PM +0200, Georgios Petasis wrote:
> > Στις 8/3/2012 15:07, ο/η Darryl L. Pierce έγραψε:
> >> On Wed, Mar 07, 2012 at 08:50:29PM +0200, George Petasis wrote:
> >>> Hi all,
> >>>
> >>> I am facing a problem with Spice: if I enable spice as the display
> >>> model, everything works (display, mouse), but the keyboard does not
> >>> work. If I use VNC as the model, the keyboard works, but the display
> >>> has a slow refresh rate.
> >>>
> >>> Any ideas on what it may be wrong?
> >>>
> >>> Running fedora 16, will updates installed.
> >> I have a similiar problem, except for me its the mouse that seems to be
> >> adjusting to the geometry of the host desktop; i.e., when inside of the
> >> viewing window the mouse pointer might be at (100,100) but clicking
> >> takes place at (200, 200) in the window because that's approximately
> >> where it is on the phyiscla desktop.
> >>
> > Have you tried adding the "EvTouch USB Graphics Tablet" input
> > device, along with the normal mouse?
>  This seems to have fixed the problem with VNC. Thanks. :)
>  
It works also with spice, although with spice the keyboard may not work 
(not because of the tablet).

Regards,

George

[Georgios Petasis]

Στις 8/3/2012 15:35, ο/η Alon Levy έγραψε:
>  On Thu, Mar 08, 2012 at 03:29:42PM +0200, Georgios Petasis wrote:
> > Στις 8/3/2012 15:29, ο/η Alon Levy έγραψε:
> >> It's there, just the dissector thinks it VNC, but the initial
> >> bytes say REDQ. Looking into it, thanks for the trouble.
> > Dear Alon,
> >
> > Hm, I am sorry, I didn't mean to cause any trouble...
>  You misunderstand me: I didn't say you caused trouble, I was thanking
>  you for going through all the trouble to get three different captures
>  for me.
>
> > Regards,
> >
> > George 
So, there seems to be no solution? I have to revert to vnc, to get the 
keyboard working?

George