Windows Guest suddenly stops

[jbaileypro]

Hi all,

I've recently updated our main VM server to version 4.4 and also create a new VM which is a terminal server.

It very strangely stopped today while people were working on it. When I checked proxmox web gui it showed the VM as stopped and displayed nothing in the task history.

I've also checked the event viewer which didn't display anything about the "power loss" until the machine booted back up and first message was that it wasn't shut down cleanly.

Is there anywhere I can look to help diagnose why this happened? No other VMs stopped during this time (some which have been running for months) and no hardware changed during this time.

All hard drives and networking is Virtio using the latest drivers. Guest is Windows 7 pro. Ballooning isn't installed and guest software isn't either.

Many thanks,

 

[wolfgang]

Hi,

you can hav a look in the syslog and journal

the syslog is located in
/var/log/syslog

the journal of the vm you get with

journalctl -u <VMID>.scope

 

[valeech]

I had the exact same thing happen on 7/27. Windows is 2012R2, virtio disk and nic with quest agent installed.

root@pve20:~# pveversion -v
proxmox-ve: 4.4-77 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-5 (running version: 4.4-5/c43015a5)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.35-1-pve: 4.4.35-77
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-102
pve-firmware: 1.1-10
libpve-common-perl: 4.0-85
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-71
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-10
pve-container: 1.0-90
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-5
lxcfs: 2.0.5-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

The only thing in syslog is:
Jul 27 00:04:21 pve20 kernel: [17456543.428268] vmbr1: port 2(tap105i0) entered disabled state
Jul 27 00:04:21 pve20 kernel: [17456543.428932] vmbr1: port 2(tap105i0) entered disabled state


and journalctl -u 105.scope gives:

-- Logs begin at Thu 2017-01-05 21:45:50 EST, end at Wed 2017-08-02 10:03:12 EDT. --
Jan 06 11:36:41 pve20 systemd[1]: Starting 105.scope.
Jan 06 11:36:41 pve20 systemd[1]: Started 105.scope.
Jan 06 11:41:52 pve20 systemd[1]: Starting 105.scope.
Jan 06 11:41:52 pve20 systemd[1]: Started 105.scope.
Jan 06 19:04:59 pve20 systemd[1]: Starting 105.scope.
Jan 06 19:04:59 pve20 systemd[1]: Started 105.scope.
Jan 06 19:09:59 pve20 systemd[1]: Starting 105.scope.
Jan 06 19:09:59 pve20 systemd[1]: Started 105.scope.
Jan 06 20:46:29 pve20 systemd[1]: Starting 105.scope.
Jan 06 20:46:29 pve20 systemd[1]: Started 105.scope.
Feb 13 22:29:16 pve20 systemd[1]: Starting 105.scope.
Feb 13 22:29:16 pve20 systemd[1]: Started 105.scope.
Jul 27 08:24:48 pve20 systemd[1]: Starting 105.scope.
Jul 27 08:24:48 pve20 systemd[1]: Started 105.scope.

Is there anything else I can look for?

 

[koval]

Hello!
The same story here. Suddenly stops without any clear reason.
Any solution?

 

[JPPWeber]

Hello,

i dig this out cause i have nearly the same issue.

User starts db repair program
VM stops
BUT is marked as running, vm symbol is gray and is locked like a backup is running.

It can be reproduced.

"Workaround" after it happended:
qm unlock 100
qm stop 100
qm start 100

Syslog says nothing about the error and the scope also nothing.

Windows only says it wasnt shutdown properly.

Spoiler: pveversion

proxmox-ve: 5.1-35 (running kernel: 4.13.13-4-pve)
pve-manager: 5.1-42 (running version: 5.1-42/724a6cb3)
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-19
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9