SOLVED

Running in Virtual Box on WVD is slow?

%3CLINGO-SUB%20id%3D%22lingo-sub-1904513%22%20slang%3D%22ja-JP%22%3ERunning%20in%20Virtual%20Box%20on%20WVD%20Is%20Slow%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1904513%22%20slang%3D%22ja-JP%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20the%20Recent%20Popularity%20of%20the%20Cloud%2C%20We%20Are%20Planning%20to%20Migrate%20Your%20Internal%20Developer%20PCs%20to%20Windows%20Virtual%20Desktop.%3C%2FP%3E%3CP%3EWhen%20I%20Tested%20the%20Migration%2C%20I%20Found%20That%20VirtualBox%20%2B%20Vagrant%20Is%20Quit%20Slow%20and%20It%20Takes%202-3%20Hours%20to%20Get%20the%20Guest%20OS%20Up%20and%20Running%2C%20Is%20This%20Something%20That%20Thing%20From%20Windows%20Virtual%20Desktop%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20we%20only%20have%20one%20user%20per%20machine%20and%20we%20use%20the%20standard%20ssd%20plan%2C%20it's%20unlikly%20that%20it%20will%20be%20that%20slow.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1904513%22%20slang%3D%22ja-JP%22%3E%3CLINGO-LABEL%3EVagrant%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVirtual%20Box%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Virtual%20Desktop%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1914725%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20in%20Virtual%20Box%20on%20WVD%20is%20slow%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1914725%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F874111%22%20target%3D%22_blank%22%3E%40ksesoko%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20very%20slow.%20It%20is%20not%20related%20to%20WVD%20but%20Hyper-V%20nested%20virtualization%20capabilities.%3C%2FP%3E%3CP%3EWith%20E%20v3%2B%20and%20D%20v3%2B%20vms%20you%20can%20do%20nesting%20but%20you%20will%20only%20get%20the%20virtualization%20performance%20benifts%20with%20Hyper-V.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20that%20VMware%20have%20more%20nesting%20capabilites%20but%20I%20don't%20know%20if%20VMware%20hosts%20on%20azure%20have%20nesting%20enabled.%20Note%20that%20VMware%20on%20Azure%20is%20not%20cheap%20and%20I%20don't%20know%20if%20you%20can%20(legally)%20run%20WVD%20on%20Azure%20VMware%20hosts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1914928%22%20slang%3D%22ja-JP%22%3ERe%3A%20Running%20in%20Virtual%20Box%20on%20WVD%20is%20slow%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1914928%22%20slang%3D%22ja-JP%22%3EThanks%20for%20the%20reply.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20I%20was%20running%20VirtualBox%20on%20WVD%2C%20but%20I%20will%20try%20to%20verify%20if%20it%20can%20work%20property%20with%20WVD%20%2B%20Azure%20VM.%20%3CBR%20%2F%3E%20Since%20there%20is%20a%20confluence%20with%20cost%2C%20I%20will%20try%20to%20start%20the%20verifcation%20from%20the%20minimum%20configuration.%3C%2FLINGO-BODY%3E
New Contributor

 

With the recent popularity of the cloud, we are planning to migrate our internal developer PCs to Windows Virtual Desktop.

When I tested the migration, I found that VirtualBox + Vagrant is quite slow and it takes 2-3 hours to get the guest OS up and running, is this something that comes from Windows Virtual Desktop?

 

Since we only have one user per machine and we use the Standard ssd plan, it's unlikely that it will be that slow.

3 Replies
best response confirmed by ksesoko (New Contributor)
Solution

@ksesoko 

It is very slow. It is not related to WVD but Hyper-V nested virtualization capabilities.

With E v3+ and D v3+ vms you can do nesting but you will only get the virtualization performance benifts with Hyper-V.

 

I know that VMware have more nesting capabilites but I don't know if VMware hosts on azure have nesting enabled. Note that VMware on Azure is not cheap and I don't know if you can (legally) run WVD on Azure VMware hosts.

Thanks for the reply.

I was running VirtualBox on WVD, but I will try to verify if it can work properly with WVD + Azure VM.
Since there is a conflict with cost, I will try to start the verification from the minimum configuration.

It was necessary to convert the box files to vdi, but
The combination of Azure VM + WVD worked fine.

 

thank you