Advanced Proxmox beginner finds a bug?

MALEFX

New Member
Nov 3, 2023
10
2
3
Hello Proxmox community

I recently installed this amazing software and ran into a strange problem:
Proxmox 8 latest version clean installation and updated
I installed several virtual machines, all working perfectly and without problems, until the installation of yet another virtual machine, WINDOWS 10 LTSC
I installed windows in UEFI and also tried legacy mode
VIRTIO drivers installed and agent installed.
From WINDOWS prompt i send powercfg -H off
Everything seems to run perfectly until the system dies randomly.
I did several TESTS, NOTHING.
So I thought about a hardware problem with this industrial PC and decided to do the same test on a new INTEL NUC machine
On the NUC I installed a new proxmox 8 clean install with all the updates and strangely I have the exact same problem.
I then decided, again on the NUC where there are no other virtual systems, to install a Windows 10 PRO with the exact same configuration as LTSC and magically the problem did not occur.
Can someone help me?
Is it a BUG? WINDOWS 10 LTSC doesn't want to go.
I do not know what to do
Possibly tell me all the commands to run to send you the LOG and help me understand the problem
I thank everyone in advance and I hope someone can help me

Thank you PROXMOX community
 
Hallo,

eventuell sendet die VM ein Signal an das BIOS, weshalb sich der Host abschaltet. Ich habe noch nie mit powercfg in VMs gearbeitet.
 
hello
the powercfg command is just a command given to windows to make sure to disable hibernation, nothing else.
Proxmox has some problems with Windows LTSC and it seems strange to me that no one has noticed....
 
hello
the powercfg command is just a command given to windows to make sure to disable hibernation, nothing else.
Proxmox has some problems with Windows LTSC and it seems strange to me that no one has noticed....
Post your VM config please. About 50 LTSC-VMs here running perfectly under 8.0.4....
 
  • Like
Reactions: proxifoxi
agent: 1
bios: ovmf
boot: order=scsi0;net0
cores: 4
cpu: host
efidisk0: ssd:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
machine: pc-q35-8.0
memory: 8192
meta: creation-qemu=8.0.2,ctime=1699611541
name: Win10-LTSC
net0: virtio=2A:6B:28:57:B2:B0,bridge=vmbr0
numa: 0
ostype: win10
scsi0: ssd:vm-104-disk-1,cache=writeback,discard=on,iothread=1,size=1500G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=9b8d8b79-feb9-477e-9acc-094d0158c7e3
sockets: 1
vmgenid: d2b39ac5-ad35-4fb8-824a-a26d182498f2
 
I did not even know a windows LTSC existed ;) Downloading it now

Do i understand correctly that your proxmox stops working when you shutdown that windows ltsc vm?
does Proxmox hang or crash and reboot?
 
I did not even know a windows LTSC existed ;) Downloading it now

Do i understand correctly that your proxmox stops working when you shutdown that windows ltsc vm?
does Proxmox hang or crash and reboot?
Meanwhile, thanks for the reply.
No, proxmox does not crash, it does not close or restart.
Just randomly I find the Windows LTSC VM shut down.
The same VM configuration performed with Windows 10 PRO runs smoothly without anomalies or strange closures and I no longer know what to do
 
Are you sure your problem isn't coming from somewhere else?
1. hibernation is always deactivated by default in Windows and therefore your command does not change anything
2. what does your host configuration look like?
3. do you happen to have a high I/O delay or a backup running when Windows crashes?
4. do you see any messages in the Windows event log?
 
Are you sure your problem isn't coming from somewhere else?
1. hibernation is always deactivated by default in Windows and therefore your command does not change anything
2. what does your host configuration look like?
3. do you happen to have a high I/O delay or a backup running when Windows crashes?
4. do you see any messages in the Windows event log?
hello and thank you too for the reply.
I've done several tests and I just don't understand what the problem could be.
Out of desperation as I wrote in the first post, I took an Intel NUC that I had disused and installed proxmox from scratch and only the WINDOWS 10 LTSC virtual machine. Nothing, the problem is the same as the other industrial PC that I use as a server at home.
The incredible thing that leaves me very perplexed is that when I installed a WINDOWS 10 PRO for testing on the same NUC with the same VM configuration as WINDOWS 10 LTSC, the problem does not arise, which is why I thought it was a PROXMOX bug.
Anyway, no strange I/O and no backup execution
No messages from the windows event LOG
My test host is an intel NUC i7-8665U with 20Gb of ram, memtest ran without any problems. No IOMMU enabled
I don't know what to do anymore and I don't understand why I have no problems with WINDOWS 10 PRO and WINDOWS 10 LTSC YES
 
hello and thank you too for the reply.
I've done several tests and I just don't understand what the problem could be.
Out of desperation as I wrote in the first post, I took an Intel NUC that I had disused and installed proxmox from scratch and only the WINDOWS 10 LTSC virtual machine. Nothing, the problem is the same as the other industrial PC that I use as a server at home.
The incredible thing that leaves me very perplexed is that when I installed a WINDOWS 10 PRO for testing on the same NUC with the same VM configuration as WINDOWS 10 LTSC, the problem does not arise, which is why I thought it was a PROXMOX bug.
Anyway, no strange I/O and no backup execution
No messages from the windows event LOG
My test host is an intel NUC i7-8665U with 20Gb of ram, memtest ran without any problems. No IOMMU enabled
I don't know what to do anymore and I don't understand why I have no problems with WINDOWS 10 PRO and WINDOWS 10 LTSC YES
There may be something different about the configuration.
Is the LTS version a Windows EVAL?
There are some known problems, but they have nothing to do with Proxmox.
 
There may be something different about the configuration.
Is the LTS version a Windows EVAL?
There are some known problems, but they have nothing to do with Proxmox.
something different in which configuration?
I downloaded the original WINDOWS 10 LTSC ISO from the Microsoft site:
The file is named 19044.1288.211006-0501.21h2_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_it-it.iso
I haven't inserted the license yet because I wanted to do all the tests first and make sure that everything worked and then make a backup and not waste the license.
But even in windows 10 PRO which runs without problems it is not active and runs without a license
 
Hi,
With the Windows Eval versions it is normal that if the Windows is older than 180 days, the Windows regularly restarts or shuts down.
I therefore never use the EVAL images if I want to test for longer ;)
 
hmmmmmmmmm...
older than 180 days even if newly installed and regularly updated via windows update?
My Windows LTSC under proxmox always crashes within an hour and this time is never regular on both PCs.
Where do I find the non-EVAL LTSC image?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!