*Update*
I found out, that changing CPU from host to any other CPU type allows the vm to install docker and hyper V. Why is this the case? I need the vm to use CPU host, but this no longer works
This is the output from the grep command
grep -R "" /sys/module/kvm_intel/parameters
/sys/module/kvm_intel/parameters/enlightened_vmcs:N
/sys/module/kvm_intel/parameters/eptad:Y
/sys/module/kvm_intel/parameters/flexpriority:Y
/sys/module/kvm_intel/parameters/vmentry_l1d_flush:cond...
I havnt followed the known issues, no. However the problem is not starting the VM, rather that enabling windows hyper V results in a crash. Does the cpu flag hv-evmcs need to be on for virtualization to work? Because then i cannot start the vm
- Yes i frequently update. I have the newest 6.2-4 installed
- Nothing else than docker which needs virtualization no. But just enabling windows' hyper V feature, breaks the VM.
- The pvereport -v is very long, the content is to long to be posted on here. Do you want a pastebin link?
Hello guys :),
At the moment i'm hosting a windows vm with TeamCity and docker running on it. It's for my school project, and i was disappointed to find out, that the vm kept crashing at launch.
- I tried restoring it from a backup, same problem.
- I tried creating a new vm, enable windows...
Hello Darin, the fix which worked for me, was going into the bios and changing a CPU option from IGD to PEG. I have an intel motherboard, but i would guess the same counts for a amd :)
FIXED!!! By some amazing help from jimnordb aka. SilentSpy, we were able to find out, that a bios option regarding CPU specifications needed to be changed from IGD to PEG. This enables my GPU to be used seperatly and worked like a charm.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.