Hello,

At our company, we use Veeam to back-up all VMs on our Hyper-V servers.

We ran into an issue, when we needed to restore a sharepoint 2016 server.

The VHDX that contained the MS-SQL database files was corrupted.

** We had several weeks of SUCCESSFUL VEEAM Backups** that when restored, were corrupt.

Veeam support's response is that it is a Microsoft issue.

What is the best practice to test/confirm or otherwise verify that a VHDX and its file system is not corrupt?

The point of backups is to mitigate risk, I can't imagine that we are the only company to experience this or ask this question.

This question is NOT about backups, it is what is the best practice to ensure what is being backed up is valid.

Thank you.

I'm currently in the process of migrating all of our virtual servers from OVirt to new Hyper-V 2016 clusters.

Two of the VMs that have been migrated are running Centos 7.5 and they have a few docker containers on them.

They both have the hyper-v tools installed on them that come from the Centos repositories.

When I take a checkpoint of these VMs they hang permanently with the following recurring message:

task hv_vss_daemon:1397 blocked for more than 120 seconds. and the last entry in /var/log/messages is about Hyper-V doing a hot backup.

At this point the VM's are unusable and I have to force them off via task manager as the native hyper-v 'turn off' button refuses to do anything.

Things I have tried:

Upgrade to the latest version of Linux Integration tools from the MS website - this made no difference

Disable SELinux on the guest - this made no difference.

Things I did that made it work:

- Stop the docker containers and create a checkpoint (checkpoint seems to complete without issue)

- Remove the Hyper-V agents from the guests (checkpoint seems to complete without issue)

Has anyone come up against this before ?

For the time being, I'm just backing up via Veeam with the hyper-v vss agent removed from these guests as crash consistent backups should be fine for these.

I'm running FreeBSD 11.2-RELEASE-p3 on Hyper-V Server 2016 in a generation 2 VM. The server is recently updated. The administration console, in the tab "Network Functions" informs me that the status of my vNICs is "Degraded (Integration services update required)".
I'm not sure if this is simply because I'm using the latest versions of both freeBSD and Hyper-V.
Does anyone know if there are updates of the integration services for my VM and if there are, how to install them?

I really appreciate your help and experience.

PD. I haven't found any performance problems.

Best regards,
Gabriel

When i try to install windows server 2016 evaluation edition in hyper-v,  its giving error in the second screen of installation.

''a media driver your computer needs is missing. this could be a DVD,USB or Hard disk driver. If you have a CD, DVD or USB flash drive with  the driver on it, please insert it now.''

I tried from ISO file, physical drive & by downloading the image twice but same. i also googled the issue but i didn't got the right solution yet. please help

Thank you 

I have in production 9 Hyper-V Server 2012 R2 host and 2 Hyper-V server 2016 host in a domain environment.
From a Windows 8.1 Pro (x64) I connect through Hyper-V Manager to all hosts without problems.
However from a Windows 10 Pro (x64) when I try to connect to the hosts using Hyper-V Manager, there are 2 of them (2012 R2) that throw me the following error:

The domain user that I start Hyper-V Manager with in Win 8 and Win 10 is the same, so I understand that it is not a user permission problem. I also disabled the firewall on troubled hosts, but I can't connect either.
Does anyone know why this error could be? Will it be a problem with the Hyper-V Manager console version of Win 10? 

Thank you for your help.

Best regards

Gabriel

I have a clean install on an HP ML350 G10 server of Windows 2019 standard now that it was re-released.

The HP SPP worked fine to get all drivers loaded since 2019 isn't supported yet for the intelligent provisioning process.

Server activated, all four network card work fine.  No bangs in device manager, all devices have drivers loaded and are recognized.

I've added the Hyper-V role, that goes fine. 

Then trying to add an adapter to the hyper-v switch, it fails.  Ultimately the error is that it can't find a file.  This is trying to get the adapter installed via the GUI.  So I dropped to powershell, tried to create it there, same error.  Tried every network card, same error. 

Removed Hyper-V role, re-added it, same error.

Removed Hyper-V role, then when I added it, tried to add the interface to the network switch during the GUI install of the Hyper-V role.  It didn't give an error, but when the install was done and system rebooted, there was nothing for the hyper-v switch.  And trying manually via GUI or powershell still does the same thing.

