Hello Christophe, After several tests, I finally found that the problem is due to some network settings. Although I have not understood everything (I don't know much about networking), I now have a way that works fine: - I start virt-manager from a shell with the correct network config (incl. proxy definitions when at work) I only use this GUI to configure and start the VM; display connection does not work in that case. - unset all proxy variables (http_proxy https_proxy ftp_proxy) and just use remote-viewer and it works. This way I can benefit from both the necessary proxy definitions and the Spice accelerated display with cut/paste etc... FYI I attached the log of a failing remote-viewer session when the proxy variables are set and the host firewall disabled. Many thanks for your kind and efficient help, using remote-viewer helped a lot ! Diego On 11/13/2013 02:30 PM, Christophe Fergeau wrote: > Hi, > > On Wed, Nov 13, 2013 at 02:17:44PM +0100, Diego COSTE wrote: >> On 13/11/2013 12:09, Christophe Fergeau wrote: >>> 'don't work' is awfully unspecific, the first step in getting some >>> help would be to give more details about how you are using spice >>> (which client, ...), and what 'don't work' means. Is something >>> crashing? Is the display corrupt? ... Christophe >> and thank you for your quick answer. > Thanks for the detailed explanation, this is very puzzling, but at least > it's possible to try to help ;) > >> As a real pure-flavour rookie, I use virt-manager to create/start the VM. >> I followed the IBM tutorial referenced in linux-kvm.org: >> http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/kvminstall/liaaikvminstallstart.htm >> >> The VM is configured with 2GB memory, 1 CPU out of the 4 of the host, >> config cloned from host (=Sandy Bridge) >> Network, storage and serial drivers use virtio mode. >> Network uses the default NAT mode. >> Storage is my raw /dev/sdb, a disk encrypted by my company's IT with >> McAfee endpoint encryption (previously named SafeBoot). >> At VM creation the display is automatically configured by virt-manager >> in Spice mode with QXL video (64MB). >> >> In the working case the graphics view of virt-manager first shows the >> McAfee end-point encryption login screen (this is pre-Windows) and >> eventually the normal windows display. Cut/paste work fine, etc... and >> the performances are good. >> >> In the non-working case, the graphic display remains uniformly grey, >> exactly as when the guest is not started at all. >> Still virt-manager reports that the machine is running and the power >> control switch lets me force power-off (mcafee login does not support >> acpi shutdown command). > Could you check on the host if qemu is running (it's probably named > qemu-kvm or qemu-system-x86_64)? As virt-manager reports that the VM is > running, I expect it to be running, but better to check ;) > The next thing I'd look at is libvirt logs (located in > /var/log/libvirt/qemu on the host). > You can also try to connect to the VM using remote-viewer, and get some > logs from remote-viewer (SPICE_DEBUG=1 G_MESSAGES_DEBUG=all remote-viewer > --spice-debug spice://localhost:5900 or so). > > >> I would have liked to post screen shots, but, well, these experiments >> are for my spare time and I have to work with that Windows machine, so I >> have now booted directly from this HDD. >> >> I have also started re-installing host Linux OS to restart from a fresh F19. >> This time I will try to install kvm and create the VM with the system >> already configured in multi-screen mode (need to bring the docking >> station and a monitor back to home for the test). > Something which would be interesting would be to also try with a basic > virt-manager VM if that is an option. What I mean by 'basic' is to create > the VM using virt-manager defaults (don't try to tweak CPU, network, ...) > using a raw or qcow2 image (rather than a raw /dev/sdb), no company > encryption if that's an option, ... Just set the display to SPICE, and add > a QXL device and SPICE agent channels (the latter is optional). > Testing this would help narrow down a bit what can go wrong. > > Christophe
[root@gnb404508 ~]# systemctl stop firewalld.service [root@gnb404508 ~]# remote-viewer --spice-debug spice://localhost:5900(remote-viewer:2886): GSpice-DEBUG: spice-session.c:171 New session (compiled from package spice-gtk 0.20) (remote-viewer:2886): GSpice-DEBUG: spice-session.c:175 Supported channels: main, display, inputs, cursor, playback, record, smartcard, usbredir (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11e0f60 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11e0f20 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11e0d50 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11cf840 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11dad50 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x11d84d0 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1602 session: disconnecting 0 (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:127 main-1:0: spice_channel_constructed (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1909 main-1:0: new main channel, switching (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:809 Changing main channel from (nil) to 0x11f2750 (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2385 main-1:0: Open coroutine starting 0x11f2750 (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2231 main-1:0: Started background coroutine 0x11f27e0 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1722 connecting 0x7f827fe328b0... (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1791 open host localhost:5900 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1708 connect ready (remote-viewer:2886): GSpice-WARNING **: HTTP proxy connection failed: 403 Forbidden (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2255 main-1:0: trying with TLS port (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2259 main-1:0: Connect error (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:464 clipboard_get_targets: (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:464 clipboard_get_targets: (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:464 clipboard_get_targets: (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "text/plain" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "UTF8_STRING" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "STRING" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "TEXT" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "COMPOUND_TEXT" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "TARGETS" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "MULTIPLE" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "TIMESTAMP" (remote-viewer:2886): GSpice-DEBUG: spice-gtk-session.c:468 "SAVE_TARGETS" (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1602 session: disconnecting 0 (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2036 main-1:0: channel destroy (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2585 main-1:0: channel disconnect 0 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:171 New session (compiled from package spice-gtk 0.20) (remote-viewer:2886): GSpice-DEBUG: spice-session.c:175 Supported channels: main, display, inputs, cursor, playback, record, smartcard, usbredir (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x12df250 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x12bf900 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x12920b0 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x12cbe70 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x12f56b0 (remote-viewer:2886): GSpice-DEBUG: usb-device-manager.c:856 device added 0x1270b20 (remote-viewer:2886): GSpice-DEBUG: spice-channel.c:2363 main-1:0: Coroutine exit main-1:0 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1602 session: disconnecting 0 (remote-viewer:2886): GSpice-DEBUG: spice-session.c:191 session dispose (remote-viewer:2886): GSpice-DEBUG: spice-session.c:1602 session: disconnecting 1
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel