Project

General

Profile

Actions
Copy link

action #17658

closed

VNC reconnect feature needed for xen/svirt and stalled VNC connections

Added by michalnowak about 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2017-03-10
Due date:
% Done:

0%

Estimated time:

Description

Because Xen resets guest's VNC connection, we have couple of following provisions for Xen over svirt to make sure we have a live VNC connection after guest restarts:

    script_run 'reboot';
    reset_consoles;
    if (check_var('VIRSH_VMM_FAMILY', 'xen')) {
        sleep 4;
        select_console 'sut';
    }

That is: when the system is restarting, reset consoles, wait some time and re-connect to 'sut' console, when the system is booting. Of course this is prone to fail as we don't know how long to wait.

Decent workaround would be wait_serial for serial device output from GRUB. But a proper one seems to me a VNC reconnect feature in os-autoinst, via polling or DOM events. virt-install has it: https://github.com/SPICE/virt-viewer/blob/master/src/virt-viewer.c.

Related issues 2 (0 open — 2 closed)

Has duplicate openQA Tests - action #18550: [migration] test fails in first_boot with s390x zkvm-image workerRejectedokurz2017-04-13

Actions
Blocks openQA Tests - action #10206: [tools]libvirt tests (Xen, Hyper-V, VMware)Resolvedmichalnowak2016-01-13

Actions
Actions
Copy link
 #1

Updated by michalnowak about 7 years ago

  • Blocks action #10206: [tools]libvirt tests (Xen, Hyper-V, VMware) added
Actions
Copy link
 #2

Updated by michalnowak about 7 years ago

  • Subject changed from VNC reconnect feature needed to Xen and stalled VNC connection to VNC reconnect feature needed for Xen and stalled VNC connections
Actions
Copy link
 #3

Updated by RBrownSUSE about 7 years ago

Wouldn't a better option be to file a bug against Xen? I do not think it should reset the guests VNC connection

Actions
Copy link
 #4

Updated by michalnowak about 7 years ago

It's not just a VNC but a serial console connection is well. I believe the connection close is deliberate, hence the virt-viewer's --reconnect option.

Actions
Copy link
 #5

Updated by coolo about 7 years ago

  • Assignee set to coolo
Actions
Copy link
 #7

Updated by okurz almost 7 years ago

  • Subject changed from VNC reconnect feature needed for Xen and stalled VNC connections to VNC reconnect feature needed for xen/svirt and stalled VNC connections
Actions
Copy link
 #8

Updated by okurz almost 7 years ago

  • Has duplicate action #18550: [migration] test fails in first_boot with s390x zkvm-image worker added
Actions
Copy link
 #10

Updated by dzedro almost 7 years ago

Build 0341 fails with considering VNC stalled - turning black
aarch64 yast_self_update
s390x allpatterns

Actions
Copy link
 #12

Updated by coolo almost 7 years ago

  • Assignee deleted (coolo)

I did the reconnect feature for stalled VNC - and told Michal how to disable a VNC console before disconnect to force a reconnect. I don't know of anything else I can do atm

Actions
Copy link
 #13

Updated by okurz almost 7 years ago

  • Status changed from New to In Progress

@michalnowak can you comment on what are the next steps?

Actions
Copy link
 #14

Updated by michalnowak almost 7 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF