SPICE connect time out. No firewall. Same network.

M

mainprog

New Member
Sep 6, 2013
18
0
1
I've tried to connect to my VMs using SPICE.
But getting that thing:

c:\Users\alex\Downloads>"C:\Program Files\VirtViewer\bin\remote-viewer.exe" --debug spiceproxy.vv

c:\Users\alex\Downloads>(remote-viewer.exe:7048): remote-viewer-DEBUG: Insert window 0 00000000008DC000
(remote-viewer.exe:7048): remote-viewer-DEBUG: fullscreen display 0: 0
(remote-viewer.exe:7048): remote-viewer-DEBUG: Opening display to spiceproxy.vv
(remote-viewer.exe:7048): remote-viewer-DEBUG: Guest spiceproxy.vv has a spice display
(remote-viewer.exe:7048): remote-viewer-DEBUG: After open connection callback fd=-1
(remote-viewer.exe:7048): remote-viewer-DEBUG: Opening connection to display at spiceproxy.vv
(remote-viewer.exe:7048): remote-viewer-DEBUG: New spice channel 0000000003242120 SpiceMainChannel 0
(remote-viewer.exe:7048): remote-viewer-DEBUG: Checking full screen auto-conf
(remote-viewer.exe:7048): remote-viewer-DEBUG: auto-conf disabled
(remote-viewer.exe:7048): remote-viewer-DEBUG: notebook show status 00000000008DB150

(remote-viewer.exe:7048): GSpice-WARNING **: Socket I/O timed out
(remote-viewer.exe:7048): remote-viewer-DEBUG: main channel: failed to connect
(remote-viewer.exe:7048): remote-viewer-DEBUG: Disposing window 00000000008DC000

(remote-viewer.exe:7048): remote-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0


Versions:
pve-cluster 3.0-8
pve-firmware 1.0-23
pve-kernel-2.6.32-26-pve 2.6.32-114
pve-libspice-server1 0.12.4-2
pve-manager 3.1-21
pve-qemu-kvm 1.4-17


When I check tcpdump on server I see packets in both directions.
 
When running proxy in debug I see that:

root@kvm1:~# /usr/bin/spiceproxy --debug


685813: ACCEPT FH12 CONN1
685813: CONNECT 106, kvm1, 61000
685813: CONNECTed to '127.0.0.1:61000'
close connection AnyEvent::Handle=HASH(0x397dc18)
685813: CLOSE FH12 CONN0
 
If you're using PVE spice console, beware that this has a ticket based access system, which expires very soon.
You won't be able to connect permanently using thos .vv files you downloaded.
Their intended use is: open them with spice viewer, not download and store them as a permament way to conenct to vm.

To do that, you must install spice server into your vm (not windows, of course, use rdp for that).

Marco
 
m.ardito said:
If you're using PVE spice console, beware that this has a ticket based access system, which expires very soon.
You won't be able to connect permanently using thos .vv files you downloaded.
Their intended use is: open them with spice viewer, not download and store them as a permament way to conenct to vm.

To do that, you must install spice server into your vm (not windows, of course, use rdp for that).

Marco
Click to expand...

I know that :) You have 30 sec.
If file is expired you will get an error about ticket.

So I was doing download file and connecting immediately.


Thank you for your answer.
 
I am using SPICE from Proxmox UI.
Debug I've made to have some additional info.
In general when I click the SPICE button I am getting error that viwer can not connect to graphical server.
 

Attachments

  • spice.jpg
    spice.jpg
    34.1 KB · Views: 56
I don't undetsnad how to use that feature from the box?
SPICE is broken in Proxmomx 3.1?
 
well no, afaict, it is working really simply for me, at least from win7x64sp1, virt-viewer 0.5.7 x64.
as for pve:
Code: 
~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Marco
 
Mine is the same.
I have two fresh nodes.
Non of vms working with SPICE. What I am missing?


Code: 
root@kvm1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
I'm sorry but I don't know how to debug...

perhaps you could
- updating pve packages (who knows)
- ask the spice/virt-viewer people... perhaps try to show them logs...
- try a standard physical spice server, and debug connection to that (excluding pve)

Marco
 
I know it's an old thread, but as it does fit best...

I try to connect to spice, but no luck. So far: I've set up Proxmox VE 5.1 new today just as shipped from setup ISO (just in case there was a bug in my test installation). I've set up a Windows 7 professional x64 VM with virtio and switched graphic card to spice. Within Windows VM I can see there is a Red Hat QXL GPU, so I think I got the VM part correct.
But Proxmox does not open a spice console when clicking the default Console link, but opens a noVNC console.
If using the spice console link, I get the ticket downloaded and opened in virt_viewer, but the connection is not established. Debug:

"c:\Program Files\VirtViewer v6.0-256\bin\remote-viewer.exe" --debug UkkQJnWr.vv

(remote-viewer.exe:9244): Gtk-WARNING **: Could not find signal handler 'virt_viewer_window_menu_change_cd_activate'. Did you compile with -rdynamic?
(remote-viewer.exe:9244): virt-viewer-DEBUG: Opening display to UkkQJnWr.vv
(remote-viewer.exe:9244): virt-viewer-DEBUG: Guest (NULL) has a spice display
(remote-viewer.exe:9244): virt-viewer-DEBUG: ignoring [ovirt] section content as URL, VM GUID are missing from the .vv file
(remote-viewer.exe:9244): virt-viewer-DEBUG: After open connection callback fd=-1
(remote-viewer.exe:9244): virt-viewer-DEBUG: Opening connection to display at UkkQJnWr.vv
(remote-viewer.exe:9244): virt-viewer-DEBUG: New spice channel 000000000649B360 SpiceMainChannel 0
(remote-viewer.exe:9244): virt-viewer-DEBUG: notebook show status 00000000062F5840
(remote-viewer.exe:9244): virt-viewer-DEBUG: main channel: failed to connect Socket I/O timed out
(remote-viewer.exe:9244): virt-viewer-DEBUG: Destroy SPICE channel SpiceMainChannel 0
(remote-viewer.exe:9244): virt-viewer-DEBUG: zap main channel

I can see the attempt to connect in /var/log/pveproxy/access.log, however, I don't ever see a real connection.

Sure I make some mistakes, but...?

Should the Proxmox host be available via spice? In fact, the spice option is available, but here too, no connection is established ("Socket I/O timed out").

I have to admit, that I do not have a valid subscription yet, as I do only use Proxmox in private and as a fun project, but I couldn't find a hint that this would cause spice not to work.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back