action #17658
closedVNC reconnect feature needed for xen/svirt and stalled VNC connections
0%
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.
Updated by michalnowak almost 8 years ago
- Blocks action #10206: [tools]libvirt tests (Xen, Hyper-V, VMware) added
Updated by michalnowak almost 8 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
Updated by RBrownSUSE almost 8 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
Updated by michalnowak almost 8 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.
Updated by asmorodskyi over 7 years ago
Updated by okurz over 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
Updated by okurz over 7 years ago
- Has duplicate action #18550: [migration] test fails in first_boot with s390x zkvm-image worker added
Updated by coolo over 7 years ago
https://github.com/os-autoinst/os-autoinst/pull/764 as a test ballon
Updated by dzedro over 7 years ago
Build 0341 fails with considering VNC stalled - turning black
aarch64 yast_self_update
s390x allpatterns
Updated by SLindoMansilla over 7 years ago
It happened again on Build0348 on ppc64le and x86_64
Updated by coolo over 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
Updated by okurz over 7 years ago
- Status changed from New to In Progress
@michalnowak can you comment on what are the next steps?
Updated by michalnowak over 7 years ago
- Status changed from In Progress to Resolved