Re: [Spice-devel] 2K/4K resolutions not available?

2015-06-15 Thread Mike 

Hi Christophe,

	I installed Debian Testing and interestingly enough the higher 
resolutions appear in the available resolution dropdown box, so we can 
just pick the one we want and everything worked fine, even without the 
spice agent installed and mucking about with dynamic resizing (which we 
aren't interested in anyways).


Using Debian going forward may be the path of least resistance given 
that Ubuntu doesn't seem too receptive to updating QXL anytime soon (I 
have posted a bug report, but I noticed there were several outstanding 
for over a year).


Thanks for your help.

On 06/15/2015 01:50 AM, Christophe Fergeau wrote:

On Fri, Jun 12, 2015 at 10:48:56AM -0700, Mike wrote:

Hi Christophe,

I fired up a Fedora 22 live CD and it does change the guest resolution 
when
I resize the window, but only larger, it doesn't resize it smaller for some
reason.

When comparing the package versions between Fedora and Ubuntu, the
spice-client/spice-vdagent versions match, but it appears that Fedora 22
uses xorg-x11-drv-qxl v0.1.3-2 and Ubuntu uses xserver-xorg-video-qxl
v0.1.1-0ubuntu6. So I'm guessing that may be the issue...

I will see if I can get Ubuntu upgraded to the latest version to confirm for
sure.


Yes would be nice (there's a 0.1.4 version as well), for now you could
try to make a local build of this new version, or get someone to build
that for you (potentially in a ppa). Debian has 0.1.4 in its unstable
repository, maybe their source package can be used for a rebuild on the
ubuntu version you need.

Christophe



--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] 2K/4K resolutions not available?

2015-06-12 Thread Mike 

Hi Christophe,

	I fired up a Fedora 22 live CD and it does change the guest resolution 
when I resize the window, but only larger, it doesn't resize it smaller 
for some reason.


When comparing the package versions between Fedora and Ubuntu, the 
spice-client/spice-vdagent versions match, but it appears that Fedora 22 
uses xorg-x11-drv-qxl v0.1.3-2 and Ubuntu uses xserver-xorg-video-qxl 
v0.1.1-0ubuntu6. So I'm guessing that may be the issue...


I will see if I can get Ubuntu upgraded to the latest version to confirm 
for sure.


Thanks.


On 06/12/2015 03:01 AM, Christophe Fergeau wrote:

On Thu, Jun 11, 2015 at 08:58:02AM -0700, Mike wrote:

Hi Christophe,

I was using just "spicec" as the viewer in full screen mode, but trying
remote-viewer doesn't seem to make any difference (full-screen or windowed
mode), it just scales the guest display (and results in blurry text) and
doesn't actually change the resolution on the guest side. I checked and
spice-vdagent/spice-vdagentd are running in the guest as well and the log
shows connections to it being made...


Hmm this could be an agent bug, this could be a qxl driver bug, this
could be an issue with your desktop environment, plenty of possible
parameters come into play here :( Could you try a fedora 22 guest and
see if it works there ? This would at least rule out host-side issues.

Christophe



--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] 2K/4K resolutions not available?

2015-06-12 Thread Mike 

Hi Gerd,

	I'm already specifying the following command line options, increasing 
the video memory was the first thing I tried, which didn't make a 
difference:


qxl-vga,id=video0,ram_size=134217728,vram_size=134217728,vgamem_mb=32

Thanks.

On 06/11/2015 11:04 PM, Gerd Hoffmann wrote:

On Do, 2015-06-11 at 08:58 -0700, Mike wrote:

Hi Christophe,

I was using just "spicec" as the viewer in full screen mode, but trying
remote-viewer doesn't seem to make any difference (full-screen or
windowed mode), it just scales the guest display (and results in blurry
text) and doesn't actually change the resolution on the guest side. I
checked and spice-vdagent/spice-vdagentd are running in the guest as
well and the log shows connections to it being made...

Using the script Gerd posted to force xrandr to change the resolution
does work for a few minutes, but as soon as I try to launch some
applications like Libreoffice Writer it crashes X immediately. It also
seems to cause all sorts of other strange issues with the window manager
(title bars disappear and reappear, etc...)


Try assign more memory to the qxl device.  For starters try double both
ram and vram (64m by default, try 128m instead).

HTH,
   Gerd




--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] 2K/4K resolutions not available?

2015-06-11 Thread Mike 

Hi Christophe,

	I was using just "spicec" as the viewer in full screen mode, but trying 
remote-viewer doesn't seem to make any difference (full-screen or 
windowed mode), it just scales the guest display (and results in blurry 
text) and doesn't actually change the resolution on the guest side. I 
checked and spice-vdagent/spice-vdagentd are running in the guest as 
well and the log shows connections to it being made...


