Windows 10 VM boot delay

[frankz]

Hello everyone, I have a proxmox node with the following packages installed:

proxmox-ve: 6.4-1 (running kernel: 5.4.174-2-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-15
pve-kernel-helper: 6.4-15
pve-kernel-5.4.174-2-pve: 5.4.174-2
pve-kernel-5.4.166-1-pve: 5.4.166-1
pve-kernel-5.4.162-1-pve: 5.4.162-2
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1

In recent days, I realized that a Windows 10 VM, during boot, took about 7 mn to complete the complete boot phase, i.e. startup and login mask. I tried to check in the virtual PC that services or anything else prevented them from starting correctly.

Instead, for pure randomness, for example by rebooting from windows users the defect occurs, on the contrary if the user shuts down the VM, and from proxmox it restarts it, the machine takes about 30 seconds to boot.

I think something in memory or something else remains "dirty" at the reboot, but mine is just a doubt!
I've done this test several times, and it seems like that's right.

 

[oguz]

hi,

In recent days, I realized that a Windows 10 VM, during boot, took about 7 mn to complete the complete boot phase, i.e. startup and login mask. I tried to check in the virtual PC that services or anything else prevented them from starting correctly.

that's weird for sure.
* does the VM work slowly after boot is completed?
* what kind of disk are you using on the host? (e.g. where the VM is stored)

could you also post the VM configuration? qm config <VMID> (replace VMID with yours)

also:

proxmox-ve: 6.4-1 (running kernel: 5.4.174-2-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)

your package version is old, maybe you should think about upgrading to get the latest bug and security fixes? [0]

[0]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[frankz]

hi,


that's weird for sure.
* does the VM work slowly after boot is completed?
* what kind of disk are you using on the host? (e.g. where the VM is stored)

could you also post the VM configuration? qm config <VMID> (replace VMID with yours)

also:

proxmox-ve: 6.4-1 (running kernel: 5.4.174-2-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)

your package version is old, maybe you should think about upgrading to get the latest bug and security fixes? [0]

[0]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

Hi. And thank you for answering.
Here is the cfg:

root@pve:~# qm config 101
agent: 1,type=virtio
boot: order=ide0;ide1;net0
cores: 2
cpu: host
ide0: local1tb:101/vm-101-disk-0.raw,size=64G
ide1: none,media=cdrom
machine: pc-i440fx-5.2
memory: 3072
name: win10
net0: virtio=22:DC:15:33:5A:CE,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
protection: 1
scsihw: virtio-scsi-pci
smbios1: uuid=9e68ed63-1297-4642-8a1c-0e0c507d0008
sockets: 1
tablet: 1
vmgenid: 2b1d147e-f69c-494a-a565-1f1316058d38
vmstatestorage: local1tb

As for the update, I am fully aware of the version progress, but at the moment it remains the one in place.

 

[oguz]

As for the update, I am fully aware of the version progress, but at the moment it remains the one in place.

okay

Here is the cfg:

do you have the virtio drivers [0] [1] installed on the VM?
it could help if you do that, and use virtio devices for the disks instead of IDE (you'd get better performance)

* does the VM work slowly after boot is completed?
* what kind of disk are you using on the host? (e.g. where the VM is stored)

also it would help if you can answer the above questions as well

[0]: https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
[1]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

 

[frankz]

okay


do you have the virtio drivers [0] [1] installed on the VM?
it could help if you do that, and use virtio devices for the disks instead of IDE (you'd get better performance)


also it would help if you can answer the above questions as well

[0]: https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
[1]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

Hello, yes, of course when I install or rather create a VM I install the virtio drivers in particular .iso.

 

[oguz]

Hello, yes, of course when I install or rather create a VM I install the virtio drivers in particular .iso.

in that case please try to switch the disks from ide to virtio and check if it makes a difference.

you haven't answered:
* does the VM work slowly after boot is completed?
* what kind of disk are you using on the host? (e.g. where the VM is stored)

 

[frankz]

* does the VM work slowly after boot is completed?

Vm work badly if they are restarted by the same VM e.g. users reboot windows 10 ( result = slowness to reboot windows). If the VM user shuts down the system e.g. turn off the PC from windows and then from proxmox restart the VM works great, boot time 30 sec. The node always remains active, I only referred to the windows 10 VM used by the user.

* what kind of disk are you using on the host? (e.g. where the VM is stored)

The VM is stored on a 7200 rpm SATA local disk

 

[frankz]

Hello everyone, the problem of the boot speed of vm windows continues to occur. It also takes 5 mn for the complete restart.

 

[frankz]

Is it possible that there is the same problem in different VMs?