Windows 10 vm Freeze

[mamatov]

Hi,

On my proxmox cluster, I have a windows 10 VM.

Since one month, the VM has freezes 3 times. From the proxmox console I can't login (ctrl+alt+sup). The login page is stuck.

The only way to fix it is to stop/start the VM.

-------------------

pveversion :

pve-manager/4.4-13/7ea56165 (running kernel: 4.4.59-1-pve)

vm configuration :

bootdisk: virtio0
cores: 6
cpu: host
ide2: none,media=cdrom
memory: 4096
name: anne-srv
net0: virtio=2A:30:62:87:A8:96,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
smbios1: uuid=80e74279-6e80-4949-9445-f271f1a06f0a
sockets: 1
virtio0: vm-datastore:vm-125-disk-1,cache=writeback,size=100G

----------------------

Any idea to fix this issue ?

Thanks in advance.

 

[Alwin]

What is your system load on the PVE server? How is your storage configuration (/etc/pve/storage.cfg)?

If you use the [\CODE] blocks, then formatting stays. Found under the little plus in the editor.

 

[ktecho]

The same is happening to me.

Did your CPU goes to 100% too in Proxmox admin? I'm getting crazy to try and fix this.

I tried disabling ballooning, but it's still failing.

I was thinking the problem could be this one: https://bugzilla.kernel.org/show_bug.cgi?id=197449

I've contacted the guy who opened the bug report and he told me that using a 4.12 kernel solved its problem. I don't know if this could help.

The other change I'm gonna make is changing disks from VirtIO to IDE because I have read a lot of people with VirtIO SCSI problems, but I cannot do that until weekend.

My server has a CPU utilisation near 0 to 1%.

root@ns204651:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content rootdir,images,iso,vztmpl
        maxfiles 0

dir: backup
        path /vz/backup
        content backup
        maxfiles 2
        shared 0

dir: backupDiarios
        path /vz/backupDiarios
        content backup
        maxfiles 7
        shared 0

Any other tip?

 

[ktecho]

Wow... didn't read that reporter is using Proxmox 4.4 with an old kernel. So maybe a different problem, a change in Windows 10 or a problem with VirtIO drivers...

 

[mamatov]

Hi,

Thanks for these informations.

Today the windows 10 VM crashed again.

Before the crash, the load average of the PVE server was around "4".
This is due to the cpu usage of the windows 10 vm (50% of 6 vCPU)

Please see below the cpu usage of the windows VM for the last month :

I restarted the VM (stop/start). After the PVE load is between 1 and 2.

I will check why this VM is consumming a lot of CPU all the time.

My storage configuration :

dir: local
        path /var/lib/vz
        content images,rootdir,iso,vztmpl
        maxfiles 0

iscsi: iscsi_c0_p0
        portal 10.1.1.101
        target iqn.1984-05.com.dell:powervault.md3800i.600a09800065589f0000000054d8ee83
        content none

iscsi: iscsi_c1_p0
        portal 10.1.1.102
        target iqn.1984-05.com.dell:powervault.md3800i.600a09800065589f0000000054d8ee83
        content none

lvm: vm-datastore
        vgname LUN0
        content images
        shared 1

iscsi: iscsi_c0_p1
        portal 10.1.2.101
        target iqn.1984-05.com.dell:powervault.md3800i.600a09800065589f0000000054d8ee83
        content none

nfs: nfs-hercule
        export /vm-backup/prod
        path /mnt/pve/nfs-hercule
        server 192.168.10.200
        content backup
        maxfiles 1
        options vers=3

nfs: nfs-hercule-test
        export /vm-backup/test
        path /mnt/pve/nfs-hercule-test
        server 192.168.10.200
        content backup
        maxfiles 1
        options vers=3

Regarding virtio driver, can I upgrade this driver safetly ?
Maybe your are right ktecho, I will try to migrate to ide if the problem persist.

 

[Alwin]

Regarding virtio driver, can I upgrade this driver safetly ?

It is always advisable to do a backup. Usually a upgrade is done as with other drivers. You also should get to the latest Windows Updates, as Microsoft is also fixing bugs in regards to virtualization.