I am trying to make some virtual Machines with Hyper-V,I Create and external virtual switch in Hyper-v and then link it to the physical host network card.
Then i type a name for this virtual switch and select the exact physical network card which currently connect your host to internet,and select thE external virtual switch as network adapter of the virtual machines.
But it doesn't work anyone can help me?
Brian Hoyt
Hello Community
On Windows Server 2012 R2 I installed Hyper-V.
After I created myserver.vhdx .
The problem is that when I try to install Windows Server 2012 R2
on myserver.vhdx I go to Hyper-V Manager, right click myserver.vhdx
and click connect.
Next I go to:
Hyper-V Manager
right click Virtual Machine Name
Connect
Note: A message appears stating:
"boot failure. reboot and select proper boot device
or insert boot media in selected boot device "
Next I click:
Action
Insert Integration Services Setup Disk
and it says success
Next I click the cdrom drive and see:
Windows Server 2012 R2
Install Now
Next I click
Install Now
the hourglass appears and shows
"Setup is copying temporary files"
The problem is the install won't go any further
it just hangs here.
In short how can I get the Windows Server 2012 R2
to get past that message and finish installing?
Shabeaut
Hi Everybody,
I am facing an unwanted issue with clustered Hyper-V and Failover Over Role with NetApp CIFS. Here it is :
I have two physical servers with Hyper-V enabled, both of them have a NetApp CIFS storage for Virtual Machines.
I have no issue everything is working fine : i can create, start, manage VMs on both nodes with Hyper-V Manager and i can manually move VMs between nodes.
When i add the Failover Role and i want to configure this role for HA Virtual Machine, it failed with the following messages :
The path where the virtual machine configuration is stored, '\\fsst00115\FSST00115_1', is not on storage managed by this failover cluster. Verify that the path is accessible from all nodes of the cluster that can own this virtual machine.
The path where the virtual machine checkpoints are stored, '\\fsst00115\FSST00115_1', is not on storage managed by this failover cluster. Verify that the path is accessible from all nodes of the cluster that can own this virtual machine.
The path where the virtual machine Smart Paging files are stored, '\\fsst00115\FSST00115_1', is not on storage that is managed by this failover cluster. Verify that the path is accessible from all nodes of the cluster that can own this virtual machine.
The path where the virtual machine hard disk is stored, '\\fsst00115\FSST00115_1\Virtual Hard Disks\test.vhdx', is not on storage managed by this failover cluster. Verify that the path is accessible from all nodes of the cluster that can own this virtual machine.
Of course the path is available and accessible from all nodes with Hyper-V Manager. i tried to give Full access to machine node and cluster node account on the share but no success.
I check again all parameters on my NetApp share for the vserver invole in the share :
https://www.netapp.com/us/media/tr-4172.pdf
https://kb.netapp.com/support/s/article/how-to-set-up-svm-cifs-for-hyper-v-over-smb?language=en_US
https://library.netapp.com/ecmdocs/ECMP1196891/html/GUID-BC313C3E-ADE2-48F6-8E88-2141BCBFD006.html
Does anyone can help about this issue that i try to resolve since hours with no sucess ? Thanks by advance for your help.
Regards
Brian Hoyt
Hello all,
I require some assistance from you guys as I am out of ideas.. I have a Hyper V Server running multiple Windows servers. randomly throughout the day I have some servers which are getting paused with the description of "Running out of space". I realised that there is a .avhd attached and I will have to reboot the server to merge the snapshot so that the server is back online. I do not have any snapshot settings attached to the servers and they range from 2008R2 to 2012R2. There is also Hyper-v replica between two physical servers.
Any experience on this as I am truly lost.
Tux
Hello,
Since about 4 months ago, we are having trouble when trying to connect a USB drive to our virtual machines.
We have 2 Dell PowerEdge R430 servers with Windows Server 2012 and Hyper-V installed, when I connect a USB Drive while the physical machine is running, I can't attach the USB drive to the virtual machines, for it to work I need to restart the physical machine with the USB drive already plugged in, after doing this I can connect the USB drive to the virtual machine again, but, if for some reason I unplug and plug it again, it shows me this error:
NOTE: I was going to insert an image here, but Technet wouldn't allow me, because it says my account is not verified, so I've uploaded it to: h t t p s : //s14.postimg.org/hwk41jykx/1471635468078_remmina_2016_12_2_19_27_55_491706.png
As you can see in the above screenshot, the disk is set Offline at Disk Management and I'm using Physical Disk Option at SCSI section in Hyper-V manager, this used to work before, but it started occuring this error at some point that I don't remember, maybe after any update, I can't say for sure.
This same error also occurs at the other server, which is equal to this one, but with different virtual machines.
I couldn't find any details on event viewer, so I can't figure out the reason for this error.
Please help, we use to change the backup media every week and it's obviously nonsense to reset the physical server once a week, every time we have to exchange the disk.
Let me know if you need any more details.
Sorry for the poor english.
Hugo Thebas
I am getting this error while creating the VM all of a sudden on my Windows 2012 R2 Hyper-v.
I could create a vhd seperately and also create a vm without vhd and point the vhd which provides temporary fix
Any Thoughts
Thanks
Jacob
Hello, I have a Hyper-V Core server running 2016 as a VM, and I can't access the Internet. I was running everything successfully last night, and wiped the server down to metal to make sure the instructions were correct, and it looks like I missed documenting one step. Nevertheless, it means it's not a hardware issue.
The problem is that when loading MS2016, I can not get an Internet connection.
On the host HV:
Select Network Adapter Index# (Blank=Cancel):
and ipconfig /all (with the extraneous junk cut out)
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
And in the Hyper-V Manager, the Virtual Switch is set to "External", and I am definitely using the right card (#58) to link to the switch. I have tried checking and unchecking all the boxes and rebooting all the hardware, both the VMs and the physical server. Here's the current configuration: http://imgur.com/I8ppTW7
And as I have read several guides suggesting that I cycle the option boxes, I want to make it clear that I have cycled all the option boxes.
I have turned the firewall on the Hyper-V server completely off for troubleshooting.
Since I'm posting this, it's not a problem with my router and I can see that there is no VM on the client list.
ipconfig from the VM is here. As you can see, it's still using the default address.
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
Neither a restart on the VM nor an ipconfig /renew seems to do anything except throw a "could not reach the DHCP server" error. (Similar error with different text to the Ubuntu Server when setting that up.)
What am I missing here? Last night nothing worked until I installed MS2012, and then mysteriously both 2016 and Ubuntu Server were 100% fine. That didn't fix anything this time.
Any help you can throw my way would be excellent.
Thanks!
Hello, I have a Hyper-V Core server running 2016 as a VM, and I can't access the Internet. I was running everything successfully last night, and wiped the server down to metal to make sure the instructions were correct, and it looks like I missed documenting one step. Nevertheless, it means it's not a hardware issue.
The problem is that when loading MS2016, I can not get an Internet connection. (The problem is also true with 2012 and Ubuntu 16.10, which leads me to believe this is in the way the virtual switch is configured.)
On the host HV:
Select Network Adapter Index# (Blank=Cancel):
and ipconfig /all (with the extraneous junk cut out)
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
And in the Hyper-V Manager, the Virtual Switch is set to "External", and I am definitely using the right card (#58) to link to the switch. I have tried checking and unchecking all the boxes and rebooting all the hardware, both the VMs and the physical server. Here's the current configuration: http://imgur.com/I8ppTW7
And as I have read several guides suggesting that I cycle the option boxes, I want to make it clear that I have cycled all the option boxes.
I have turned the firewall on the Hyper-V server completely off for troubleshooting.
Since I'm posting this, it's not a problem with my router and I can see that there is no VM on the client list.
ipconfig from the VM is here. As you can see, it's still using the default address.
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
Neither a restart on the VM nor an ipconfig /renew seems to do anything except throw a "could not reach the DHCP server" error. (Similar error with different text to the Ubuntu Server when setting that up.)
What am I missing here? Last night nothing worked until I installed MS2012, and then mysteriously both 2016 and Ubuntu Server were 100% fine. That didn't fix anything this time.
Any help you can throw my way would be excellent.
Thanks!
friends ... i would like to know couple of things
1. what is the best possible way to replicate production data to DR site ... we have production Vms and would like replicate these Vms to DR site ... i understand hyperV replicate gives Async backup ... do we have a Sync technology to do this ...
2. for HyperV replica can you guys please guide me what are the things we need to take care of .. Dr site is at a WAN location with bandwidth of around 20Mb between two sites but data is around 8 Tb ... i am sure this is a problem as transferring this will take ages.. can you advise the best way to do this ...
3. can i use same DR server to have replicas from two different domain .. as at source i have two domains running few Vms each .. i want to replicate both to Dr site to the same hardware ... possible ..??
Thanks, Happiness Always
Jatin
I have installed a new Windows Server 2016 Hyper-V environment.
Intel i7-6800K, 64GB RAM, LSI MegaRAID 9361-8i, RAID-6 (5x 1TB SSD)
I was observing that Hyper-V guests are resetted instead of saving and restoring state.
This happend in 7 of 10 Hyper-V Host reboots.
Making some tests, it seems to turn out, that the problem is not present without the November update kb3200970.
After installing the update, the guests are not correctly restored on some reboots.
There is no hint in the eventlogs. No error, no warning, no information.
Changing the shutdown option for the guest to "shutdown" instead of saving state works as expected. The guest is correctly shutted down and restarted again on every reboot.
I have reinstalled the complete system about 7 times, and the problem was always present after the update.
Severin
I’m seeing errors on VMs:
The VM and host networking components failed to negotiate protocol version '6.1'
The VM and host networking components failed to negotiate protocol version '6.0'
Both VM and host servers are 2016.
It’s +0 Windows Server versions difference and suppose to be supported.
Both VM and host are patched to same level.
One strange thing, tho:
If I connect to any 2016 host using Hyper-V manager on 2012R2 server, every VM (2016 and 2012R2) shows Network adapter status asDegraded (Integration services upgrade required)
But when I connect to 2016 host using Hyper-V manager on 2016 server there are no such errors on any VM.
Somewhat similar question was asked here, but I don’t think the answer is applicable:
I apologize for my complete ignorance on the matter but have to ask. We currently basically need 2 host servers in two different locations for safety in case LA slides into the ocean. We have two offices (one on each coast) so in theory we could do it with replication. We could also consider a colo facility. The CEO asked me if we could have it all in the cloud and I told him I'd find out as I did not know.
We basically need a 5 virtual machines - 1 file server, 2 app servers, 1 sql server and one remote desktop server. I suppose we could move our exchange to office365 hosted at that point.
I have no idea who offers an ability to float our VMs on the cloud, if it really is a diverse solution or we'd basically just be putting all our eggs into one colo facility and calling it the cloud.
Thanks.
In Windows Server 2016 by using the new VHDS (sets) format of disk you are supposed to be able to use Hyper-V replica. However I can't get this to work. Has anyone got this working?
Zimman2004
I appear to be having the same problem as is listed in this posting from 2012.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/6cf27c31-5d9b-4a18-9eea-3bfdcadeaa4a/virtual-machine-connection-stuck-on-connecting?forum=winserverhyperv
However I have not been able to resolve it. I have tried
I am trying to setup the initial VMs so that I can use them so just using RDP is not an option. The host is running on a Windows 10 Pro machine running the latest updates as of 12/5/2016.
I have seen some other posts where people resolved this with a reset of windows on their host but this is not really an option at this point.
Hi Techies,
We have got the requirement that create a separate VLAN for all the clients including Hyper-V VMs which is part of failover clusters 2012 R2.
Need your suggestions,how it is achieved in your organization?
We have four NICs.
Two NICs for Management which is teamed up.
One NIC for Live-Migration &
One NIC for Heartbeat
Can i Use LM NIC for backup VLAN? as i heard that LM can be managed management NIC itself.
Please suggest.
Regards,
KR