I'm not allowing the management operating system to share the adapter, although I tried with letting that happen and the result is the same.

Some of the things I've seen for older OS's like 2012 and 2016 said to remove the "Hyper-v Extensible Virtual Switch" from the bindings on the cards first then try again, but that won't uninstall.  I get an error 0x80071779

I've removed and reinstalled the drivers, and a few different versions of the drivers, including the ones it finds automatically when I just went to the network card properties and told it to find drivers to update as well as the current and previous versions on HP's website for this adapter.

Anyone else see this?  It always comes back to "Error applying virtual switch properties changes. Failed while adding virtual ethernet switch connections."  The details show the GUID of the adapter, with the final text, "The system cannot find the file specified." and an error code of 0x80070002

Another post mentioned they solved something similar on an earlier windows build by disabling internet connection sharing - that's already disabled.

Another post mentioned antivirus causing this in a previous Windows server build - but this is a clean windows install, no antivirus is installed here.

One of the joys of playing with a new server build right at release...

Just in case it WAS something that was corrupted from the original install, I nuked it, reinstalled clean from scratch, and the problem persists.

I wish I had another spare server I could test this with to see if it's a bug with Windows, or simply some incompatibility with HP.  But since other people have had this issue since 2012, I'm guessing there's just something I will have to wait to get updated with by MS or by HP.

I made the mistake of posting the question on spiceworks and got people "instructing" about everything EXCEPT the actual problem.  It's a bit like posting on an auto forum about a brake issue, and people "answer" complaining about the color of your car...

Since I have a business continuity device on this network I have no qualms about deploying 2019 this early for a Hyper-V role, as I can spin up any of its guests within minutes if something happens, so no complaining that "you shouldn't use 2019 in production until after the first service pack," or other such.  Let's please try to stick with the actual technical issue.  I prefer to NOT have to deploy a 3+ year old OS on a brand new server now if I don't have to.

Thanks for any guesses... 

John

John

I have a cluster, 2 nodes. There are repeating events id 25, every few second:

The MAC address 00-15-5D-AE-25-19 has moved from port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External) to port 6D5ABBEF-0A8E-4F5D-8CC2-0871846CEF82 (Friendly Name: BCK).

The MAC address 00-15-5D-AE-25-18 has moved from port 53A6AB28-EBD3-4F72-B690-69406077B8A7 (Friendly Name: vSwitchFN_External) to port 9A8780F9-D931-4F85-B087-397A2F718C01 (Friendly Name: HB).

Config:

No NLB (MAC spoofing) on VMs.

PS C:\Users\pero>  Get-NetLbfoTeam

Name                   : mgmt
Members                : {M2, M1}
TeamNics               : mgmt-624
TeamingMode            : Lacp
LoadBalancingAlgorithm : Dynamic
LacpTimer              : Fast
Status                 : Up

Name                   : vm
Members                : {K2L1, K1L1}
TeamNics               : vm
TeamingMode            : Lacp
LoadBalancingAlgorithm : Dynamic
LacpTimer              : Fast
Status                 : Up

PS C:\Users\pero> Get-VMNetworkAdapter -ManagementOS

Name          IsManagementOs VMName SwitchName MacAddress   Status IPAddresses
----          -------------- ------ ---------- ----------   ------ -----------
BCK           True                  vSwitchFN  00155DAE2519 {Ok}
HB            True                  vSwitchFN  00155DAE2518 {Ok}
SETswitchSMB2 True                  SETswitch  00155DAE250C {Ok}
SETswitchSMB1 True                  SETswitch  48DF371EFC2D {Ok}
LM            True                  SETswitch  00155DAE250D {Ok}

PS C:\Users\pero> Get-VMSwitch

Name      SwitchType NetAdapterInterfaceDescription
----      ---------- ------------------------------
vSwitchFN External   Microsoft Network Adapter Multiplexor Driver #2
SETswitch External   Teamed-Interface

PS C:\Users\pero> Get-VMNetworkAdapterVlan -ManagementOS

VMName VMNetworkAdapterName Mode   VlanList
------ -------------------- ----   --------
       SETswitchSMB1        Access 1980
       LM                   Access 1981
       HB                   Access 1044
       BCK                  Access 887
       SETswitchSMB2        Access 1979

