From within Hyper-V, select Virtual Network Settings. The first thing you need to do is create a new virtual network. Overviewīasically what you’re going to do is create a new virtual network on your Hyper-V machine, add a new NIC to your VMs and then put them on the same network. Use whatever method works for you… for me, this method works great and it’s what I use. I’m sure there will be plenty of comments from people who have their own method… that’s just fine. Hopefully this helps you.ĭisclaimer – I fully recognize there are other ways to achieve this. Now, I’m a bit of a networking-idiot and had to get Todd Baginski and Maurice Prather to help me with this (so big shout out to them), but it’s actually quite simple and I after explaining it to to quite a few people, I’m documenting it so I have a URL to point to where others can do it on their own. There is a way around this though… it’s a simple networking trick. It’s frustrating because it was so easy to do in VirtualPC or VMWare Workstation as we had the easy copy files to and from the desktop just like we can do with Remote Desktop. Those of us who use Hyper-V for development know of the challenge we face when we try to copy files or talk to the guest virtual machine or have the guest VM access the host machine. Disclaimer – I fully recognize there are other ways to achieve this.
Allowing a host machine to talk to guest VM’s in Hyper-V (and vice versa)
0 kommentar(er)
