Windows 10 / Server 2016 Hyper-V Issues

F

funtimes

New Member
Oct 18, 2016
3
0
1
55
Hello all,

I'm a new user here to proxmox, which by the way is awesome! I've been attempting to install Windows 10 and Server 2016 with the Hyper-V option enabled, but I have had no success :(. The reasoning behind my wanting to install Hyper-V is for the ability to use/test docker on windows. As I want to be able to spin up docker (linux/windows)containers on the windows host(VM) inside of a private container to container only network.

We typically host an ubuntu VM with docker installed and have two ubuntu docker containers. One of the containers stays up and running all the time with some network services listening, and the other docker container only spins up briefly to test/verify some programs/code against the container only network(IE they only have loopback addresses). This has been working flawlessly on proxmox with no issues.

I was hoping to the do same thing on Windows 10 or Server 2016. I've tried the nested virtual options from the wiki as well as some other things. Was just curious if anybody else has had success running a Windows 10 or Server 2016 VM on proxmox with hyper-v enable and actually able to run the VM's under hyper-v?

Appreciate any and all help/support that anybody has to offer.
Server2016-Hyper.png

Win10-Hyper.png
 
What physical processor/motherboard are you using?
try to change the processor from within the proxmox, as shown below...
processor.png
 
hyper-v inside qemu (nesting) is not known to work.
 
Hi Tom,

Do you know if there are any plans/possibilities of this working in the future? I apologize for my lack of understanding but is this a proxmox limitation or a hyper-v/qemu limitation?
 
qemu with hyper-v.

but beside this limitation: if you want to run docker, why do you install windows?
 
Thanks for the quick reply. I posted a little bit about our build out above.

In a nutshell we present people different programming challenges, and we blindly run their code inside of a docker container, and compare the output of the results to a known good result. We are looking to branch from currently only linux supported languages to some windows support languages. We would require the docker on windows to be able to launch container only networking between the windows containers, as we wouldn't want either of the containers having network/internet access to the rest of the world.

I'm sure you can think of all the bad things you can do with blindly running users uploaded code with a connection out the world :) Hence the requirement for docker container only networking.
 
You must log in or register to reply here.
Top Bottom