PS C:\Users\pero> Get-NetAdapter

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
mgmt-624                  Microsoft Network Adapter Multiplexo...       6 Up           F4-03-43-5C-75-91         2 Gbps
K1L2                      HPE Ethernet 10Gb 2-port 561T Adapter        32 Up           48-DF-37-1F-0F-09        10 Gbps
K1L1                      HPE Ethernet 10Gb 2-port 561T Adap...#4      30 Up           48-DF-37-1F-0F-08        10 Gbps
SMB2                      Hyper-V Virtual Ethernet Adapter #5          35 Up           00-15-5D-AE-25-0C        20 Gbps
SMB1                      Hyper-V Virtual Ethernet Adapter #4          11 Up           48-DF-37-1E-FC-2D        20 Gbps
LM1                       Hyper-V Virtual Ethernet Adapter #3          16 Up           00-15-5D-AE-25-0D        20 Gbps
BCK1                      Hyper-V Virtual Ethernet Adapter #2          27 Up           00-15-5D-AE-25-19        10 Gbps
HB1                       Hyper-V Virtual Ethernet Adapter             19 Up           00-15-5D-AE-25-18        10 Gbps
M2                        Broadcom NetXtreme Gigabit Ethernet #3       20 Up           F4-03-43-5C-75-91         1 Gbps
M1                        Broadcom NetXtreme Gigabit Ethernet          24 Up           F4-03-43-5C-75-90         1 Gbps
vm                        Microsoft Network Adapter Multiple...#2      17 Up           48-DF-37-1E-FC-2C        20 Gbps
K2L2                      HPE Ethernet 10Gb 2-port 561T Adap...#2      15 Up           48-DF-37-1E-FC-2D        10 Gbps
K2L1                      HPE Ethernet 10Gb 2-port 561T Adap...#3      18 Up           48-DF-37-1E-FC-2C        10 Gbps

The events intensively fill the log and sometimes network connectivity for these virtual adapters (BCK, HB) is temporary lost.

What is problem?

Hello

Currently I have a Host with Hyper-V Windows 2016, which replicates my Vms to another Host with Windows 2016, through Hyper-V Replica.

But when Vms backup is triggered, replication continues, and I get these events:

Microsoft-Windows-Hyper-V-VMMS / Admin 19060

I wonder if this event is because of the backup that is interfering in replication and vice versa

If so, would you like to know if it's a good idea to stop replication when the backup is done, and then continue with replication?

MCP - MCTS - MCTS AD

Hi all, let me first give you a rundown of our current setup:

2 Physical Servers (one is the main, the other serves as Hyper-V replication server)
6 VMs on main server. One is a terminal server users RDP into using port XXXX. The other is meant to be a mirror of the first running RDP on port YYYY. In case of failure on the first VM, users can change RDP ports and connect to the second.

I'd like a way to run a manual or automatic file sync between the two for certain directories.

Any suggestions?

Also open to suggestions for an easier solution for minimizing downtime if this situation happens. I was researching HA Clustering but that's not an option for us currently as we only have one LAN.

Hey all,

I've been trying to enable Switch Embedded Teaming on Windows 2019 [Version 10.0.17763.107] using the below command:

New-VMSwitch -Name SETSwitch -NetAdapterName "em1","em2","em3","em4" -EnableEmbeddedTeaming $true -AllowManagementOS $true

The command executes successfully and creates the virtual switch but breaks the NICs.  In device manager they are shown with an exclamation mark and under details show the below error:

"The device cannot start. (Code 19) {Operation Failed} The requested operation was unsuccessful."

I have tried updating the NIC firmware and upgrade/downgrade of driver with no luck.  

I have also tried the exact same process on Windows 2016 on the same hardware and it works perfectly.

The hardware is a Lenovo SR650 and NIC is Intel X722 1GbE.

Any ideas as to what's going wrong?

Thanks,

Mike

Hello,

I'm trying to create a VM package that I can deploy in hyper-v. I want to disable the ability of users of this Vm from creating additional VMSwitches because I will be applying an extended ACL to the VM network adapter. These VMs will be hosted on the users PC. Is it possible to disable the ability of the users to alter the VMSwitch or VM settings? I've been searching for an answer to this for some time and I cant find anything on existing forums.