Using the script Gerd posted to force xrandr to change the resolution 
does work for a few minutes, but as soon as I try to launch some 
applications like Libreoffice Writer it crashes X immediately. It also 
seems to cause all sorts of other strange issues with the window manager 
(title bars disappear and reappear, etc...)




On 06/11/2015 03:04 AM, Christophe Fergeau wrote:

Hey,

On Wed, Jun 10, 2015 at 03:37:09PM -0700, Mike wrote:

I'm trying to get 2K+ resolutions to work with SPICE/QXL and QEMU 2.2
(Ubuntu Vivid) on the host and Ubuntu Trusty on the guest. Currently the
highest resolution is 1920x1200... I tried increasing the QXL video memory
to 128MB from 64MB, but that didn't seem to make a difference, is there
something simple I'm missing perhaps?


These resolutions are missing from the drm driver
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/qxl/qxl_display.c#n175
booting with nomodeset should make them 'appear' in the guest (but
better not to do that).

With remote-viewer/gnome-boxes, you should be able to resize the guest
window to any size you want, including the higher resolutions you are
looking for. Is this not working?

Christophe



--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

[Spice-devel] 2K/4K resolutions not available?

2015-06-10 Thread Mike 
I'm trying to get 2K+ resolutions to work with SPICE/QXL and QEMU 2.2 
(Ubuntu Vivid) on the host and Ubuntu Trusty on the guest. Currently the 
highest resolution is 1920x1200... I tried increasing the QXL video 
memory to 128MB from 64MB, but that didn't seem to make a difference, is 
there something simple I'm missing perhaps?


Below is the QEMU command that I'm using:
---
/usr/bin/qemu-system-x86_64 -name DESKTOP_LINUX_SUPPORT2 -S -machine 
pc-i440fx-2.2,accel=kvm,usb=off -cpu 
SandyBridge,+invtsc,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme 
-m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
8d504c7b-616c-4283-a2aa-6636bb5ae598 -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/DESKTOP_LINUX_SUPPORT2.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet 
-no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 
-boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 
-device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 
-device 
ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 
-device 
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive 
file=/var/lib/libvirt/images/DESKTOP_LINUX_SUPPORT2.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 
-device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
-netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c6:d3:7d,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 
-spice port=5905,addr=0.0.0.0,disable-ticketing,seamless-migration=on 
-device 
qxl-vga,id=video0,ram_size=134217728,vram_size=134217728,vgamem_mb=32,bus=pci.0,addr=0x2 
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev 
spicevmc,id=charredir0,name=usbredir -device 
usb-redir,chardev=charredir0,id=redir0 -chardev 
spicevmc,id=charredir1,name=usbredir -device 
usb-redir,chardev=charredir1,id=redir1 -chardev 
spicevmc,id=charredir2,name=usbredir -device 
usb-redir,chardev=charredir2,id=redir2 -chardev 
spicevmc,id=charredir3,name=usbredir -device 
usb-redir,chardev=charredir3,id=redir3 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

---

Thanks.

--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] investigation into spice kms crash

2014-10-15 Thread Mike 


On 10/14/2014 08:07 AM, David Mansfield wrote:

Hi All,

I've been poking around trying to find the cause of an intermittent
spice kms crash, which I think is the same as these three bugzilla bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1038275
https://bugzilla.redhat.com/show_bug.cgi?id=1050034
https://bugzilla.redhat.com/show_bug.cgi?id=1039063

and an email I sent on 11 Sep. 2014 (Subject: qxl dri related kernel oops).

The code in question seems to be looping for about 150-300ms (in
qxl_ttm.c:qxl_sync_obj_wait) and if I've understood the architecture
correctly, it's waiting for the "host" side of QXL to release some objects.

Also, in qxl_fence.c, there is this comment:

For some reason every so often qxl hw fails to release, things go
wrong.

In particular, my colleague hits this semi-regularly when using spice
via a mobile-tether: i.e. high jitter, high latency and periodic network
dropouts.

Does the "qxl hw" have a discard policy when the client is "missing" and
is the 150-300ms timing loop in the guest based on anything?




--
Mike
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] Higher (quadratical) resolution

2013-02-20 Thread Mike 

Hi Dennis,

Wow, great help Dennis, you just solved my problem I've been 
struggling with for the last week and as expected it was something 
silly. I had upgraded from QEMU 1.0 to 1.2 but all my libvirt domains 
were still specifying PC-1.1, simply changing them to PC-1.2 allowed the 
framebuffer to go from 8MB to 16MB enabling the higher resolutions.


