Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Random Crashes from Windows Server 2016 VM



Normal Mode | Print  

 Random Crashes from Windows Server 2016 VM (3 Replies, Read 1273 times)
m9shyamalan
Group: Member
Post Group: Newbie
Posts: 14
Status:
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-kvmterminating on signal 15 from pid 8323 (/usr/sbin/libvirtd)
2019-08-21 14:52:40.331+0000shutting downreason=shutdown 



/var/log/messages
PHP Code

 Aug 21 14:52:01 kvm-kil-m-013 systemdStarted Session 1695 of user root.
Aug 21 14:52:05 kvm-kil-m-013 libvirtd2019-08-21 04:52:05.006+00008323error virNetSocketReadWire:1806 End of file while reading dataInput/output error
Aug 21 14
:52:19 kvm-kil-m-013 libvirtd2019-08-21 04:52:19.012+00008323error virNetSocketReadWire:1806 End of file while reading dataInput/output error
Aug 21 14
:52:32 kvm-kil-m-013 libvirtd2019-08-21 04:52:32.782+00008323error virNetSocketReadWire:1806 End of file while reading dataInput/output error
Aug 21 14
:52:40 kvm-kil-m-013 kernelviifbr0port 2(viifv1033entered disabled state
Aug 21 14
:52:40 kvm-kil-m-013 kerneldevice viifv1033 left promiscuous mode
Aug 21 14
:52:40 kvm-kil-m-013 kernelviifbr0port 2(viifv1033entered disabled state
Aug 21 14
:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.0703device (viifv1033): state changedisconnected -> unmanaged (reason 'unmanaged'sys-iface-state'removed')
Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.0704device (viifv1033): released from master device viifbr0
Aug 21 14
:52:40 kvm-kil-m-013 kernelviifbr1port 2(vinfv1033entered disabled state
Aug 21 14
:52:40 kvm-kil-m-013 kerneldevice vinfv1033 left promiscuous mode
Aug 21 14
:52:40 kvm-kil-m-013 kernelviifbr1port 2(vinfv1033entered disabled state
Aug 21 14
:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.1139device (vinfv1033): state changedisconnected -> unmanaged (reason 'unmanaged'sys-iface-state'removed')
Aug 21 14:52:40 kvm-kil-m-013 NetworkManager[7355]: <info>  [1566363160.1139device (vinfv1033): released from master device viifbr1
Aug 21 14
:52:40 kvm-kil-m-013 libvirtd2019-08-21 04:52:40.130+00008323error qemuMonitorIO:718 internal errorEnd of file from qemu monitor
Aug 21 14
:52:40 kvm-kil-m-013 kvm1 guest now active
Aug 21 14
:52:40 kvm-kil-m-013 systemd-machinedMachine 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?
IP: --   


Threads
 m9shyamalan   Random Crashes from Windows Server 2016 VM (3 Replies, Read 1273 times)
    |--  m9shyamalan   Support have informed...   on August 21, 2019, 6:50 am
    |--  augustaliliana   Few days back,...   on August 21, 2019, 7:35 am
    |--  m9shyamalan   Hi All, This...   on August 22, 2019, 12:07 am

« Previous    Next »

Normal Mode | Print  



Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is October 15, 2019, 9:32 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.215