Apologies if this is not the right forum.

So I was preparing a new server to host virtual machines. This is a Dell PE r710, Dual quad-core Xeon processors, 48 GB RAM, 2x 72 GB SAS drives. The server has Hyper-V Server 2008 R2 installed. iSCSI volumes hosted in a Dell EqualLogic SAN will host the actual virtual machines. We have 5 of these with similar setups, 3 of which are setup in a cluster. We have 2 set aside for additional projects. These will not be clustered as they will be hosting Lync virtual machines. Anyway we have 1 server setup and working with 2 VM's. The 2nd server will initially host 2 additional VM's. My goal was to format the iSCSI volume on the 2nd server and prepare it to host VMs. Except I accidentally logged into the 1st server (it's one of those days - I was interrupted as I was typing in the server name into Remote Desktop and it auto-populated the first server instead of the 2nd) and begin formatting the volume. Needless to say Lync stopped working and the VMs crashed. I immediately recognized my mistake and stopped the format but obviously it was too late.

I was hoping I could recover the data on that volume. We have a trial of this software called GetDataBack NTFS edition. It can recognize the volume ok and it can scan it and see files. Unfortunately it does not see actual VHD files. Instead what happens is that it sees the VHD files as separate volumes/partitions/etc and recovers the data within the VHD files. Not sure if it should do that, waiting on a response from Runtime. Kind of cool in a way if we ever needed to recover data within a VHD file. Anyway, does anyone know of software that can recover data from a volume but not scan the contents of the vhd file and include that data in the recovery? By this I mean I want to recover the actual VHD files, not the data within. Perhaps Virtual Machine Manager can do something? We do have it installed and manage our VM's with it. It would save us the trouble of re-deploying Lync. Apparently there's a lot of ADSI edits needed to undo the changes Lync did to AD/ Even migrating users back requires some ADSI edits. Trying to find those online someplace just in case.

We did not have backups yet of these 2 VMS as we just recently got them setup and have moved a few users over (some of us from IT). We still had some configuration/tweaking/adjustments to make before migrating the remainder of our OCS users. I know, I know, backup backup backup. The SAN we have can even do snapshots of iSCSI volumes but we didn't even think of enabling it yet.

Regardless in what happens with the VM's, I enabled Windows Server Backup and will immediately setup nightly backups once the VM's are operational again. I will also have our SAN admin enable snapshots, and just for laughs I will also enable snapshots on the individual VM's. We're also currently testing out Data Protection Manager. Kind of wish we already had it implemented....sigh...

Thanks,

Banging my head against a board with a nail in it...

The snapshot I'm trying to merge is 600GB, the parent main-disk is 1TB. There's 1.92TB of free space on the disk. Running Windows 2012 R2. Google didn't really direct me anywhere useful unfortunately

Hi,

Would you please advise how to access the symbol vmms.pdb for vmms.exe 10.0.14393.2248 ?

The symbol for vmms.exe isn't able to be accessed through http://msdl.microsoft.com/download/symbols.

I found this blog, and expecting for some way to access the hyper-v symbols : 

https://blogs.technet.microsoft.com/virtualization/2018/04/25/hyper-v-symbols-for-debugging/

Regards, Toshi

Hi,

Presumably because WS2019 just came out, I can only find 1 YouTube video which explains from A-Z how to install and configure Hyper-V on WS2019. Unfortunately, that video is without sound and is very blurry, so I can't really see what the demonstrator is doing.

I am a total newbie at virtualization. I would greatly appreciate it if someone could point to a video or written tutorial on how to do this.

TIA,

mlavie

Dear All

I want to add 3 nodes to a existing 3 node cluster with hyper-v on windows server 2012 R2 R2. Storage LUNs are from VNX storage and these new 3 nodes are added to the same zone of existing cluster. I can see same LUNs in the disk management of all 3 new nodes. old nodes and new nodes have different hardware. Kindly let me know that how to proceed further. Is it possible simply to install clustering feature and then run validation ? or if i run validation with storage, it will bring resources offline on old nodes ? if then how to proceed futher ?

Hello Tech Brains.

I cant reach ma server.

i receive a Reply from 192.168.0.220:Destination host unreachable

please help