However, something else caught my eye that may help solve another 
problem I was having with dual heads, is your QEMU command generated by 
libvirt, and if so would you be able to send me a copy of the .XML file 
that you use (or just the graphics/QXL part)? I'm curious whats 
generating this part of the command:


-device qxl,id=video1,vram_size=67108864,bus=pci.0,addr=0x6 -device 
qxl,id=video2,vram_size=67108864,bus=pci.0,addr=0x7

Thanks.

On 13-02-20 12:43 AM, Dennis Böck wrote:

Hi Mike,

Xorg.log attached.
Here is the QEMU command for the VM:
/usr/bin/qemu-kvm -name Fedora18 -S -M pc-1.2 -enable-kvm -m 1024 -smp 
2,sockets=2,cores=1,threads=1 -uuid 2711c802-04d1-bed7-fba2-5c9f02fd54b9 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/Fedora18.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/var/lib/libvirt/images/Fedora18.img,if=none,id=drive-virtio-disk0,format=raw
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device 
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev 
tap,fd=22,id=hostnet0 -device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:ec:07:ff,bus=pci.0,addr=0x5 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing 
-vga qxl -global qxl-vga.vram_size=67108864 -device 
qxl,id=video1,vram_size=67108864,bus=pci.0,addr=0x6 -device 
qxl,id=video2,vram_size=67108864,bus=pci.0,addr=0x7 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4

Best regards
Dennis

Von: Mike [i...@snappymail.ca]
Gesendet: Dienstag, 19. Februar 2013 21:56
An: Marian Krcmarik
Cc: Dennis Böck; spice-devel@lists.freedesktop.org
Betreff: Re: [Spice-devel] Higher (quadratical) resolution

We're running into a similar problem, however the highest resolution
available to us is 1900x1080 in Linux (Windows is much higher).

Dennis, I'm wondering if you would be so kind as to provide us with your
Xorg.log file from the guest, as well as the QEMU command you use to
start the guest so we could do some comparisons?

Thanks.

On 13-02-19 07:16 AM, Marian Krcmarik wrote:

- Original Message -

From: "Dennis Böck" 
To: spice-devel@lists.freedesktop.org
Sent: Wednesday, February 13, 2013 3:53:12 PM
Subject: Re: [Spice-devel] Higher (quadratical) resolution

Hi David,

installing all updates for Fedora 18 didn't help, but enabling the
"Test Updates" repository did help - so obviously this feature is
still not officially released.
Now the output of xrandr looks like this:

Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 8192 x 8192
qxl-0 connected 2560x1600+0+0 0mm x 0mm
 2560x1600  60.0*+
 2560x1440  60.0
 2048x1536  60.0
 1920x1440  60.0
 1920x1200  60.0
 1920x1080  60.0
 1600x1200  60.0
 1680x1050  60.0
 1400x1050  60.0
 1600x900   60.0
 1280x1024  60.0
 1440x900   60.0
 1280x960   60.0
 1366x768   60.0
 1360x768   60.0
 1280x800   60.0
 1152x870   60.0
 1152x864   60.0
 1280x768   60.0
 1280x760   60.0
 1280x720   60.0
 1024x768   60.0
 1024x600   60.0
 960x64060.0
 832x62460.0
 800x60060.0
 800x48060.0
 640x48060.0
qxl-1 disconnected
qxl-2 disconnected
qxl-3 disconnected

