New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
correct
done
I can just best guess it has something to do with storage, and not CPU.
Can you benchmark the LVM in that proxmox?
i think you are onto something
i have asked chatgpt to run a benchmark, i did it with the vm on and off, i hope it's correct
is lvm overhead this bad? chatgpt said it could be because my container is nearly full as well
READ: bw=48.9MiB/s (51.3MB/s), 12.2MiB/s-12.3MiB/s (12.8MB/s-12.9MB/s), io=2935MiB (3078MB), run=60001-60001msec
WRITE: bw=21.0MiB/s (22.1MB/s), 5362KiB/s-5419KiB/s (5491kB/s-5549kB/s), io=1263MiB (1324MB), run=60001-60001msec
basically below a IDE drive, i think windows boot will finish in ~1 hour, if you let it boot, it will, I bet 100%
PS; a disk yabs will be better, as if at 4K random RW you have below 15 MB/sec, it is a no-go for windows.
honestly im not sure how to do that...
i wonder what's causing this...
will try to yabs the drive without windows
for now i'll migrate my windows VM to other (slower) server but should be better speed because i dont understand what's happending to my server at hostbrr
im overwhelmed
so something is causing terrible terrible SSD, well IDE speeds
which probably causes it problem with not booting using "host" preset
vm in vm ...... nothing can help
95% efficiency plus 95% efficiency shouldn't be 15MB/s
That doesn't make sense. You're NOT on a dedicated server, you're sharing the server with possibly hundreds of others.
how doesnt that make sense?
i had 0 problems with windows 2022, great speed
all i did, is put proxmox infront of it with 1 virtual machine, exactly the same windows server 2022
same server
same specs
before:
unknown hypervisor -> windows 2022
after:
unknown hypervisor -> proxmox -> windows 2022
a extra hypervisor add much more overhead on VMM vmenter/vmexit and spinlocks, expecially there are two scheduler which result in much more bad decision, etc. The performance degrade is exponential not linear.
If you don't believe and also won't study more depth on VMM and system sheduler then there are not much to talk...
I have never tried this before, but I would guess that it has to do with the CPU flags. Since CPU type ‘host’ does not work, I would suggest specifying all available CPU flags for your windows vm.
well i created a new VM, pretty much same settings HOST type
and win server 2022 works.... just bloody works
yeah, i assume some stuff i have installed in preventing boot, no fucking clue
will debug
hbrr? in connection with windows server...?!
https://lowendtalk.com/discussion/comment/4394595/#Comment_4394595
im unsure what this supposed to mean
well, as described earlier, i had 0 problems, problems started since i used proxmox on top
for now continuing to pay bills hoping to find solution sooner than later
more debugging
booting in safe mode (host preset) works fine!
it has to be software, driver or similar...
Have you installed the latest VirtIO Drivers on the window vm? I have been running server 2022 for years with no issue.
yupp, might honestly remove them all and reinstall them, im unsure
pain because the VM has no internet (intended)
I have always under the impression that Windows does not like user replacing components. Is there a reason not to start from cratch?
I always keep a "live" Windows template (not converted to proper template) to have it updated and ready to replace any intances that have issues.
Licenses, other users, activating all that shit
Pain in the ass, days of calling MS support and probably 50-100€ for licenses on top
update:
i have deinstalled buuuunch of things and tried a buuuunch of thngs
it works! now idk why it works
will try uninstalling drivers
and then booting up again
so backup, remove all drivers (virtio, parsec, etc) then see if it boots...
pain in the ass, but im very close
i have solved it ! i think
just remove wsl2 and hyperv stuff and it boots fine, i need to do more teste but yeah, that works fine
dism.exe /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
dism.exe /online /disable-feature /featurename:VirtualMachinePlatform /norestart
dism.exe /online /disable-feature /featurename:Microsoft-Hyper-V-All /norestart
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -NoRestart
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-PowerShell -NoRestart
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Management-Clients -NoRestart
the commands are from AI, use your own sense to remove wsl2 and hyperv
thanks to everyone trying to help!
yeah it boots fine, instantly and disk speed is also fine, fuck knows what happened