When I enable nested virtualization the VM will not boot with a fresh install. I can not use docker because it says that virtualization is disabled. I use docker within the windows guest os so I can make sure our configurations work cross platform. I can now not debug configurations that have issues in windows. Is this a recognized issue? Since I work on critical infrastructure I will be looking to another solution if I this is not addressed promptly.
I've spent all morning trying to boot my vm. Thanks to this post as soon as I disabled nested virtualization it booted up fine. This is unacceptable. I do docker development on my windows vm and without hyper-v I can't run docker for windows!
It works in VMWare Fusion. I may have to switch to it if I can't continue my current work. Every hour I can't work costs me. Are we at least going to get a time line or some one to tells us they are working on it? What do I have to do to get this working? Anyone else that is having issues please post here. Maybe someone will respond.
Please, make report about problem and send it to Parallels. Go to Menu->Help->Send Technical Data If it possible, also write here number of report.
I already reverted to 13.0. I didn't have time to wait for you to even ask for this because I have work to do. I have also started a pilot of VMWare fusion because this should have been handled much faster. I will await a fix but I don't have time to stop work so I had to find other solutions.
Has this been fixed? Any estimated time? Do you even acknowledge there is a problem with nested virtualization and hyper-v support?
Are you still there or was this just a bot I don't understand how it would not be addressed with a hotfix. I guess most people must not use hyper-v or can live without it. This should be fixed asap. It seems like they are ignoring a broken core feature. What gives? Any staff out there care to shed some more light on the issue? Reading other messages posted here it seems only basic support replies to these so we get the typical "Did you restart your computer?" or check out this old outdate fix link type of support.
Well, the "hotfix" is to rollback to a Parallels version in which "nested virtualization" once worked. In my case that is Parallels 13.0 until Parallels 13.2 or higher comes out.
That's pretty ridiculous, I've patiently waited for acknowledgement or a fix, looking at going back to Fusion now due to bad support.
Hi @jschrade, we released a new update Parallels Desktop 13 for Mac Update 1 Hotfix 1 (13.1.1-43120) and this update addresses this issue. To check for updates, click on the Parallels Desktop menu on Mac menu bar and select Check for Updates: http://kb.parallels.com/124262
Hi @MichaelD21, we released a new update Parallels Desktop 13 for Mac Update 1 Hotfix 1 (13.1.1-43120) and this update addresses this issue. To check for updates, click on the Parallels Desktop menu on Mac menu bar and select Check for Updates: http://kb.parallels.com/124262
New patch works for me. Boots fine again with nested virtualization on, hyper-v working, docker for windows working.
Glad to know that you were able to sort out the issue. Please get back to us for any further queries. Thanks!
Glad to know that you were able to sort out the issue. Please get back to us for any further queries. Thanks!