Now the highest resolution which the "Displays" tool offers is
2560x1600 Pixels. Therefore I tried to change the resolution with
the comand:
xrandr --output qxl-0 --mode 2048x2048
But the error message:
xrandr: cannot find mode 2048x2048
was displayed.
Any idea how I could achieve this? (I would prefer a static xorg.conf
but don't know the configuration options)

Adding new modeline worked for me 
(https://wiki.archlinux.org/index.php/Xrandr), I've added only a line into 
Monitor section of xorg.conf:
"Modeline "2048x2048_60.00"  358.25  2048 2208 2432 2816  2048 2051 2061 2121 -hsync 
+vsync"

Best regards and thanks in advance
Dennnis

Von: David Jaša [dj...@redhat.com]
Gesendet: Montag, 11. Februar 2013 16:23
An: Dennis Böck
Cc: spice-devel@lists.freedesktop.org
Betreff: Re: [Spice-devel] Higher

Re: [Spice-devel] Higher (quadratical) resolution

2013-02-19 Thread Mike 
200 pixels. Is there any way to increase this limit?

Best regards and thanks in advance
Dennis
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

--

David Jaša, RHCE

SPICE QE based in Brno
GPG Key: 22C33E24
Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

--

David Jaša, RHCE

SPICE QE based in Brno
GPG Key: 22C33E24
Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel


___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel



--
Mike

___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] vdagent-win32 update

2011-11-28 Thread Mike Hinz 

-- 

Thanks!

Mike Hinz
mike.h...@hinzgroup.com
713-594-3095 (m) 


> Hi there,
> No updates for some time. Have you tried using the debug vdagent I 
> posted a while ago?
> A newer version with several fixes can be found at spice-space.org 
> download page, or directly at:
> http://www.spice-space.org/download/binaries/vdagent-win32_2024.zip
> Please update with your results.
> Regards,
> Arnon


Arnon,

I've gotten back on this problem and have done some more testing.  

First, there was a new version of qemu that I installed from the F15
virt-preview repos, 0.15.1.  Then within my WinXP VM, I installed the
new vdagent dated 11/24/2011.  

I can say that things have changed, but the problem is still present.
Let me try to describe.  First though are the contents of the log files:

vdservice.log

2976::INFO::2011-11-27 11:45:53,453::VDService::main::***Service
started***
2976::INFO::2011-11-27 11:45:53,453::log_version::1.1.0.1009
2976::INFO::2011-11-27 11:45:53,453::VDService::launch_agent::Wait for
vdagent to connect
2976::INFO::2011-11-27 11:45:53,531::VDService::launch_agent::Pipe
connected by vdagent
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::created
VirtioVDIPort
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::Connected to
server
3932::INFO::2011-11-27
11:45:55,453::VDService::control_handler::Interrogate service

vdagent.log

3632::INFO::2011-11-27 11:45:53,515::VDAgent::run::***Agent started in
session 0***
3632::INFO::2011-11-27 11:45:53,515::log_version::1.1.0.1009
3632::INFO::2011-11-27
11:45:53,515::DesktopLayout::consistent_displays::#qxls 1 #others 0
3632::INFO::2011-11-27 11:45:53,515::VDAgent::connect_pipe::Connected to
service pipe
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::37
3632::INFO::2011-11-27
11:45:53,515::VDAgent::input_desktop_message_loop::Desktop: Default
3632::INFO::2011-11-27
11:45:53,515::VDAgent::input_desktop_message_loop::First display setting
3632::INFO::2011-11-27 11:45:53,531::DisplaySetting::load::loading
display setting
3632::INFO::2011-11-27
11:45:53,531::DisplaySetting::reload_from_registry::explorer pid 144
3632::INFO::2011-11-27 11:45:53,531::DisplaySetting::reload_wallpaper::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_wallpaper::wallpaper wasn't
disabled
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_font_smoothing::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_font_smoothing::font smoothing
value didn't change
3632::INFO::2011-11-27 11:45:53,546::DisplaySetting::reload_animation::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_win_animation::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_win_animation::reload window
animation: success
3632::INFO::2011-11-27 11:45:53,546::DisplaySetting::reload_ui_effects::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_ui_effects::UserPreferencesMask =
80073e9e 6c
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::Got capabilities
(1)
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::77
3632::INFO::2011-11-27
11:45:53,656::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,656::VDAgent::send_announce_capabilities::37
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::Got
capabilitiesArnon,

I've gotten back on this problem and have done some more testing.  

First, there was a new version of qemu that I installed from the F15
virt-preview repos, 0.15.1.  Then within my WinXP VM, I installed the
new vdagent dated 11/24/2011.  

I can say that things have changed, but the problem is still present.
Let me try to describe.  First though are the contents of the log files:

vdservice.log

2976::INFO::2011-11-27 11:45:53,453::VDService::main::***Service
started***
2976::INFO::2011-11-27 11:45:53,453::log_version::1.1.0.1009
2976::INFO::2011-11-27 11:45:53,453::VDService::launch_agent::Wait for
vdagent to connect
2976::INFO::2011-11-27 11:45:53,531::VDService::launch_agent::Pipe
connected by vdagent
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::created
VirtioVDIPort
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::Connected to
server
3932::INFO::2011-11-27
11:45:55,453::VDService::control_handler::Interrogate service

vdagent.log

3632::INFO::2011-11-27 11:45:53,515::VDAgent::run::***Agent started in
session 0***
3632::INFO::2011-11-27 11:45:53,515::log_version::1.1.0.1009
3632::INFO::2011-11-27
11:45:53,515::DesktopLayout::consistent_displays::#qxls 1 #others 0
3632::INFO::2011-11-27 11:45:53,515::VDAgent::connect_pipe::Connected to
service pipe
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::

Re: [Spice-devel] vdagent-win32 update

2011-11-27 Thread Mike Hinz 
On Thu, 2011-11-24 at 14:56 +0200, Arnon Gilboa wrote:
> Hi there,
> No updates for some time. Have you tried using the debug vdagent I 
> posted a while ago?
> A newer version with several fixes can be found at spice-space.org 
> download page, or directly at:
> http://www.spice-space.org/download/binaries/vdagent-win32_2024.zip
> Please update with your results.
> Regards,
> Arnon
> 

(resent.  sent from wrong email account the first time).

Arnon,

I've gotten back on this problem and have done some more testing.  

First, there was a new version of qemu that I installed from the F15
virt-preview repos, 0.15.1.  Then within my WinXP VM, I installed the
new vdagent dated 11/24/2011.  

I can say that things have changed, but the problem is still present.
Let me try to describe.  First though are the contents of the log files:

vdservice.log

2976::INFO::2011-11-27 11:45:53,453::VDService::main::***Service
started***
2976::INFO::2011-11-27 11:45:53,453::log_version::1.1.0.1009
2976::INFO::2011-11-27 11:45:53,453::VDService::launch_agent::Wait for
vdagent to connect
2976::INFO::2011-11-27 11:45:53,531::VDService::launch_agent::Pipe
connected by vdagent
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::created
VirtioVDIPort
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::Connected to
server
3932::INFO::2011-11-27
11:45:55,453::VDService::control_handler::Interrogate service

vdagent.log

3632::INFO::2011-11-27 11:45:53,515::VDAgent::run::***Agent started in
session 0***
3632::INFO::2011-11-27 11:45:53,515::log_version::1.1.0.1009
3632::INFO::2011-11-27
11:45:53,515::DesktopLayout::consistent_displays::#qxls 1 #others 0
3632::INFO::2011-11-27 11:45:53,515::VDAgent::connect_pipe::Connected to
service pipe
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::37
3632::INFO::2011-11-27
11:45:53,515::VDAgent::input_desktop_message_loop::Desktop: Default
3632::INFO::2011-11-27
11:45:53,515::VDAgent::input_desktop_message_loop::First display setting
3632::INFO::2011-11-27 11:45:53,531::DisplaySetting::load::loading
display setting
3632::INFO::2011-11-27
11:45:53,531::DisplaySetting::reload_from_registry::explorer pid 144
3632::INFO::2011-11-27 11:45:53,531::DisplaySetting::reload_wallpaper::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_wallpaper::wallpaper wasn't
disabled
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_font_smoothing::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_font_smoothing::font smoothing
value didn't change
3632::INFO::2011-11-27 11:45:53,546::DisplaySetting::reload_animation::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_win_animation::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_win_animation::reload window
animation: success
3632::INFO::2011-11-27 11:45:53,546::DisplaySetting::reload_ui_effects::
3632::INFO::2011-11-27
11:45:53,546::DisplaySetting::reload_ui_effects::UserPreferencesMask =
80073e9e 6c
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::Got capabilities
(1)
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::77
3632::INFO::2011-11-27
11:45:53,656::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,656::VDAgent::send_announce_capabilities::37
3632::INFO::2011-11-27
11:45:53,656::VDAgent::handle_announce_capabilities::Got
capabilitiesArnon,

I've gotten back on this problem and have done some more testing.  

First, there was a new version of qemu that I installed from the F15
virt-preview repos, 0.15.1.  Then within my WinXP VM, I installed the
new vdagent dated 11/24/2011.  

I can say that things have changed, but the problem is still present.
Let me try to describe.  First though are the contents of the log files:

vdservice.log

2976::INFO::2011-11-27 11:45:53,453::VDService::main::***Service
started***
2976::INFO::2011-11-27 11:45:53,453::log_version::1.1.0.1009
2976::INFO::2011-11-27 11:45:53,453::VDService::launch_agent::Wait for
vdagent to connect
2976::INFO::2011-11-27 11:45:53,531::VDService::launch_agent::Pipe
connected by vdagent
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::created
VirtioVDIPort
2976::INFO::2011-11-27 11:45:53,531::VDService::execute::Connected to
server
3932::INFO::2011-11-27
11:45:55,453::VDService::control_handler::Interrogate service

vdagent.log

3632::INFO::2011-11-27 11:45:53,515::VDAgent::run::***Agent started in
session 0***
3632::INFO::2011-11-27 11:45:53,515::log_version::1.1.0.1009
3632::INFO::2011-11-27
11:45:53,515::DesktopLayout::consistent_displays::#qxls 1 #others 0
3632::INFO::2011-11-27 11:45:53,515::VDAgent::connect_pipe::Connected to
service pipe
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::Sending capabilities:
3632::INFO::2011-11-27
11:45:53,515::VDAgent::send_announce_capabilities::37
3632::

Re: [Spice-devel] vdagent-win32 update

2011-11-24 Thread Mike Hinz 
Arnon,

I'll have to apologize for the lack of action on my part.  I've gotten
busy with a bunch of customer work and other personal matters.  I'm
returning to my office on Monday and will restart my testing.  I'll also
try the newest vdagent on my XP VMs.  
-- 

Thanks! 


Mike Hinz
President
YR20
1718 Fry Road
Suite 440
Houston, TX  77084
mike.h...@yr20.com
832-225-1293 (o)
713-594-3095 (m)
832-550-2657 (f) 


On Thu, 2011-11-24 at 14:56 +0200, Arnon Gilboa wrote:
> Hi there,
> No updates for some time. Have you tried using the debug vdagent I 
> posted a while ago?
> A newer version with several fixes can be found at spice-space.org 
> download page, or directly at:
> http://www.spice-space.org/download/binaries/vdagent-win32_2024.zip
> Please update with your results.
> Regards,
> Arnon
> 

___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] problems with cut n paste - WinXP VM specificall

