failed to initialize whpx: No space left on device falling back to tcg

[Tasty_Tech]

Hello,

I have been facing the issue when booting the virtual core. Please find the screenshot below. I have a lot of available space on my disk and I am using only 40% of the RAM which is 32GB. Could someone please help me with this?

Thank you in advance

[nickH]

Hi @Tasty_Tech 

Like mentioned in the message you can check in the device settings at "hardware acceleration" for the root cause. 

If you click on the i-icon you will get more information on the state of the hardware acceleration on your PC. 

Best regards, 

Nick

[Tasty_Tech]

Hello Nick,

Thank you for your reply. Please find the screenshot attached,

Do you know how it works with Bosch laptop?

Could you please help me as I have a workshop?

Thank you

[CodeShepherd]

Did you like suggested turn on the windows feature Windows Hypervisor Platform? And beware to have Hyper-V switched off.

Yes it is working on Bosch laptops as we are also using it.

[Tasty_Tech]

Hello @CodeShepherd and @nickH 

Could you please help, I cannot change anything in the BIOS as its Bosch laptop. How do i do it in another way? as it says below

Thank you

[nickH]

You don't need to do changes to the BIOS. As it says in your screenshot CPU "Hardware Virtualization in Firmware" is enabled in BIOS. What you need to do is turn on the Windows Feature "Windows Hypervisor Platform". Therefore you need Admin Rights on your PC. 

Open the Windows Dialog "Turn Windows features on or off" and select "Windows Hypervisor Platform". Please also unselect "Hyper V" in case it is active, as these two do not work together. After that a restart of your PC is required. 

Screenshot of the Windows Dialog "Turn Windows Features on or off": 

[Tasty_Tech]

Hello @nickH ,

Thank you very much for quick reply. I have did what you suggested, hardware accelerator settings of the virtual core looks good now, thank you.

I still have the same issue, I am using 2.6.4 ctrlx Works,

But the good thing is the core boots after approximately 5-10min. is this normal?

Thank you in advance

[Sgilk]

@Tasty_Tech ,

No. This is a very long time to boot the virtual CORE.

The image above still indicates a problem with your hardware acceleration, but also with memory. Can you check your RAM usage when booting the CORE? Also, make sure you have Windows Hypervisor Platform selected for the hardware acceleration of this virtual CORE.

[Tasty_Tech]

Hello @Sgilk ,

I have the windows Hypervisor platform configured.

What i observed when i am booting the virtual core the CPU usage is at 100% and RAM is just at 56% to 60% so I still have 22GB space left in RAM. Is it because of CPU maxing or what else it can be?

I still have the same error as above.

Thank you

[Sgilk]

@Tasty_Tech , 

You can try reducing the CPU cores configuration option. Is there sufficient standard memory available at the configured storage location? The virtual COREs require 5+ GB.

If you enable the emulation process window, is there any additional information provided in the terminal window?

[FooFighter]

Hello Tasty_Tech,

is your current windows version up to date. This error might be fixed in a Windows Update. Are you using Windows 10?

Regards, Oliver

[Tasty_Tech]

Hello,

Thank you for your reply. As ours is Bosch laptop, I dont see any upcoming update, lookings like for now its up to date.

Could you please guide us as many ofthe engineers here has the same problem?

Thank you

[Pinball_NL]

Like me. Since I have updated to 2.6 I cannot use the virtual core anymore. I updated, but I do not know if the compagny I work for managed something at our notebooks. But I have the message " No Hardware Acceleration was found ". But with this info it is solved.

Take care that you take the correct checkbox. The other one doesn't work for this problem .... 😉

[FooFighter]

Hello Pinball_NL,

Since 2.4 we do not support IntelHaxm acceleration because this in no longer maintained by Intel.

You need to click on 'Details' in the Devices Settings Page, then you can click on the link 'Turn Windows Features on or off'. In the dialog you have to check 'Windows Hypervisor Platform' and restart your computer.

After a restart your controls with acceleration set to WHPX should start in about 40 to 80 seconds depending on your graphics card (GPU).

Regards, Oliver

[ChristianZ · Accepted solution]

I had configured a virtual ctrlX CORE some time ago and it was starting fine, but just the other day I did notice that I have the same message mentioned in the headline of this post. The control takes very long time to start or it didn't start at all. I did not change anything on the settings in between. It could be, that some Windows or BIOS updates have been installed on my computer.

In the end I could fix the problem by

• deactivating the Hypervisor Plattform, boot my Laptop,
• activate it again and boot the laptop one more time. 

[CodeShepherd]

@ChristianZ As an additional hint, this problem was coming up at several persons with an update of the Oracle VM VirtualBox Manaager.