I'm running Server 2008 64bit with Hyper-V. I've created a virtual machine with Vista 64bit and installed it. I can't get the Vista virtual machine to see the network adapter.
I've set-up an external network on the Virtual Network Manager (Hyper-V) and associated that with the virtual machine (Vista). I've also tried using a Legacy Network Adapter but that didn't work either although that time the Vista machine saw the network card but couldn't connect through it.
This is (obviously) the first time I've tried to set-up a virtual machine.
Any ideas?
EDIT: I notice that this question has been voted down a couple of times. I know that it's not a programming question but I'm a developer setting up a virtual machine to test my C#/ASP.NET code on and thought that other developers may hit this problem as well when they're doing this...
I don't know Hyper-V, but I know in VMWare you can create a network connection in Bridged mode (meaning the VM will get it's own IP address via DHCP if that's enabled) or host-only mode (meaning the VM can only communicate with the host). When Vista could see the card, could it communicate with the host machine (which would indicate a host-only connection was specified)? What kind of IP address did it have (I would guess Hyper-V has a built-in DHCP server like VMWare does?) -- that might give additional clues.
Sorry I don't know Hyper-V better...
Make sure you have the Hyper-V Tools installed on the Guest VM. You shouldn't need the legacy adapter.
You also may want to make sure you have all of the latest updates which may have addressed your issue. Particularly, KB950050
http://support.microsoft.com/kb/950050
It turns out that Vista x64 running as a VM through Hyper-V doesn't support the virtual network connection/card and that you have to set it up as a legacy network card. When I eventually got the config settings correct for the legacy network and disable the virtual network it connected.
Thanks for the help guys - much appreciated!
Related
I have some trouble with my windows server 2019 running Hyper-V, for the background my windows server run on an ESXI infra.
It is impossible for me to get any internet access nor domain access on my Hyper-V virtual machine, this is how my host configuration look like
Host network
For me all look good, but when I turn on my virtual machine this is what I get
VMs network
VMs ping
I can see the machine getting a IP from my DHCP server, but it is impossible for me to ping any of the gateway, DNS.
My DHCP
This is how my virtual switch look like
vSwitch Hyper-V
And if needed my Ipconfig of my Windows server Hyper-V host
Hyper-V host network
I think that i have now tried everything I could, I don't see why my machine can get a DHCP IP, but can't communicate with any of my server.
I already have a topic posted on SpiceWorks (https://community.spiceworks.com/topic/2326264-hyper-v-wont-provide-internet-access-on-my-virtual-machine?page=1#entry-9231547), the last answer suggested that the problem came from my vSwitch on Hyper-V, but even after recreating a new one I can't get anything.
If you have any idea that can help me to achieve my configuration even the slightest one I'll gladly take it.
First thing I would like to ask, you are doing a Double Nested Virtualization, meaning: [ESXi] is the BareMetal Hypervisor, then inside of this Host you have at least 2 VMs, one name "SRVPARDC001" & the Hyper-V VM named "TESTHYPERV" , and inside this last one you have another VM called "VDI-Master" , if this is correct, you are asking:
*Why is VDI-Master, not getting internet, when SRVPARDC001 has leased an IP address ( 192.168.1.118) ?
My question is, why does the ipconfig output for VDI-Master show IP 192.168.1.121 , which per your DHCP, should be leased to the Desktop
Would it be possible to use a different subnet for the Virtual Switch inside the Hyper-V , to eliminate routing/dhcp issues?
My impression is that there is an issue on how the virtual switch is configured on the TESTHYPERV vm, since that virtual switch should be allowing the traffic upstream to the ESXi host and then out via your gateway/router/firewall device.
After rebooting is it possible to open a Hyper-V virtual machine without going through the Manager? It seems like it is already running in the background or maybe it is just in its last state.
If the OS in the Hyper-V virtual allows for remoting and also it is on the same network as the attempt to open a remote desktop to that virtual.
Note that the default network adapter for a virtual will provide a different IP address than what the local network provides to the server. You will most likely want to create a network adapter (in Hyper-V) which shares the network card to the virtual and the virtual will get its IP address from the local network.
If you can ping it, then it can be remoted to..but other things within the virtual has to allow for remoting.
Upon reading the OPs comments, it is clear that the need is to launch the virtual outside of Hyper-V. Hyper-V uses VMConnect.exe to achieve that...and that is available.
One can do that in an elevated Powershell shell such as:
vmconnect {Local/remote computer name} {Virtual Name}
such as
vmconnect Hyperion W10-Zephyr
where Hyperion is the local computer name and W10-Zephyr is the virtual's name.
See also Connecting to Hyper-V virtual machines with PowerShell
I have been trying to setup a Win7 VM on Hyper-v that connects to the internet through my Win 8 host machine.
I can't seem to figure out why the VM can't ever get passed limited connectivity. Any ideas?
NO sure why but all I had to do was Disable/enable the vEthernet adapter and everything worked great!
Check that you have a Virtual Switch with an "External Network" using the Virtual Switch Manager.
The other network types offer VM isolation. If your VM is on an "Private Network" it can only talk to other VMs on the server. The "Internal Network" allows VMs can talk to other VMs and to the host.
In contrast, an External Network allows the VM to contact machines on the network that the host is attached to.
I worked on this issue for a while myself after upgrading to Windows 8.1 and losing connectivity. Added and removed the adapter to no avail. The solution was to upgrade the VM's Integration Services.
I had the same issue because my DHCP settings on my guest VM was setup wrong.
So check the DHCP setting if they are on obtain automatically.
Control Panel\Network and Internet\Network Connections
Network adapter properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties ->
Obtain DNS server address automatically
I have had great success with Hyper-V and windows 8 and windows 10 virtuals using external switches with a Windows 8.1 host. Unfortunately I could not get the external switch to ever work on windows xp virtual running under Hyper-V. Instead, after reading a lot of sites/suggestions, I followed this guide to bridge an internal virtual switch (with Hyper-V legacy network adapter for XP) to the host wifi. I hope this saves someone else some time when working on an XP virtual.
Using Hyper-V with a Wireless Network Adapter
I am using Hyper-V for the first time (running Windows 8). When I create a new virtual network switch, external, it bridges the VMs network adapter with the WiFi - and that for some reason kills the WiFi's internet connection. Why, and what could I be doing wrong?
Thanks,
A.
If you have VirtualBoxinstalled, check if any of the Hyper-V virtual adapters/bridge connection has the VirtualBox Bridged Networking Driver ticked in the connection properties. If they do, simply untick this service where it is present and this should fix it up for you. No need to uninstall VirtualBox.
I had a static ip-address in my ethernet adapter.
Removed the static entry.
Made my external virtual switch.
Had the extra vEthernet adapter, made my static entries (ip-address, dns-server) in this adapter.
Everything is working fine now.
Chris
I had the same problem, it takes a couple of seconds to setup the connection again. Check this tutorial: https://superuser.com/questions/469806/windows-8-hyper-v-how-to-give-vm-internet-access
I just ran into the same problem, losing the internet connection when creating the virtual switch. Uninstalling VirtualBox which I had installed at the same time fixed the problem for me (just disabling the VBox adapters was not enough), so they seem to be unable to happily coexist.
I ran into the same problem recently when creating an external switch in Hyper-V. Long story short, every time an external switch was created, it would bring my ethernet connection down on my host laptop. I had wifi connection option also but disabled it to just strictly troubleshoot the ethernet network adapter.
I brought down the VM, once turned off, deleted the external network adapter from hyper V virtual switch manager. On the host machine, disabled and re-enabled the network adapter from within network connections (ethernet). Once connected, I brought the VM back online FIRST, then created the external switch second which connected with no issues. Verified I was able to access outside world aka internet on both host and VM.
Maybe you unchecked by accident the Allow management OS to share this network adapter setting that is enabled by default. Disabling this setting will leave your hypervisor OS without network connectivity.
I was able to fix such an issue by disabling Internet sharing on the wireless adapter, creating an Internal virtual switch in Hyper-V first, then disabling VMWare bridge on all involved interfaces, then I made a bridge in Network sharing center by selecting my internal switch and Wi-Fi adapter and after that I was able to select external network in Virtual switch manager in Hyper-V
I ran into the same problem too. I don't know for sure, but after trying all of the solutions above and any others I could find, I renamed my virtual switch to 'realtek' (the type of network card I have installed) instead of taking the default name that I think was 'new virtual switch'. Something else I did may have solved the problem (I modified everything I could find for two days), but I think renaming it is what finally gave me internet access to the vm.
I'm trying to do mobile application development (BlackBerry, Android) on a virtual machine. My idea is that no matter what desktop I'm on I can open a remote connection to the virtual machine and have my mobile development environment ready. The problem is that I would like to deploy code to the mobile device as if it were physically connected to the virtual machine. Ideally the devices will be plugged in to the client machine that is creating the remote connection.
I'm currently using VMWare workstation to manage my virtual machines, I've done a bit of research to see what the best solution for connecting my usb devices over the network is.
There are a multitude of pricey USB over network solutions that may or may not work for what I'm trying, but I would like to avoid those. I would be interested in a free open source solution where both the usb host and usb client are windows machines. This is close to what I am looking for http://usbip.sourceforge.net/, but you can't host a device from Windows.
It appears that I may be able to do this with a Hyper-V VM and RemoteFX through Microsoft RDC, but I would like this to work on my existing VMWare VM.
The quickest solution I've found is a network usb hub that would allow me to connect the devices over the network, but this would force me to be attached to the hub which is a problem if more people come on my project.
Ideally I'm looking for an existing software solution to my problem. Any suggestions?
Also can anyone confirm this would work in Hyper-V using RemoteFX?
I would consider porting your VM over to VirtualBox from Sun (now Oracle) they have remote USB support out-of-the-box, and are very stable.
I've ported machines the other way (for work) and it's not difficult.