[
https://issues.apache.org/jira/browse/CLOUDSTACK-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128131#comment-14128131
]
ASF subversion and git services commented on CLOUDSTACK-6898:
-------------------------------------------------------------
Commit 4c9507d21e82e9c55ac64e75165329565ec6a14f in cloudstack's branch
refs/heads/master from [~anshulg]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4c9507d ]
CLOUDSTACK-6898: [Hyper-V] fixed rdp console freezing during reboot.
Console was freezing because we read data from socket in blocking mode.
During reboot it was blocking infintely.
To fix issue, now we are reading data in non-blocking mode.
In non-blocking mode I set the timeout to 5 seconds.
> [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from
> inside the console), the console gets stuck at a point.
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6898
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6898
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.4.0
> Environment: Hyper-V
> Reporter: Abhinav Roy
> Assignee: Anshul Gangwar
> Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
> Attachments: CS-6898.jpg
>
>
> Steps :
> ==============
> 1. Deploy a Hyper-V setup with advanced zone.
> 2. Deploy a VM.
> 3. Now open the console of the VM from CS UI.
> 4. Now reboot the VM from CS or from inside the console of VM
> Expected behavior :
> ===============
> 1. The console should be accessible when the the VM is rebooting and after it
> boots up.
> Observed behavior :
> ==============
> The console gets stuck at the point of stopping the VM and remains in that
> state.
> Even if you close the console and reopen , it remains in the same state.
> Attaching a screenshot for that.
> Workaround :
> ============
> Either close the console or even in the open state don't do any activity on
> it for 3 mins. After that it becomes accessible again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
