New Question

Windows Server becomes unresponsive

asked 2016-10-12 09:11:37 +0300

Parth Gandhi gravatar image

Hi, I have couple of windows VM (running on KVM) which becomes unresponsive - ping status works however RDP does not work and horizon console just shows a black screen. The only way to get this up and running is to do a soft reboot from the console. I did it on few VM's and checked the event log. I did not find any error message except few warning for VIOSTOR with event ID 129- Reset to device, \Device\RaidPort0, was issued. On researching further on this event came across certain article where users have faced such issues on hyper-v and VMware(link below for VMware KB) and the suggestion is to change the controller from scsi to IDE.

Can this be an issue in our case as well on KVM?

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2016-10-13 20:10:08 +0300

avladu gravatar image


Please check the MTU size set by your dhcp server. If you are using tunneling it should be somewhere around 1450.


Adrian Vladu

edit flag offensive delete link more


Hi Adrian, we do not have any tunneling setup in our environment./ Thanks.

Parth Gandhi gravatar imageParth Gandhi ( 2016-10-19 12:44:24 +0300 )edit

can you put in a pastebin the output of the command "ps ax|grep kvm" from a kvm compute node? and what virtio drivers are you using?

avladu gravatar imageavladu ( 2016-10-20 00:04:58 +0300 )edit

Hi, I am using Red hat VirtIO driver(0.1.102) ver=03/10/2015, Below is the result of the ps ax|grep kvm command.

Parth Gandhi gravatar imageParth Gandhi ( 2016-11-02 11:54:18 +0300 )edit

We continue to face the same issue on the windows VM. Initially we found that the balloon drivers were not installed on affected VM and we installed it on all the VM. However this does not seem to have fixed the issue and few VM still becomes unresponsive after live migration.

Parth Gandhi gravatar imageParth Gandhi ( 2016-11-29 08:26:23 +0300 )edit

You can try creating an image using the improved windows-openstack-imaging-tools with the new 0.1.126 stable virtio drivers, this might solve the issues you are having. Moreover, can you give a detailed view of your environment? As this is the first time you mentioned live migration issues. Thanks

avladu gravatar imageavladu ( 2016-11-29 11:22:49 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-10-12 09:11:37 +0300

Seen: 377 times

Last updated: Oct 13 '16