Windows Server becomes unresponsive

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

Parth Gandhi
16 ●7 ●10 ●12

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?

https://kb.vmware.com/selfservice/mic...

edit retag flag offensive close merge delete

add a comment

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

avladu

613 ●1 ●3 ●5

Hello,

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

Thanks,

Adrian Vladu

edit flag offensive delete link

Comments

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

Parth 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 ( 2016-10-20 00:04:58 +0300 )edit

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

Parth 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 ( 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 ( 2016-11-29 11:22:49 +0300 )edit

hi Adrian, apologize to have been missed out mentioning live migration in actual post. Yes, we face this issue post live migration. We are using Openstack Juno with KVM and libvirt. I tested it with new drivers and still facing this issue. The VM having this issues are using QCOW2 images.

Parth Gandhi ( 2016-12-05 08:34:28 +0300 )edit

Hi, I might have found a possible reason for your issue. Can you try to run this powershell/cmd on the Windows instance before you migrate it:

powercfg.exe /S "8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c"

Thank you,
Adrian Vladu

avladu ( 2016-12-06 19:37:41 +0300 )edit

Hi Adrian, I tried changing the power option to high performance using above command and did a live migration, however the instance got stuck again after migration. I saw the below compute logs on the host that it was migrated.

Parth Gandhi ( 2016-12-07 08:27:23 +0300 )edit

DEBUG nova.virt.libvirt.driver [req-03d85ee3-04ba-4287-8ff4-d571138bbaaf None] [instance: ID] Could not determine fibre channel world wide node names get_volume_connector /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py:1282

Parth Gandhi ( 2016-12-07 08:28:29 +0300 )edit

see more comments

Windows Server becomes unresponsive

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

Windows Server becomes unresponsive edit

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

Windows Server becomes unresponsive