Virctl vnc failing intermittently

21 views
Skip to first unread message

Vishesh Tanksale

unread,
Jan 5, 2019, 6:33:37 PM1/5/19
to kubevirt-dev
Hi Team,

I am using KubeVirt v0.10.0. When I try to virtctl vnc into a vm, a window appears for a moment and disappears. I see the following message on terminal. 

[root@srv2 home]# ./virtctl vnc testvm-win
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:119","timestamp":"2019-01-05T15:28:44.496393Z"}
{"component":"virtctl","level":"info","msg":"remote-viewer connected in 133.247751ms","pos":"vnc.go:130","timestamp":"2019-01-05T15:28:44.629641Z"}
Error encountered: read tcp 127.0.0.1:40220->127.0.0.1:57210: read: connection reset by peer

After multiple attempts, virtctl is able to connect successfully. I have not been able to triage this. Any pointers as to how can I solve this issue?

Thanks,
Vishesh Tanksale

Marc Sluiter

unread,
Jan 7, 2019, 4:13:30 AM1/7/19
to Vishesh Tanksale, kubevirt-dev
Hi Vishesh,

you are probably running into this issue: virtctl vnc does not wait until the VM is ready, while virtctl console does. There is already a github issue for it:

Does this help?

Regards,

Marc


MARC SLUITER

SENIOR SOFTWARE ENGINEER

Red Hat GmbH

Werner-von-Siemens-Ring 14, 85630 Grasbrunn, Germany

Commercial register: Amtsgericht München, HRB 153243

mslu...@redhat.com    T: +49-211-95439679    M: +49-174-9902337    


--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To post to this group, send email to kubevi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/0133f42f-1375-4fc6-b096-c281a9cf9ab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Vishesh Tanksale

unread,
Jan 8, 2019, 3:39:53 PM1/8/19
to Marc Sluiter, kubevirt-dev

Hi Marc,

 

When I check the state of the VMI it shows ‘running’,but still the virtctl vnc throws the same error. I think the github issue you mentioned is about trying to vnc when the VMI state is ‘scheduling’.

 

Thanks,

Vishesh Tanksale

 

 

From: kubevi...@googlegroups.com <kubevi...@googlegroups.com> On Behalf Of Marc Sluiter
Sent: Monday, January 7, 2019 1:13 AM
To: Vishesh Tanksale <vtan...@nvidia.com>
Cc: kubevirt-dev <kubevi...@googlegroups.com>
Subject: Re: [kubevirt-dev] Virctl vnc failing intermittently

 

Hi Vishesh,

 

you are probably running into this issue: virtctl vnc does not wait until the VM is ready, while virtctl console does. There is already a github issue for it:

 

Does this help?

 

Regards,

 

Marc

 


MARC SLUITER

SENIOR SOFTWARE ENGINEER

Red Hat GmbH

Werner-von-Siemens-Ring 14, 85630 Grasbrunn, Germany

Commercial register: Amtsgericht München, HRB 153243

mslu...@redhat.com    T: +49-211-95439679    M: +49-174-9902337    

 

On Sun, Jan 6, 2019 at 12:33 AM Vishesh Tanksale <vtan...@nvidia.com> wrote:

Hi Team,

 

I am using KubeVirt v0.10.0. When I try to virtctl vnc into a vm, a window appears for a moment and disappears. I see the following message on terminal. 

 

[root@srv2 home]# ./virtctl vnc testvm-win

{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:119","timestamp":"2019-01-05T15:28:44.496393Z"}

{"component":"virtctl","level":"info","msg":"remote-viewer connected in 133.247751ms","pos":"vnc.go:130","timestamp":"2019-01-05T15:28:44.629641Z"}

Error encountered: read tcp 127.0.0.1:40220->127.0.0.1:57210: read: connection reset by peer

 

After multiple attempts, virtctl is able to connect successfully. I have not been able to triage this. Any pointers as to how can I solve this issue?

 

Thanks,

Vishesh Tanksale

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To post to this group, send email to kubevi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/0133f42f-1375-4fc6-b096-c281a9cf9ab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To post to this group, send email to kubevi...@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Marc Sluiter

unread,
Jan 9, 2019, 4:02:16 AM1/9/19
to Vishesh Tanksale, kubevirt-dev
Mh, ok. We need some more information then. Does virtctl console work? Can you please provide
- the output of virtctl vnc with --v=9 for more logging
- the VM(I) spec
- the logs of virt-api server
- the logs of virt-launcher of the VM

Thanks,

Marc

Reply all
Reply to author
Forward
0 new messages