2011-10-05 Thread Mike Hinz 

On Sun, 2011-10-02 at 14:03 -0500, Mike Hinz wrote:
> On Sun, 2011-10-02 at 11:01 +0200, Arnon Gilboa wrote:
> > Hi Mike,
> > Can you please:
> > 1. net stop vdservice
> > 2. delete vdservice.log & vdagent.log from %windir%\temp
> > 3. net start vdservice
> > 4. copy a text in the guest, paste in host & vice versa
> > 5. send us the logs
> > Thanks,
> > Arnon
> 
> Arnon, Alon,
> 
> I've done the tests as you requested. 
.
.
.
.
> Hopefully the above is helpful to you.  Please don't hesitate to ask for
> more info as you need. 

> Thanks in advance for all your help!
> 
> Mike

I was just curious if you gents had made any progress with respect to
what might be happening with cut n' paste from the WinXP VM?  Was the
information that I had sent previously helpful?  Do you need more info
on the systems I'm using?

Please let me know and I'll be happy to supply.

Thanks in advance.

Mike. 

___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] problems with cut n paste - WinXP VM specificall

2011-10-02 Thread Mike Hinz 

On Sun, 2011-10-02 at 11:01 +0200, Arnon Gilboa wrote:
> Hi Mike,
> Can you please:
> 1. net stop vdservice
> 2. delete vdservice.log & vdagent.log from %windir%\temp
> 3. net start vdservice
> 4. copy a text in the guest, paste in host & vice versa
> 5. send us the logs
> Thanks,
> Arnon

