[Spice-devel] [Announce] spice-gtk 0.2

[Marc-André Lureau]

Hi

On Fri, Dec 3, 2010 at 3:48 PM, Gianluca Cecchi
<gianluca.cecchi at gmail.com> wrote:
> Ok.
> it works, nice.
> Some things:
> - The icons at the top under the menu should have some sort of tool
> tip? In that case O don't see anything while placing mouse on them

Spicy is a simple client. I don't know how far we want to develop it.
It has probably several UI issues / lack. Patches welcome!

> - My guest is w2k3 (no qxl drivers installed yet) 32 bit. The
> resolution is set to 800x600
> When I open the client, xwininfo says that my X11 spicy window is
>  Width: 640
>  Height: 575
>
> So I have to manually adjust to
>  Width: 800
>  Height: 695
>
> Is in plan a sort of "resize to VM" as in virt-manager vnc window?
> Or an automatic setting?

The plan is to have the guest resize it's size, instead of resizing
the client window. It works fine with Linux/vdagent. I didn't try it
with Windows. Do you have vdagent installed? (assuming the windows
version is able to resize the desktop)

> At start of spicy I receive:
> GSpice-Message: main channel: opened
> GSpice-Message: create window (#0)
>
> (spicy:19135): GLib-GObject-WARNING **: IA__g_object_get_valist:
> object class `SpiceDisplay' has no property named `Statusbar'
>
> (spicy:19135): GLib-GObject-WARNING **: IA__g_object_get_valist:
> object class `SpiceDisplay' has no property named `Toolbar'
>

Sorry about that, it was fixed just after the release yesterday. It is harmless.

> - Till now the guest starts with these options:
>
> qemu     17942     1 12 15:26 ?        00:00:00 /usr/bin/qemu-kvm -S
> -M fedora-13 -cpu core2duo,+x2apic -enable-kvm -m 768 -smp
> 1,sockets=1,cores=1,threads=1 -name w2k3 -uuid
> 9dd0e8cf-c501-b01a-48a4-eb025bb73f6b -nodefconfig -nodefaults -chardev
> socket,id=monitor,path=/var/lib/libvirt/qemu/w2k3.monitor,server,nowait
> -mon chardev=monitor,mode=readline -rtc base=localtime -boot dc -drive
> file=/vista/Users/tekkaman/Documents/virtualizzazione/spice/spice-windows.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
> -drive file=/var/lib/libvirt/images/w2k3new.img,if=none,id=drive-ide0-0-1,boot=on,format=raw
> -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1
> -device rtl8139,vlan=0,id=net0,mac=52:54:00:ff:61:63,bus=pci.0,addr=0x4
> -net tap,fd=45,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device
> isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -spice
> port=5903,disable-ticketing -vga qxl -device
> AC97,id=sound0,bus=pci.0,addr=0x5 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
>
> I installed the vdagent service and restarted guest trying to
> substitute in my wrapper
> -device usb-tablet,id=input0
> with
> -device virtio-serial -device spicevmc
>
> the domain doesn't start and I get:
>
> Error starting domain: internal error Process exited while reading
> console log output: char device redirected to /dev/pts/8
> do_spice_init: starting 0.6.3
> spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
> spice_server_add_interface: SPICE_INTERFACE_MOUSE
> mouse_mode_notifier: absolute pointer: not available
> spice_server_add_interface: SPICE_INTERFACE_QXL
> red_worker_main: begin
> svc:   1: vmc_initfn
> spice_server_add_interface: SPICE_INTERFACE_RECORD
> spice_server_add_interface: SPICE_INTERFACE_PLAYBACK
> qemu-kvm: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3:
> PCI: slot 3 function 0 not available for virtio-balloon-pci, in use by
> virtio-serial-pci
> qemu-kvm: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3:
> Device 'virtio-balloon-pci' could not be initialized
>
> Traceback (most recent call last):
>  File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain
>    vm.startup()
>  File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup
>    self._backend.create()
>  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
>    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error Process exited while reading console log
> output: char device redirected to /dev/pts/8
> do_spice_init: starting 0.6.3
> spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
> spice_server_add_interface: SPICE_INTERFACE_MOUSE
> mouse_mode_notifier: absolute pointer: not available
> spice_server_add_interface: SPICE_INTERFACE_QXL
> red_worker_main: begin
> svc:   1: vmc_initfn
> spice_server_add_interface: SPICE_INTERFACE_RECORD
> spice_server_add_interface: SPICE_INTERFACE_PLAYBACK
> qemu-kvm: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3:
> PCI: slot 3 function 0 not available for virtio-balloon-pci, in use by
> virtio-serial-pci
> qemu-kvm: -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3:
> Device 'virtio-balloon-pci' could not be initialized
>

> What are the arguments to substitute with what, to test for example
> copy/paste and vdagent?

There are various things that are needed before you can really start a
Spice VM from virt-manager, it's still work in progress.

I use a qemu wrapper to run my spice branch of qemu. I edit the VM
configuration with virsh and restart the VM. I think that's what you
need too:

#!/bin/sh
exec /usr/local/bin/qemu-system-x86_64 -enable-kvm -cpu host "$@"
-device virtio-serial -device spicevmc

Fyi, I'll publish soon some patches for virt-manager integration (I
push regularly my development branch in bitbucket:
http://bitbucket.org/elmarco/virt-manager)

But the qemu arguments issue probably need a qemu update.

regards

-- 
Marc-André Lureau