Hello, Replying to myself.. see below for more details about the problem. On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote: > > 2) virt-viewer doesn't work anymore. > > It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 2.0-7, with a lot of changes.. > > If I try to use virt-viewer and run "virt-viewer <testvm>" command, I get an error popup dialog saying "Failed to connect: Display can only be attached through libvirt with --attach". > > verbose debug output: > > > # virt-viewer -v --debug -c "xen://" testvm > > (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > [root at fdell01 rpm]# less testvm01.txt > (virt-viewer:9374): virt-viewer-DEBUG: connecting ... > (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// > Opening connection to libvirt with URI xen:// > (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520 > (virt-viewer:9374): virt-viewer-DEBUG: initial connect > (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f0000 > (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 > (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback > (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f0000 > (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining display > Guest testvm is running, determining display > (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display > Guest testvm has a vnc display > (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection > (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics > (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1 > (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7 > (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820 > > (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > > > And trying with the "attach" option: > > # virt-viewer -v --debug -c "xen://" -a testvm > > (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > [root at fdell01 rpm]# less testvm02.txt > (virt-viewer:9389): virt-viewer-DEBUG: connecting ... > (virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// > Opening connection to libvirt with URI xen:// > (virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580 > (virt-viewer:9389): virt-viewer-DEBUG: initial connect > (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 > (virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 > (virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback > (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 > (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining display > Guest testvm is running, determining display > (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display > Guest testvm has a vnc display > (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection > (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not supported by this connection > (virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1 > (virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7 > (virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820 > > (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 > > > > So it seems both connection types/methods now fail.. I'm not sure if the issue is in our custom libvirt build, or in Xen's qemu.. (googling for those errors reveals some related patches which also have patches for qemu: http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185) > > Error from the first attempt: > > (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection > (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics > > Error from the second attempt: > (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection > (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not supported by this connection > It seems CentOS 7.1 is still using virt-viewer version 0.6.0-12, and on centos7 virt-viewer works OK for me with xen/libvirt! So it seems only the newer virt-viewer 2.0 on CentOS 6.7 is broken .. Both the c6 and c7 hosts have the same version of libvirt (1.2.15-3) from centos/xen repos: c7 (works OK): virt-viewer-0.6.0-12.el7.x86_64 xen-4.4.3-2.el7.x86_64 libvirt-daemon-1.2.15-3.el7.x86_64 libvirt-daemon-config-network-1.2.15-3.el7.x86_64 libvirt-daemon-driver-network-1.2.15-3.el7.x86_64 libvirt-daemon-driver-xen-1.2.15-3.el7.x86_64 libvirt-daemon-driver-storage-1.2.15-3.el7.x86_64 c6 (doesn't work): virt-viewer-2.0-7.el6.x86_64 xen-4.4.3-1.el6.x86_64 libvirt-daemon-config-nwfilter-1.2.15-3.el6.x86_64 libvirt-daemon-driver-interface-1.2.15-3.el6.x86_64 libvirt-daemon-driver-nwfilter-1.2.15-3.el6.x86_64 libvirt-daemon-driver-xen-1.2.15-3.el6.x86_64 libvirt-daemon-driver-secret-1.2.15-3.el6.x86_64 libvirt-daemon-driver-storage-1.2.15-3.el6.x86_64 libvirt-daemon-driver-network-1.2.15-3.el6.x86_64 libvirt-daemon-config-network-1.2.15-3.el6.x86_64 libvirt-daemon-driver-nodedev-1.2.15-3.el6.x86_64 libvirt-daemon-1.2.15-3.el6.x86_64 libvirt-daemon-driver-lxc-1.2.15-3.el6.x86_64 libvirt-daemon-driver-libxl-1.2.15-3.el6.x86_64 libvirt-daemon-driver-qemu-1.2.15-3.el6.x86_64 Thanks, -- Pasi