Arnon, Alon,

I've done the tests as you requested.  First, I confirmed that the F15
host / F16 VM combination still works properly with respect to cut n'
paste.  Then I killed that VM and restarted the WinXP VM.

Then I did exactly as you stated above and verified in the cmd windows
that indeed the service was started and stopped properly.  As far as I
could tell, it indeed was.

When I did the actual test, please be aware that I did precisely the
following steps.

1.  net stop vdservice
2.  deleted the log files from the WinXP VM
3.  net start vdservice
4.  attempted 2 copy 2 lines of text from the WinXP VM from Wordpad.
5   attempted to paste those same 2 lines of text into the F15 host.
This operation failed.
6.  attempted to copy 2 lines of text from the F15 host.  
7   attempted to paste those same 2 lines of text into  WinXP VM.  This
operation failed.
7.  net stop vdservice.
8.  copy the contents of the log files into the email below.

Contents of vdservice.log:

482.078 VDService::main: ***Service started***
482.078 log_version: 0.5.1.0
482.078 VDService::launch_agent: Wait for vdagent to connect
482.109 VDService::launch_agent: Pipe connected by vdagent
482.109 VDService::execute: created VirtioVDIPort
482.109 VDService::execute: Connected to server
482.109 VDService::read_pipe: ReadFile without pending 40
484.078 VDService::control_handler: Interrogate service
541.656 VDService::control_handler: Stop service
541.656 VDService::stop: Service stopped
541.656 VDService::handle_control_event: Control command 1

Contents of vdagent.log

