Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005).

Article
2016-01-21

Question

_{Thursday, January 21, 2016 7:01 AM | 1 vote}

I have enabled nested virtualization by running the script.

Invoke-WebRequest https://raw.githubusercontent.com/Microsoft/Virtualization-Documentation/master/hyperv-tools/Nested/Enable-NestedVm.ps1 -OutFile ~/Enable-NestedVm.ps1
~/Enable-NestedVm.ps1 -VmName <VmName>

After then my vm is failed to start with following error.

An error occurred while attempting to start the selected virtual machine(s).

'vm2016'failed to start.

'vm2016' could not initialize.

Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005).

All replies (17)

_{Friday, January 22, 2016 7:02 AM ✅Answered}

Hi,

Turn Off your VM and run this to disable Nesting.

Set-VMProcessor -VMName "WinVM1" -ExposeVirtualizationExtensions $false

Then check if you can start it.

Have you gone through the issues and troubleshooting steps mentioned here.

Nested Virtualization:

https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/nesting

What is your OS, build 'winver'.

(Get-WmiObject win32_operatingsystem).version

This should not be $null or blank. If blank then the script is not going to set things correctly.

(Get-VMProcessor -VM $vm).ExposeVirtualizationExtensions

Regards,

Satyajit

Please“Vote As Helpful” if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

_{Thursday, January 21, 2016 10:16 AM}

Hi Pratik,

Open the VM Settings from Hyper-V manager. -> Hard Drive settings.

Please check if you have the VHDx setup correctly. The path might be invalid or the VHDx might be missing from the path.

Regards,

Satyajit

Please“Vote As Helpful” if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

_{Thursday, January 21, 2016 10:42 AM}

Hi Satyajit,

The Hard Drive path is valid and present. Here is the error message while starting the VM.

PS C:\Users\Administrator> Start-VM vm2016
Start-VM : 'vm2016' failed to start.
'vm2016' could not initialize.
Failed to create partition: The hypervisor could not perform the operation because an invali
(0xC0350005).
'vm2016' failed to start. (Virtual machine ID 70635278-4F5E-473B-A255-74B571CB3C0D)
'vm2016' could not initialize. (Virtual machine ID 70635278-4F5E-473B-A255-74B571CB3C0D)
Failed to create partition: The hypervisor could not perform the operation because an invali
(0xC0350005).
At line:1 char:1

Start-VM vm2016

+ CategoryInfo : NotSpecified: (:) [Start-VM], VirtualizationException
+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVM

Regards,

Pratik

_{Thursday, January 21, 2016 11:05 AM}

Hi Pratik,

This error is related to Your script... You need to re-validate the script if this is correct and having all parameters correct.

Some helpful ref links:

https://www.veeam.com/blog/nesting-hyper-v-with-vmware-workstation-8-and-esxi-5.html

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/error-0x8004240f-failed-to-create-a-new-partition/03270f3f-116e-4d1d-8f27-17ff1108460d?auth=1

Thanks,

Mayank Dhama

_{Thursday, January 21, 2016 1:14 PM}

Do you happen to have processor compatibility enabled on the VM? That is not supported in setting up nested virtualization.

. : | : . : | : . tim

_{Friday, January 22, 2016 2:25 AM}

Hi Pratik,

Which OS is running on your hyper-v host? Both hypervisors need to be the latest versions of Hyper-V. Other hypervisors will not work.

Have you disabled dynamic memory?

And you need at least 4GB memory.

Best Regards,

Leo

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Sunday, January 24, 2016 6:04 AM}

I too have been having this exact problem enabling nested virtualization on VMs my Windows 10 Enterprise build 10586 machine:

I have run the Enable-NestedVM.ps1 script on the VM and can confirm that:

Dynamic Memory is off on the VM.
4 GB RAM has been assigned to the VM.
The network adapter has spoofing enabled on the VM.

I've tried with VM's with and without an OS installed.

An event with ID 15130 also appears in the Microsoft\Windows\Hyper-V-VMMS\Admin event log:

I'd love a solution to this problem too, but I suspect as this feature is in early preview (even on Windows 10) that it is broken on some installations.

