1) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43280)
Posted 26 Aug 2020 by Jewfro
Post:
Just wanted to update this because the issue has been resolved. I don't know what exactly fixed it, but after some unrelated fiddling with a lot of settings to get a FreeBSD VM working on Virtualbox, BOINC started working again. I believe it may have had something to do with enabling and disabling WSL and Hyper-V through the command line (not just the windows features menu as I tried before). For anyone who has a similar issue and finds this, I have WSL and Hyper-V disabled, and Virtual Machine Platform and Windows Hypervisor Platform enabled in Windows Features. I unregistered all WSL distributions from the command prompt, and disabled Hyper-V through the command prompt with "bcdedit /set hypervisorlaunchtype off". Hopefully this can help someone else.
2) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43171)
Posted 3 Aug 2020 by Jewfro
Post:
After changing to a Windows 10 pro installation the issue persists. Looks like the issue is unrelated to the license.
3) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43144)
Posted 30 Jul 2020 by Jewfro
Post:
Unfortunately the new entry seems to have the same issue after following the steps outlined and even after enabling IOMMU.
4) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43143)
Posted 30 Jul 2020 by Jewfro
Post:
Thank you for the insight. I will follow those steps.
5) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43124)
Posted 29 Jul 2020 by Jewfro
Post:
That is a good point. I was running an Intel CPU and motherboard before, but I must not have properly reattached the machine under a different id. I cannot seem to attach with a different id, and I can't delete the existing id. Is there something I'm missing?
6) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43119)
Posted 28 Jul 2020 by Jewfro
Post:
The license is from a previous employer, but the machine is my personal machine. Thank you for reminding me to change that, but it did not seem to affect anything. Task manager says virtualization is enabled, and I am able to create virtual machines myself as I was able to before. I have not tried any other projects, but when I noticed this issue I tried cosmology to check if it occurred there too. I will look for a third vm based project to check.
7) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43106)
Posted 26 Jul 2020 by Jewfro
Post:
The motherboard works fine. As I said virtualization is working in other applications. I am on the most recent revision BIOS.
8) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43103)
Posted 24 Jul 2020 by Jewfro
Post:
Yes. I should clarify that when I said I turned on or off "virtualization", SVM was the BIOS option I changed. There is nothing further in the BIOS that I could find relating to virtualization.
9) Questions and Answers : Windows : Virtualization capability read incorrectly (Message 43095)
Posted 23 Jul 2020 by Jewfro
Post:
Hello, I have a strange virtualization issue running lhc@home (also affects other projects like cosmology@home). I've tried looking through other forum posts and troubleshooting on my own, but I just can't figure this out. BOINC seems to read virtualization as the inverse of it's actual setting. When I enable virtualization in BIOS (tested to work with virtualbox VMs, leomoon cpu-v, task manager, and android VMs) my machine has "Virtualbox (6.1.12) installed, CPU does not have hardware virtualization support" listed under vitrualization in computer information in my profile. When I turn off virtualization (all tests mentioned before confirm virtualization is disabled) the same line in my profile is listed as "CPU supports virtualization and it is enabled". Only when virtualization is off am I sent virtual machine tasks, all of which fail because virtualization is off. I have gone through Yeti's checklist multiple times, disabled hyper-v, checked client_state.xml for "<p_vm_extensions_disabled>" (which stays at 0 even when virtualization is turned off in BIOS), and reinstalling virtualbox and BOINC. If I've missed anything please let me know, thanks.



©2024 CERN