482.109 VDAgent::run: ***Agent started in session 0***
482.109 log_version: 0.5.1.0
482.109 DesktopLayout::consistent_displays: #qxls 1 #others 0
482.109 VDAgent::connect_pipe: Connected to service pipe
482.109 VDAgent::send_announce_capabilities: Sending capabilities:
482.109 VDAgent::send_announce_capabilities: 37
482.109 VDAgent::input_desktop_message_loop: Desktop: Default
482.109 VDAgent::input_desktop_message_loop: First display setting
482.109 DisplaySetting::load: loading display setting
482.109 DisplaySetting::reload_from_registry: explorer pid 2012
482.109 DisplaySetting::reload_wallpaper: 
482.109 DisplaySetting::reload_wallpaper: wallpaper wasn't disabled
482.109 DisplaySetting::reload_font_smoothing: 
482.109 DisplaySetting::reload_font_smoothing: font smoothing value
didn't change
482.109 DisplaySetting::reload_animation: 
482.109 DisplaySetting::reload_win_animation: 
482.109 DisplaySetting::reload_win_animation: reload window animation:
success
482.109 DisplaySetting::reload_ui_effects: 
482.109 DisplaySetting::reload_ui_effects: UserPreferencesMask =
80073e9e 70
541.656 VDAgent::read_completion: error 109
541.656 VDAgent::run: Agent stopped

Hopefully the above is helpful to you.  Please don't hesitate to ask for
more info as you need. 

I believe that I mentioned it in an earlier message but I'm running all
the most recent spice related drivers in the VM which I downloaded
directly from the spice-space.org download page.

Thanks in advance for all your help!

Mike




___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] problems with cut n paste - WinXP VM specificall

2011-09-30 Thread Mike Hinz 


On Fri, 2011-09-30 at 22:32 +0300, Alon Levy wrote:

> 
> Can you try spicec and report? Can you try to restart vdagent in the
> guest and report?

Alon,

I've just tried spicec and I've also tried restarting vdagent in the
guest.  There was no change.  The WinXP VM doesn't seem to support cut n
paste, while the F16 VM continues to work well.  

I didn't specifically note it in my earlier email, but I've tried
uninstalling all the spice specific element within the WinXP vm and
reinstalling them and have tried stopping and restarting the vdagent in
the WinXP VM repeatedly earlier and it's never made any difference.

I am convinced the problems lie within the WinXP VM as the host machine
works perfectly with the F16 VM.

FYI and thanks!

Mike.  


___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

[Spice-devel] problems with cut n paste - WinXP VM specifically

2011-09-30 Thread Mike Hinz 
All,

I'd like to be able to use the cut n paste function between a host
machine a VM.  Here's what I've tried and found so far.

Host is a F15-64 bit system with virt-preview repo enabled and
everything fully updated.

First VM is F16-64bit-beta-rc3 with everything fully updated.  Cut and
paste works perfectly between that VM and the host.  All I had to do was
to install spice-vdagent and viola, it worked!

Second VM is WinXP-SP3 with the qxl video driver, the virtio-serial
driver, and the vdagent all installed within the VM.  All these were
downloaded from the spice-space.org website and are the latest versions
on the download page.  Examining the WinXP device manager and the admin
console to check services, it appears to me that all 3 drivers are
correctly loaded.  Certainly sound works and the video is quite good
quality so I'm sure that major portions of everything are indeed working
correctly.  

This WinXP VM will not cut n paste at all.  I've struggled to find the
issue and the only clues I have are as follows:

In the log file /var/log/libvirt/qemu/winxp.log, I see the following 3
lines when I attempt to copy a bit of text from within Wordpad in the
VM:

main_channel_release_pipe_item: SPICE_MSG_MAIN_AGENT_DATA 0x3d2dea0
0x3d2d040, 0
main_channel_release_pipe_item: SPICE_MSG_MAIN_AGENT_DATA 0x3d2dea0
0x3d26cc0, 0
dispatch_vdi_port_data: invalid port

I also did 'virt-manager --debug' to see if I could see any relevant
messages there and I see the following:

