Random Crashes from Windows Server 2016 VM

Thu, 22 Aug 2019 00:07:29 GMT

Hi All,

This was related to an expired evaluation licence on the template. I resolved the issue by upgrading to Server Standard. From an elevated command prompt:

PHP Code

 Dism /online /Set-Edition:ServerStandard /AcceptEula /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx 

Then reboot and the issue will disappear.

Random Crashes from Windows Server 2016 VM

Wed, 21 Aug 2019 07:35:11 GMT

Few days back, I was also going through the same. Some how, I manage to get this issue resolved by getting into contact with the best technicians at https://www.xgeeksquad.com/geek-squad-helpline/Geek Squad Helpline Number +1(888)383-7303. This might help you to get rid of the issue in least possible duration.

Random Crashes from Windows Server 2016 VM

Wed, 21 Aug 2019 06:50:42 GMT

Support have informed me this is most commonly caused by expired licensing in Windows. Have added a product key now and will update tomorrow with the outcome.

Wed, 21 Aug 2019 05:47:41 GMT

I have had issues with Windows Server 2016 VM's crashing randomly. These VM's have been created from Server 2016 templates provided by Virtualizor support.

The guest is indicating these are unexpected shutdowns, so the shutdown command is not being issued by the guest. The following appears in logs at the time of a shutdown

/var/log/libvirt/qemu/v1033.log

PHP Code

 2019-08-21T14:52:40.042210Z qemu-kvm: terminating on signal 15 from pid 8323 (/usr/sbin/libvirtd)

2019-08-21 14:52:40.331+0000: shutting down, reason=shutdown 

/var/log/messages

PHP Code

 Aug 21 14:52:01 kvm-kil-m-013 systemd: Started Session 1695 of user root.

Aug 21 14:52:05 kvm-kil-m-013 libvirtd: 2019-08-21 04:52:05.006+0000: 8323: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error

Aug 21 14:52:19 kvm-kil-m-013 libvirtd: 2019-08-21 04:52:19.012+0000: 8323: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error

Aug 21 14:52:32 kvm-kil-m-013 libvirtd: 2019-08-21 04:52:32.782+0000: 8323: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error

Aug 21 14:52:40 kvm-kil-m-013 kernel: viifbr0: port 2(viifv1033) entered disabled state

Aug 21 14:52:40 kvm-kil-m-013 kernel: device viifv1033 left promiscuous mode

Aug 21 14:52:40 kvm-kil-m-013 kernel: viifbr0: port 2(viifv1033) entered disabled state

Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.0703] device (viifv1033): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')

Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.0704] device (viifv1033): released from master device viifbr0

Aug 21 14:52:40 kvm-kil-m-013 kernel: viifbr1: port 2(vinfv1033) entered disabled state

Aug 21 14:52:40 kvm-kil-m-013 kernel: device vinfv1033 left promiscuous mode

Aug 21 14:52:40 kvm-kil-m-013 kernel: viifbr1: port 2(vinfv1033) entered disabled state

Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.1139] device (vinfv1033): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')

Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.1139] device (vinfv1033): released from master device viifbr1

Aug 21 14:52:40 kvm-kil-m-013 libvirtd: 2019-08-21 04:52:40.130+0000: 8323: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor

Aug 21 14:52:40 kvm-kil-m-013 kvm: 1 guest now active

Aug 21 14:52:40 kvm-kil-m-013 systemd-machined: Machine qemu-12-v1033 terminated.

Nothing is appearing in the admin panel logs for this VM at all, I am just coming back to find it powered off.

Are there any further logs for libvirt I have missed that may hold more insight?
Anyone else had similar issues?