We have Broadcom BCM57840 NICs in our servers to connect to an iSCSI SAN. These cards have TCP Offload Engine and iSCSI Offload Engine (both licensed).
They have been left disabled in the past. Now I'm looking at optimizing things a bit... should I enabled them? Both or just one? I cannot find any piece of info about the correct configuration and the coexistence of the two offload engines.
Bye
Dario Palermo
Hi,
We have a Windows 2012 R2 Hyper-V Cluster running for several years now. On one of the hosts Domain accounts were no longer usable - had to Login using the local admin account. The VMs are running just fine - but not manageable through SCVMM or Failover Cluster Manager anymore. Powershell on hyper-v Level works.
I checked Logs... the only thing I found is in Systems: a DNS error followed by Event 5823 "The System sucessfully changed ist Password on the Domain Controller XXX. This Event is logged when the Password for the Computer account is Change by the System...".
The host is able to reach all DNS and AD servers. Name resolution works. I searched for the Event 5823 - found many entries regarding mix of AD 2003 and AD 2012... but this is not the cause of the problem as we never had an Active Directory 2003 or Domain Level 2003. Does anyone have an idea how to find the reason for this problem? I would try to use reset-computermachinepassword in hope of not having to reboot the server. Does anyone knows more about this situation and what works best?
Hi,
I built a Windows server 2016 with the Hyper-V role, and when I try to connect to a VM if fails with a "certificate mismatch" error. VM is located in the same server. It seems that the mismatch is because of the FQDN in the certificate (servername vs servername.lab.internal). I will appreciate any information that could resolver the issue that I am experiencing.
Thanks
Hi
What is the best way to share user files from host into Windows Server 2016 domain controller VM? I want the DC users to be able to access files but also keep the files on host for easy backup.
Thanks
Regards
Hi,
I have a Hyper-V 2012 R2 server with 4 1GB in a team for VM traffic and that's working fine. i have a second windows 2016 server activing as file server. I installed a 10GB NIC in each of the physical servers via a cross over cable. Gave them local IPs and can ping and file transfer between them and the file copy show 1GB/s. However if i then create a virtual switch using that NIC, and add a virtual NIC to a VM on that switch my file copies never go over 100MB/s (same I get wiht 1GB NICs).
Am I missing something here that needs to be done? I have 35TB of data to copy and really need 10GB speed. I can not mount the VHDs and copy that way as the VM is production and needs to be up.
Many thank in advance.
Matt
Matt Peek
I'm running server 2016 Data center edition. I upgraded an existing install from Server 2012 R2 to 2016. Everything seemed to be up and working fine, it been about a month since I upgraded. However I went to create a new VM today and after going through the wizard I get the error:
"New virtual Machine Wizard:
The server encountered an error while configuring the devices on New Virtual Machine. Hyper-V encountered and error trying to access an object on computer 'MYCOMPUTERNAME' because the object was not found. The object might have been deleted, or you might not have permissions to preform the task. Verify that the Virtual Machine Management server on the computer is running. If the server is running, try to preform the task again by using Run as Administrator."
After this the MMC will crash.
I have tried to create a new VM under both of the local accounts I have. This machine isnot domain joined. I have discovered that if I don't attach a VHD I am able to create the machine successfully, I can then go into settings and attach the VHD without error and the VM works. I also discovered I only get this error when creating an Gen 2 VM.
I have already tried running MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof, which I had to do initially after the upgrade to even get into the hyper-v console. I have also run sfc /scannow and DISM.exe /Online /Cleanup-Image /ScanHealth - both of which report no errors.
I would appreciate any help in resolve this issue and checking for any other underlying issues with Hyper-V. Thanks!
Hi
How can I assign host DVD, USB, Hard Drives to the VM?
Thanks
Regards
Hi, we have Exchange 2016 running on virtual Windows Server 2012 R2 on Hyper-V 2012 R2. For the databases we are using a ReFS volume, as recommended by MS. (It is a separate VHDX file that contains only one partition which is formatted with ReFS.)
The disk/volume is 4.5 TB in size, and though it never was full, the VHDX file grew to 4.5 TB. We did some cleanup and now have more than 2 TB free on the volume, but still I cannot shrink the volume to less than 4.4 TB. Also our SAN considers 4.4 TB as allocated.
I used SDELETE and PRECOMPACT to overwrite free space with zeroes, also optimized the drive (through the GUI and through Powershell with -RETRIM option), all of that multiple times, but without success. I guess that ReFS somehow does not really write the zeroed clusters but just marks them as unused or something like that, and the Hypervisor is not aware of that.
Is there anything I can do? (Except for creating a new VHDX and copying the files over, for which I don't have enough space.)
Host env WAS: Win10 Pro x64 current with Windows Update, vintage 2010 Intel Core i7 Lynnfield hardware, being retired
Host env NOW: Win10 Pro x64 current with Windows Update, Skull Canyon NUC, replacement machine
VMs: 3 VMs, 3 VHDs, two differenced from the third. Each VM was exported, from the powered off virtual state, about two months ago.
Problem: tried to import the VMs and get error "encountered an error while loading the virtual machine configuration... Import failed. Import task failed to copy file." Got error for each of the VMs when I tried to import it. Event viewer is not much more insightful:
"The description for Event ID 18440 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
%%2147943712
0x80070520
\\HOMESERV\Dick\DIY migration\XPSP3 Pro (diff from this)\Virtual Machines\AB33AB3E-0BC7-4D7B-A5B8-0B371F7A5DCF.VMRS
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines\AB33AB3E-0BC7-4D7B-A5B8-0B371F7A5DCF.VMRS
The locale specific resource for the desired message is not present"
I also saw some previous threads, via the Google, suggesting that I should create new VMs and "add the VHDs later" but there was no hint how one adds VHDs later or copies VHDs--with differencing chains involved--from one machine, or an exported VM, to another.
I must be missing something fundamental that I'm too ignorant to understand. Any helpful advice on how to migrate the VMs from the retiring machine to the new one would be greatly appreciated! Surely this is possible?
Hi,
From the following article: https://blogs.technet.microsoft.com/askpfeplat/2013/03/18/is-nic-teaming-in-windows-server-2012-supported-for-iscsi-or-not-supported-for-iscsi-that-is-the-question/ we know that we can use iSCSI over LBFO and that it has some advantages over MPIO in SOME cases. And that iSCSI over LBFO is supported for targets.
Now, I have some storages that only have 2 NIC, some have 3, others 4. On the other side, my hyper-v servers have 4,5,6,8 NICs. Thus I have somewhat 2 solutions for implementation.
If I use MPIO, I would need to create virtual adapters on the storage server to create the paths on alternate VLANs up to 6 VLANs (As some Hyper-V server would have 6 NICs for iSCSI traffic) or I would need to create teams on the Hyper-v servers to access the storage (over 2 vlans) and run MPIO on top of the teams.
In the other case, I would just team on both sides and run iSCSI traffic over the teams (initiator and target). One seems to involve way less moving parts than the other (straight up teaming instead of teaming + vlan + MPIO). And I usually feel that simpler is usually better.
So would that work while still offering good performances ? Would the iSCSI traffic be able to use the bandwidth of the aggregated NICs properly?
Thanks for any comments
I have two VMs that are part of a Hyper V cluster that both blue screened within an hour of each other over the weekend. Trying to figure out what caused this.
So far I know that it was ntfs.sys that caused the exception. BugCheck of 0x00000024.
Both of these point to a hard drive issue, but so far no luck tracking it down. I'm digging through all of the logs I can find, but nothing useful us jumping out at me except the BugCheck and the Kernel-Power events. I fell like maybe I'm not looking for logs in the right places and will admit that clustering is something that's new to me.
Environment consists of a three node Server 2012 R2 Hyper V cluster with shared storage on a Dell SAN. Guest VMs are also Server 2012 R2.
Thanks
I created a CentOS Hyper-V VM on a windows10 host. My CentOS VM is named DevEnv and am unable to putty to the VM (it gives me 'Host Does not exist' error). While debugging, i found that both my host and my VM have the same IPv4 address. The VM is connected to a virtual switch which i connected to the external WIFI nic to enable my VM to connect to the internet.
Can someone explain why the host and VM are getting same IPs (i checked that the mac for both are different and my VM is set to get dynamic IP)
Also, any ideas on why the VM is not network addressable?
HI All,
I have two Hyper-V hosts, where we have few vm's. I need to find the disk space of those vm's, Is there any script that can help for the same.
Regards,
Abhinav
Abhinav
I have installed a windows 2016 server and added hyper-v to it. I configured the virtual switch all needed to install a virtual computer. I am trying to install a Bitdefender server which I think runs on a Linux environment. I have tried to DHCP the network card and hard code it also. It never gets a DHCP address. when I put an address in I can ping the host system, but nothing on the network. I can also ping it from a workstation in the network.
Thanks very much
Kevin
Kevin
I am implementing a (2) node Hyper-V cluster with 7 VMs (2) of these VMs are DCs and are permanently located on local storage on each node. The other 5 are part of the cluster. From what I understand, this means I will need (48) 2-Core packs to license the VMs since, in a failover situation, up to (6) VMs has the potential to run on each node.
Is this math correct?
Additionally, if I am to use the clustered File Server role or the clustered DHCP Server Role, is there any additional licensing I will need?
Lastly, it was recommended to me that I put the DCs on local storage on each node in the event that something goes wrong with the cluster. That being said, should I have any similar concerns using the DHCP Cluster role?
Hi
2 fysical hosts running Windows 2012r2 with all windows updates/hyper-v patches.
Today i updated both host servers with newer broadcom nic drivers. 2 nics are used to iSCSI and 4 nics for all other hyper-v traffic. Before updating the first server, i drained all rules, so the second server had all guests running.
Updated nic drivers, rebooted, undrained all roles and then drained the second host server. Same procedure.
After both hosts was updated with new nic drivers and running normally, I noticed all my guest (both windows and linux) had rebooted. Just like if i did a hard reset from hyper-V.
This has not happened before, where I live migrated machines.
Any idea why the below happened?
Host2 Eventlog when host1 server was paused:
Cluster node 'Host1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a
Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Ownership of cluster disk 'Quorum Disk' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.
Cluster resource 'Quorum Disk' of type 'Physical Disk' in clustered role 'Cluster Group' failed.
The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.
Clustered role 'Cluster Group' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.
regards
robert
Thanks to this annoyance Here's my setup.
Single Test Hyper-V Nano 2016 TP5 on a Laptop, Single NIC. Cisco switch configured as follows
description Connection to test hyper-V
switchport trunk encapsulation dot1q
switchport trunk native vlan 21
switchport trunk allowed vlan 21,30-35
switchport mode trunk
This finally allowed me to have a trunk port for the laptop while still allowing the non-vlan tagged traffic to be allowed.
The problem now is, I connected to the server from my workstation using Hyper-V Manager Snap-in.
My first issue was how difficult it was to mount an ISO for the new VM. You can only specify the hosts DVD drive (How this is remote management beats me), can't copy anything to the Hyper-V server through Hyper-V Manager (AFAIK). I literally had to copy the ISO onto a USB stick, plug that into the laptop, open cmd and copy the file to the hyper-v's local storage. Man that is painful.
Attempting to connect to a hyper-v system that isn't domain joined. Also Really difficult (When connecting from a domain joined machine anyway).
And finally my biggest pet peeve from this testing.
I went to create a "external" vswitch on hyper-v manager. I created an external vswitch, using the only NIC available (the only one it has) specify the vlan ID for it (Wow amazing MS didn't forget to add that :S). Sure enough it says connections will fail while making the changes. Sadly I lost 6 pings, then 3 pings came back, and then it completely died. I can't reach it. When I login directly I can no longer ping the gateway.
How can I create a "external" vswitch, while retaining the non-vlan tagged mgmt IP... or better yet... how can I add a mgmt vlan ID to the dang MGMT network!!!!??!?!?! ARGGGGG
We are testing replication between two 2012 r2 hyper-v hosts. We are wanting to use replication for DR purposes.
We have 2 VM's. One is the DC for the domain. The other is an Exchange 2013 server. Only one DC exists in the domain. We have enabled replication for each VM.
Planned failover works fine for the Exchange 2013 server, but stalls at "failover to replica server" for the DC.
In a "best practices" scenario, is a running DC required to complete a planned failover? Since we only have one DC, and it is the VM we are trying to perform a "planned failover" for, in theory, should this work? We cannot find any documentation that answers this question. We have found documentation indicating that 2012 r2 hyper-v is DC aware.
We are considering having a dedicated DC VM on each hyper-v host that is not replicated to remedy the planned failover issue, if that's needed. But not unless we have to. Just the one DC works great for small network deployments.