(virt-manager:2574): GSpice-CRITICAL **: agent_clipboard_request:
assertion `c->agent_connected' failed

followed by

(virt-manager:2574): GSpice-WARNING **: clipboard get timed out

Which then seem to report every time to you try to copy something from
within the VM.  

The above log messages look wrong to me, so I wanted to report them to
see if there's something obvious.  

What's next?  Should I file this as a bug and if so where?



-- 
Thanks!


Mike Hinz
President
YR20
1718 Fry Road
Suite 440
Houston, TX  77084
mike.h...@yr20.com
832-225-1293 (o)
713-594-3095 (m)
832-550-2657 (f) 



___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Re: [Spice-devel] problems with cut n paste - WinXP VM specificall

2011-09-30 Thread Mike Hinz 


On Fri, 2011-09-30 at 12:28 +0200, Christophe Fergeau wrote:
> Hey,
> 
> On Thu, Sep 29, 2011 at 08:05:53PM -0500, Mike Hinz wrote:
> > This WinXP VM will not cut n paste at all.  I've struggled to find the
> > issue and the only clues I have are as follows:
> > 
.
.
.

> 
> How do you start your Windows VM? Maybe you're using different parameters
> than for the linux guest?
> 
> Christophe

I started both VMs via Fedora's virt-manager, latest version from
virt-preview.  

Here's what's generated for the F16 VM in which cut n paste does work.  

LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 2048
-smp 1,sockets=1,cores=1,threads=1 -name F160-beta-rc3 -uuid
61a4a3a6-7db5-c631-895e-c9716ce95fc0 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/F160-beta-rc3.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x7.0x0 
-drive 
file=/home/mike/vmstore/f16-beta-rc3.img,if=none,id=drive-virtio-disk0,format=qcow2
 -device 
virtio-blk-pci,bus=pci.0,multifunction=on,addr=0x5.0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -drive 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 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:ed:19:14,bus=pci.0,multifunction=on,addr=0x3.0x0
 -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,multifunction=on,addr=0x4.0x0 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,multifunction=on,addr=0x6.0x0


Here's what's generated for the WinXP VM in which cut n paste doesn't
work.

LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 2000
-smp 1,sockets=1,cores=1,threads=1 -name winxp -uuid
4a8d92fc-d13b-22e2-e668-3ca188248883 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,multifunction=on,addr=0x6.0x0 
-drive 
file=/home/mike/vmstore/winxp3.img,if=none,id=drive-ide0-0-0,format=qcow2 
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 
-netdev tap,fd=24,id=hostnet0 -device 
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:14:cb:b3,bus=pci.0,multifunction=on,addr=0x3.0x0
 -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=5901,addr=127.0.0.1,disable-ticketing -vga qxl -global 
qxl-vga.vram_size=9437184 -device 
AC97,id=sound0,bus=pci.0,multifunction=on,addr=0x4.0x0 -device 
virtio-balloon-pci,id=balloon0,bus=pci
 .0,multifunction=on,addr=0x5.0x0

The above looks ok to me with respect to at least the Spice elements,
but I'm certainly not an expert.  

After seeing the above, can you comment on what might be the issue?
There have been some issues over 'pci multifunction' devices not working
correctly for Windows VMs, but I have no idea of that issue is related
to this.

Thanks in advance for any help!

Mike


___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

[Spice-devel] problems with cut n paste - WinXP VM specificall

2011-09-29 Thread Mike Hinz 

All,

I'd like to be able to use the cut n paste function between a host
machine a VM.  Here's what I've tried and found so far.

Host is a F15-64 bit system with virt-preview repo enabled and
everything fully updated.

First VM is F16-64bit-beta-rc3 with everything fully updated.  Cut and
paste works perfectly between that VM and the host.  All I had to do was
to install spice-vdagent and viola, it worked!

Second VM is WinXP-SP3 with the qxl video driver, the virtio-serial
driver, and the vdagent all installed within the VM.  All these were
downloaded from the spice-space.org website and are the latest versions
on the download page.  Examining the WinXP device manager and the admin
console to check services, it appears to me that all 3 drivers are
correctly loaded.  Certainly sound works and the video is quite good
quality so I'm sure that major portions of everything are indeed working
correctly.  

This WinXP VM will not cut n paste at all.  I've struggled to find the
issue and the only clues I have are as follows:

In the log file /var/log/libvirt/qemu/winxp.log, I see the following 3
lines when I attempt to copy a bit of text from within Wordpad in the
VM:

main_channel_release_pipe_item: SPICE_MSG_MAIN_AGENT_DATA 0x3d2dea0
0x3d2d040, 0
main_channel_release_pipe_item: SPICE_MSG_MAIN_AGENT_DATA 0x3d2dea0
0x3d26cc0, 0
dispatch_vdi_port_data: invalid port

I also did 'virt-manager --debug' to see if I could see any relevant
messages there and I see the following:

(virt-manager:2574): GSpice-CRITICAL **: agent_clipboard_request:
assertion `c->agent_connected' failed

followed by

(virt-manager:2574): GSpice-WARNING **: clipboard get timed out

Which then seem to report every time to you try to copy something from
within the VM.  

The above log messages look wrong to me, so I wanted to report them to
see if there's something obvious.  

What's next?  Should I file this as a bug and if so where?
-- 
Thanks!


Mike Hinz
President
YR20
1718 Fry Road
Suite 440
Houston, TX  77084
mike.h...@yr20.com
832-225-1293 (o)
713-594-3095 (m)
832-550-2657 (f) 



___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel