Help on Windows VM - Booting from hard disk...

[rec0veryyy]

Hello, I have a small problem to see if you can help me, it turns out that every morning when I turn on my server all the virtual machines run both linux (I have 5) as a windows server, all start well but almost always the windows is stagnating on this screen, do you know why it can be?
The only thing that occurs to me is that as they start all at once this one stays like this but I do not know if it is nonsense what I just said or not, when it stays on this screen the cpu of the vm is at 25% because it can not move forward, if I turn off the machine and turn it on again bootea windows without problem.

PS: in the image it says opensuse, this ignore it as it is an image that I got from google that someone also happened, the issue is the black screen with the message: "Booting from hard disk..." and use SeaBIOS

 

[Moayad]

Hi,

Can you please post the output of the following commands:

qm config <VMID>
cat /etc/pve/storage.cfg
pveversion -v

I would also check if you set a "Startup delay" for the VMs mentioned, this will do the trick? To set a "Startup delay" you can go to the Proxmox VE Web UI -> VM -> Options -> Start/Shutdown order

 

[rec0veryyy]

qm config 109

agent: 1
args: -vnc 0.0.0.0:77
boot: order=scsi0;net0;ide0
cores: 4
cpu: host
description: args%3A -vnc 0.0.0.0%3A78
ide0: isos:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 8192
meta: creation-qemu=7.2.0,ctime=1679086674
name: WindowsGameServers
net0: virtio=8A:34:90:A7:1A:02,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
parent: ee
scsi0: vmstore:vm-109-disk-0,cache=writeback,iothread=1,size=70G
scsihw: virtio-scsi-single
smbios1: uuid=b3b88107-7673-4c04-b514-11f91e808717
sockets: 1
startup: up=10
vga: qxl,memory=128
vmgenid: 8d633416-9a82-4edd-9918-9c2fc49819c8

cat /etc/pve/storage.cfg

dir: local
    path /var/lib/vz
    content snippets
    shared 0

lvmthin: local-lvm
    thinpool data
    vgname pve
    content rootdir,images

lvmthin: vmstore
    thinpool vmstore
    vgname vmstore
    content rootdir,images
    nodes pve

dir: isos
    path /isos
    content iso,vztmpl
    shared 0

lvmthin: WDB_DATA
    thinpool WDB_DATA
    vgname WDB_DATA
    content images,rootdir
    nodes pve

lvmthin: almacen1
    thinpool almacen1
    vgname almacen1
    content images,rootdir
    nodes pve

pveversion -v

pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-6.2: 7.4-1
pve-kernel-5.15: 7.4-1
pve-kernel-6.2.9-1-pve: 6.2.9-1
pve-kernel-6.2.6-1-pve: 6.2.6-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

PD: I changed in vm options the start to 10s and today when I woke up and turned it on there was no problem and did not show that screen, it has started well, is it possible that it was because of that and that when all the machines started the windows machine was harmed and stayed in the boot caught?

 

[Moayad]

Hi,

Thank you for the output!

I changed in vm options the start to 10s and today when I woke up and turned it on there was no problem and did not show that screen, it has started well

Everything looks good for me from the above outputs, however, I would test for a few days.

is it possible that it was because of that and that when all the machines started the windows machine was harmed and stayed in the boot caught?

Hard to say without more digging into the issue. So please keep your eyes on it and see if the issue happens again. If it does, please provide us with the syslog since you started the Proxmox VE server by issuing the below command, and attach the syslog.txt.

journalctl -b > /tmp/syslog.txt