Re: [Bug 1894818] [NEW] COLO's guest VNC client hang after failover

[Lukas Straub <1894818@bugs.launchpad.net>]

On Tue, 08 Sep 2020 10:25:52 -0000
Launchpad Bug Tracker <1894818@bugs.launchpad.net> wrote:

> You have been subscribed to a public bug by Derek Su (dereksu):
> 
> Hello,
> 
> After setting up COLO's primary and secondary VMs,
> I installed the vncserver and xrdp (apt install tightvncserver xrdp) inside the VM.
> 
> I access the VM from another PC via VNC/RDP client, and everything is OK.
> Then, kill the primary VM and issue the failover commands.
> 
> The expected result is that the VNC/RDP client can reconnect and resume
> automatically after failover. (I've confirmed the VNC/RDP client can
> reconnect automatically.)
> 
> But in my test, the VNC client's screen hangs and cannot be recovered no
> longer. (I need to restart VNC client by myself.)
> 
> BTW, it works well after killing SVM.
> 
> Here is my QEMU networking device
> ```
> -device virtio-net-pci,id=e0,netdev=hn0 \
> -netdev tap,id=hn0,br=br0,vhost=off,helper=/usr/local/libexec/qemu-bridge-helper \
> ```
> 
> Thanks.
> 
> Regards,
> Derek
> 
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
> 

Hello,
Can you show the full qemu command line?

Regards,
Lukas Straub

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894818

Title:
  COLO's guest VNC client hang after failover

Status in QEMU:
  New

Bug description:
  Hello,

  After setting up COLO's primary and secondary VMs,
  I installed the vncserver and xrdp (apt install tightvncserver xrdp) inside the VM.

  I access the VM from another PC via VNC/RDP client, and everything is OK.
  Then, kill the primary VM and issue the failover commands.

  The expected result is that the VNC/RDP client can reconnect and
  resume automatically after failover. (I've confirmed the VNC/RDP
  client can reconnect automatically.)

  But in my test, the VNC client's screen hangs and cannot be recovered
  no longer. I need to restart VNC client by myself.

  BTW, it works well after killing SVM.

  Here is my QEMU networking device
  ```
  -device virtio-net-pci,id=e0,netdev=hn0 \
  -netdev tap,id=hn0,br=br0,vhost=off,helper=/usr/local/libexec/qemu-bridge-helper \
  ```

  Thanks.

  Regards,
  Derek

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1894818/+subscriptions