Daniel Scott-Raynsford, MCP. https://dscottraynsford.wordpress.com/

_{Monday, January 25, 2016 5:51 AM}

Hi Tim,

I am using the Inter Xeon E5520 CPU, which supports Virtualization Technology and Extended Page Table. I have also cross checked all the requirements for nested VM.

Regards,

Pratik

_{Monday, January 25, 2016 5:58 AM}

Hi Satyajit,

I have checked the OS version and VirtualizationExtension parameter as follow.

PS C:\Users\Administrator> (Get-WmiObject win32_operatingsystem).version
10.0.10586
PS C:\Users\Administrator> (Get-VMProcessor -VMName vm2016).ExposeVirtualizationExtensions
True

Thanks & regards,

Pratik

_{Monday, January 25, 2016 7:21 AM}

Hi Pratik,

In that case could be some issue with the Windows 10 build. Have you tried in on WinServer2016 Preview.

Regards,

Satyajit

Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

_{Monday, January 25, 2016 8:22 AM}

Hi Satyajit,

I have gone through the Document once again. I have missed the very important part that says VBS and Device Guard Enabled cannot expose virtualization extensions to guests.

I have disabled that and also uninstalled the User Isolated mode Role. Everything is running fine now.

Thank you very much for the help.

Regards,

Pratik

_{Monday, January 25, 2016 9:30 AM}

Unfortunately this didn't work for me. :(

I can confirm Device Guard and VBS are disabled and have removed the Isolated USer mode role as well:

Any further suggestions on this are most welcome :)

Daniel Scott-Raynsford, MCP. https://dscottraynsford.wordpress.com/

_{Monday, January 25, 2016 10:33 AM}

Hi Daniel,

Disable the nested virtualization and check whether the VM is starting.

Set-VMProcessor -VMName $vmName -ExposeVirtualizationExtensions $false

regards,

Pratik

_{Monday, January 25, 2016 7:38 PM}

Hi Pratik,

Thanks for your reply. I ran the cmdlet and disabled the ExposeVirtualizationExtensions on my VM and can confirm that it starts up fine without them:

Note: I don't have a guest OS installed on this VM yet.

Thanks

Dan

Daniel Scott-Raynsford, MCP. https://dscottraynsford.wordpress.com/

_{Wednesday, January 27, 2016 6:28 AM | 1 vote}

Hi Daniel,

I have recreated the VM and tested again, its working for me. Verify the following checks in your case.

1. In the Group Policy Editor, go to Computer Configuration, Administrative Templates, System, Device Guard. Double-click Turn On Virtualization Based Security. Make sure that Policy is disabled.

2. Uninstalled the User Isolated Mode role if installed.

3. Both Hypervisors (Host and Guest VM) need to be the latest Windows Insider build 10565 or greater.

4. Turn off the Gen-2 VM. In VM settings, Uncheck the Enable Dynamic Memory and memory size must be minimum 4096.

5. Go to Checkpoints and uncheck the Enable Checkpoints.

6. Go to Automatic Stop Action and select the Shut down the guest operating system option.

7. Run the cmdlet.

Set-VMProcessor -VMName $vmName -ExposeVirtualizationExtensions $true

I hope this solves the problem.

Thanks & Regards,

Pratik

_{Wednesday, January 27, 2016 8:06 AM}

Thank you Pratik! Appreciate the help.

I double checked all the items you listed (including disabling checkpoints and even trying a Gen1 VM), but still no luck :(

However, I do have a Windows 10 build 11102 machine here which I have managed to get nested VMs working. It is a Windows 10 Pro edition, unlike the machine I can't get working. Pro edition doesn't support Isolated User mode and VBA, so perhaps that is something to do with it.

I think I may just have to wait for a newer Windows 10 Enterprise build.

But again, thanks for your help!

Daniel Scott-Raynsford, MCP. https://dscottraynsford.wordpress.com/

_{Wednesday, January 27, 2016 8:45 AM}

Good find Pratik, thanks for updating us.

Regards,

Satyajit

Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Share via

Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005).

Question

All replies (17)

Additional resources