So apparently this is an incredibly rare error since googling it produces no results in english other than one cryptic page. This is a clean server I am doing a clean image for. The host is up to date and I tried both creating a new VM from installation media and even trying to mount a blank server VM I've used for installs before. Both fail with the same exact error. I've disabled virtualization based security in group policy but it still shows as running in system info, even after a reboot, so I'm assuming this is something new that requires a special work around, although I can't find what I'm doing wrong. I just setup a bunch of servers for another client a few months ago and none of these problems presented themselves.

Hello,

I have a little test environment using nested virtualization in Windows Server 2019 wehre I need to use VLANs.

The environment consists of:

- pHost > a physical server with Hyper-V role
- vHostSwitch > a private virtual switch on pHost

- vHost1 > a virtual server on pHost with Hyper-V role, connected to vHostSwitch(mac spoofing & ExposeVirtualizationExtensions enabled)
- vmSwitch > an external virtual switch on vHost1 (shared with management os)

- vHost2 > a virtual server on pHost with Hyper-V role, connected to vHostSwitch (mac spoofing & ExposeVirtualizationExtensions enabled)

- vmSwitch > an external virtual switch on vHost2 (shared with management os)

- VM1A > a virtual Server on vHost1, connected to vmSwitch (on vHost1)

- VM1B > a virtual Server on vHost1, connected to vmSwitch (on vHost1)

- VM2A > a virtual Server on vHost2, connected to vmSwitch (on vHost2)

- VM2B > a virtual Server on vHost2, connected to vmSwitch (on vHost2)

So far, so good. All Servers can ping and reach each other without VLANs.

Also everthing is fine, when I configure a VLAN on the pHost by Setting the same VLAN ID in the Hyper-V network Cards for vHost1 and vHost2.
vHost1, vHost2, VM1A, VM1B, VM2A, VM2B can still ping each other, and as expected can't ping VMs with different or no VLANs connected to vHostSwitch.

But what I need is setting up a VLAN for VM1A and VM2A, and a separate one for VM1B and VM2B.

As soon as i set VLANs in the Hyper-V network cards for those 4 VMs, the VMs on vHost1 cannot cummincate with VMs on vHost2 in the same VLAN.
This doesn't change wether or not I'm using VLANS on the pHost for the vHosts.
VMs in the same VLAN within one vHost can communicate without a problem.

Also Setting a VLAN for the Management OS in vmSwitch on vHost1 and vmSwitch on vHost2 stops the vHosts from communicating with each other.


In a real Environment, vHost1 and vHost2 would be physical servers connected to a physical VLAN capable switch.
But in nested virtualization the vHostSwitch needs to play the role of the physical VLAN aware switch.
While Hyper-V switches definitely can handle VLANs, it seems they drop VLAN tagged packets comming from Hyper-V switches from within the nested virtualization.

So is there any way to make VLANs work between VMs between different nested Hyper-V hosts on the same physical Hyper-V host?

thanks in advance!

Hi,

i've HV 2012 R2 with existsing VM's on it that it is on a shared storage.

what are my options if i need to create a cluster for that host with the active VM's on it?

can i create the cluster on the exists host and then add another host to the cluster or i need to create cluster from the second host and then add the first host?

what about the shared storage and the active vm's do i need to turned them off when i add the host to the cluster?

what will happened to the shared storage on the main host when i add it to the CSV?(i can map the LUN to both server)

THX

Hi all,

This seems like a common problem on the internet but I haven't found a definitive solution anywhere.

Sometimes when booting up a Windows 10 VM, it will boot to a black screen in either a Basic or Enhanced session.

When I switch from the one to the other magically I can see that the VM has indeeded booted. The mere switching between the session types (Basic to Enhanced or vice versa) fixed the problem.

Obviously however it would be nice to not have to do this.

Does anyone know of the reason why this occurs and how to fix it once and for all? :) 

I am using the latest HyperV manager with the latest graphics drivers.

m

Hi,

What is the recommended practice for Daily/Weekly checklist on the Hyper V 2012 r2.

Thank you!

Regards,

farhan508

Hi, I am charles

I am now attempting to enable SR-IOV with NVMe SSDs on Windows Server 2019.

I already enabled SVMs for AMD CPUs and IOMMU and ACS and ARI in the BIOS.

Then, although Hyper-V was installed on Windows, only the SR-IOV Enable button for Network Adapter was found.

How do I enable SR-IOV for SSDs?

When I checked Device's PCIe Register, Host set up almost all of the SR-IOV related Registers.

Only except VF enable and Memory Space Enable.

If I set them manually, I can access the device inside through the VF BAR.

However, the device manager does not recognize it as a new device.

What should I do to solve this problem?

Hi all,

I am having a nightmare with a DC upgrade. We currently have a 2012 R2 Standard running hypervisor services. To get more out of the box we ordered a DC licence. I have access to the Microsoft licencing site and have got a copy of what I believe to be our key but I cannot get the OS to accept this and upgrade to DC.

So – several questions…

Can I upgrade from standard to DC with the appropriate key? I did specifically ask for this when we went through the quote process and was informed that the keys we would be provided with will be suitable to do an upgrade without rebuilding our hpervisor.

The error I am getting is

Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid

The key I am using is from the micorsoft site – the section is

“Windows  Server 2012 Datacenter”

I have used the KMS key and in the web site it does show our company name as the organisation so I guess that means we are all paid etc.

I did check in the KMS server and nothing seems to have been registered in there (not sure what I was expecting but it wasn’t nothing) As an extra bit of fun out network is largly behind a firewall with no internet access but I do know that the KMS server is allowed thorough and this is working – last contact reported was only a few days ago.

So – can anyone point me in the direction of installing the key and getting this OS upgraded if

cscript c:\windows\system32\slmgr.vbs –ipk xxxxx-xxxxx-xxxxx-xxxxx

is not going to work?

Thank you

Kevin.

Good day, we have configured S2D cluster on Windows Server 2019 1809 (17763.1039) cluster successly pass tests via Test-Cluster and working with no problem, but if we moving virtual machive using live migration from other S2D cluster ( Windows Server 2016 ). After migration, vm working some time ( random 1 - 8 hours ) and rebooting with errors. 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:25.917237000Z" /> <EventRecordID>352436</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security UserID="S-1-5-18" /> </System>
- <EventData><Data Name="BugcheckCode">265</Data> <Data Name="BugcheckParameter1">0xa39ff768722a4831</Data> <Data Name="BugcheckParameter2">0xb3b703eec4ab58f9</Data> <Data Name="BugcheckParameter3">0x2000001a0</Data> <Data Name="BugcheckParameter4">0x7</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData></Event>

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:29.303375100Z" /> <EventRecordID>352517</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security /> </System>
- <EventData><Data Name="param1">0x00000109 (0xa39ff768722a4831, 0xb3b703eec4ab58f9, 0x00000002000001a0, 0x0000000000000007)</Data> <Data Name="param2">C:\Windows\MEMORY.DMP</Data> <Data Name="param3">681c7c75-c8ec-42ae-ad15-008309d23974</Data> </EventData></Event>

If stop vm on one cluster manually move files and start vm works correctly.

Good morning!

I'm running into a problem with Hyper-V and I don't have a lot of information to troubleshoot off of. I'm hoping the experience and knowledge here will help me zero in on a solve for this.

Basics:
I'm trying to enable replication of a single VM'd server from my client's office in Dothan to their office in Auburn (War Eagle!). I'm also trying tore-enable replication of two user VMs from Auburn to Dothan. Dothan's hypervisor is MS Hyper-V running in Windows Server 2019 DE. Auburn's hypervisor is MS Hyper-V running in WS2016 DE. The VM to be replicated from Dothan is WS2019 DE acting as a DC and an file server. The VMs being replicated from Auburn are Win10 Pro workstations. The purpose of all replication is simple redundancy; offsite backup of each VM in case of catastrophe. The WAN infrastructure is VPN over broadband. The organization uses ADDS with all users and machines in one domain.

History:
I'd successfully set up replication of the two VMs from Auburn to Dothan a few weeks ago. I ran into issues with Kerberos that were solved by editing the registry on each hypervisor so that Kerberos had to use TCP, and eliminating packet fragmentation at the VPN routers. Those VMs were replicating consistently until this past weekend. 

During the weekend, I had to reformat the volume where the VMs are stored in Dothan. The Auburn server is a mess that I inherited from the last IT guy, nothing is virtualized on this machine and I want some redundancy, so I was going to use DFS to replicate critical files from this server to Dothan. However, when I built Dothan I used ReFS for the storage volume, and since DFS won't run on ReFS, I decided to back up Dothan, burn down the storage volume, reformat with NTFS and restore. I used Win Server Backup in WS2019 to perform a bare metal (full) backup to an external disk. Before running the backups, I merged all checkpoints back into each VHD and created new thin-provisioned VHDs from my thick-provisioned VHDs. I successfully tested each VM with the thin-prov VHDs attached before shutting all VMs down and running the backup set.

Problem:
After formatting the storage volume NTFS, I ran into issues restoring Hyper-V directly from WSB. Instead, I restored the VHDs, built new VMs for my 1 server VM and 2 replicated user VMs, and reconnected the VHDs. Everything boots up in Hyper-V and the machines run normally. The server VM is up and running with no issues. All the data is there and I can remote into each machine. Once the dust had settled, I attempted to enable replication of the server VM from Dothan to Auburn but received the following error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupOcDu6lQhOgOmLUQ?e=52vnr2

This is proving to be maddening for me because there's no data associated with the error. No code or whatnot. I'm not receiving any errors from the replication wizard in terms of "unable to determine configuration", authentication errors, or anything during the process to make me think these two servers can't talk to each other. They're talking about this replication, they're just not kicking it off. 

In an attempt to control for other variables, I decided to re-enable replication of the two VMs from Auburn to Dothan. When I tried, I got this error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupPTJzbNDNF_oiPgw?e=hWtNbE

Unspecified errors are a joy...

I've done my rounds on search engines and tried everything I can think of, but I just keep running into this wall. These VMs were replicating fine before all of this. 

Misc:
The Dothan server uses two volumes for Hyper-V. Hyper-V configuration files and small VHDs are stored on E:, which is SSD-based. The Dothan server VM uses a small VHD on E: for it's operating system, and it's smart paging file is parked there too.

Large VHDs and all Hyper-V Replica (inbound-replicated VMs) is stored on D:. The Dothan server VM uses a VHD stored on D: for data storage in its role as a file server. Both my Auburn VMs are stored on D: when they replicate to Dothan, which is exactly how they were before I made all these changes over the weekend.

I've rebooted both hypervisors and I've checked all the VSS writers. No errors there. I can create standard and production checkpoints for each VM, the two VMs in Auburn and the server VM in Dothan. 

If anybody can help point me in the right direction on this, I would greatly appreciate it, and I'd be happy to take you for a beer anytime you're in this part of the American south!

-MB

We have a project with a customer to create a Hyper-V Cluster with 3 hosts.

They are all prepped with one 4 port copper network card and one 2 port fiber card.

The idea is to have Cluster heartbeat and Live migration traffic on the fiber cables and all other traffic on the copper cables.
We have no fiber switch available so the fiber is connected directly between the hosts, one cable between each host in a triangle.

My initial thought was to create a SET team on the 2 fiber ports on each host and attach 2 virtual cards on each, one for Cluster and one for Live Migration.

But now I have realized this might not work at all.
You'll have to correct me if I'm wrong here but both fiber ports won't be active at the same time on the SET team, leading to connection issues to the host with the not active connection connected.

Another thought I had was to maybe not have a SET team at all and instead create 2 Vnet adapters for each function (Cluster and Live Migration). And then have 1 of them to one of the fiber ports and the other to the second fiber port.
This will create more Virtual adapters on the host, allocate more IP addresses and create a bit more complex setup to maintain. But might be needed to solve this issue?

How would we design this in the best way when we have no fibre switch to use?
On this link is a visio diagram showing the setup: https://imgur.com/egTOgBx

Hi

I have a problem where i would like to recover from an avhdx file. the parent is not there in the chain and my avhdx file is about 50GB. Any help on how this can be done or is there any software that i can use to recover the data on that file.

I have created a Windows 2016 hyper-v failover cluster with 2 no hypervisors (soon to be 3) and a NAS for storage. 

Each hypervisor has 4 NICs so I used 2 of the NICs for MPIO iSCSI and the other 2 NICs I created an LACP team to our Cisco switches.  I have one external vswitch that is configured with the team logical adapter. 

The team is also a trunk link so I can pass mutiple vlans on it and it currently has a management vlan for the hypervisor physical IPs and a client traffic vlan,  see pics below - 

So my questions are - 

1) Is what I have enough for it to work properly or should I be looking to have additional networks for live migration, cluster communication etc. 

2) If I do need extra networks how exactly do I go about creating them ie. I can add any number of vlans I want to the team/virtual switch but how do I then get FCM to see and use them. 

3) If 2) can I add additional networks without any downtime or at least one hypervisor at a time so I can drain roles to the other etc. 

I have a horrible feeling I may need to rebuild the cluster to get this setup optimally. 

Any pointers would be much appreciated. 

Hi All,

Good day.

Will need some help on this, recently had converted my domain controller from VM ESxi5 to Hyper-v 2012 R2 host.

My domain controller runs in window 2008 R2.

The server is able to power on after the conversion, but only issue is i am unable to run disk management. Also the Virtual Disk Services (VDS) and volume shadow copy services (VSS), is no long listed on services.msc and i am not able to turn it on.

Is there anyway or how could i fix this issue? As my backup required VSS and VDS to work.

Hi community, 

after your authorization,

i m very happy to present my contribution to you, it is a free tool created by myself, to help everyone use Hyper-V on local or remote server, and encourage the people to use Hyper-V.

all your feedback is welcome,

this is the link :

https://gallery.technet.microsoft.com/Hyper-Virtual-Easy-Manager-6384c1c6

if anyone has any  suggestions or improvement, please feel free to give me the advice

Hi all

Two of our clusters are running on shared storage, through SOFS:

• hypervCluster1 - Windows Server 2016 - Running Virtual machines
• hypervCluster2 - Windows Server 2019 - Empty
• sofsCluster1 - Windows Server 2016

Both of our HyperV clusters have access to the same SOFS shares, granted through SCVMM.

This means that when we are doing Virtual Machine Migrations between the two clusters, SCVMM isn't initiating a storage migration, since both clusters have access to the same storage (SOFS Shares).

Question1:

Can anyone able to tell me if the ConfigStoreRootPath should be different on each cluster, or if we should keep this the same?

We have tried both, without live migrations working.

Question2:

Why isn't live migration working?

Events on source Hyper-V host (Hyper-V-VMMS-Admin):

• Virtual machine migration for 'vm01' failed because configuration data root cannot be changed for a clustered virtual machine. (Virtual machine ID ...)
• Virtual machine migration operation for 'vm01' failed at migration source 'hypervHost03'. (Virtual machine ID ...)
• Planned virtual machine creation failed for virtual machine 'vm01': %%2147778642 (0x80048052). (Virtual Machine ID ...).
• Virtual machine migration operation for 'vm01' failed at migration source 'hypervHost03'. (Virtual machine ID ...)

Events on target Hyper-V host (Hyper-V-VMMS-Admin):

• User 'runas-scvmm-admin' failed to create external configuration store at '\\sofs\Volume4\vm01': General access denied error. (0x80070005)
• Received invalid or corrupted data for a Virtual Machine migration.
• 'vm01' Failed to create Planned Virtual Machine at migration destination: General access denied error (0x80070005). (Virtual machine ID ...)
• You are using Kerberos authentication option for live migration which requires setting up credential delegation. The access denied might have been caused by incorrect credential delegation setup.

Thanks in advance for any replies!

Hi All,

I have a simple question that Google nor Bing can definitively answer. I have a cluster with 3 storage devices, Cluster Volume 1, 2 and 3.  I wan't to remove Cluster Volume 1. There is no data on that volume, so not worried about retaining any data. If I remove the volume from the cluster, do Volumes 2 & 3 stay at  2 & 3, which I would assume is the proper behaviour. I just want to make sure that the system doesn't reshuffle the volume numbers and cause all my vm's to go offline.

Ok, so this is a 2 part question. Say I want to add another volume later, will that become Volume 1 or 4?

Thanks in advance.

Event IDs on B2

Event ID 16300 Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

Event ID 33686 Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).

Event IDs on B1

Hyper-V failed to enable replication for virtual machine 'VMNAME: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

This only happens to some VMs, those that previously used Certificate based replication.

1. Domain A VMs are replicated to Domain B via certificate based replication.
2. Domain A servers are running Hyper-V Server 2012R2 or 2016.
3. VM version is 5.
4. VM is failed over to Domain B Hyper-V replica server B1 running WS2019 Datacenter host and started, no errors.
5. VM is replicated to a different WS2019 Datacenter host B2 in Domain B and is failed over.  It's still using certificate based replication.
6. Replication is removed on all hosts.
7. VM is deleted on but B2.
8. VM is shutdown and upgraded to version 9.  VM starts and works fine.
9. VM is deleted from B1.
10. Enable replication fails from B2 to B1 with errors above.
11. I can create new VMs on B2 and replicate them with or without certificate based replication without error.
12. I have searched and removed all files/folders with A10F389C-C365-4829-A748-36EAA9009690 in their name on B1.
13. Where is B1 still storing information about A10F389C-C365-4829-A748-36EAA9009690?

-=Chris

Hello 

Can someone help resolve the error reported when starting of VM Unnamed VM could not initalize, An attempt to read or update Virtual MAchine configuration failed Ran out of memory 0x8007000E VM ID.

The Host has enough memory to start the VM.

Regards

NAvin

NJ

Hello,

I am encountering some errors and warnings on a windows server 2019 with hyper-v role installed and i am not able to figure out where to get the situation.
On a windows server 2019 with hyper-v role, I get the error from these errors:

At the same time, in the virtual machine to which the error on the host refers, i see those warnings:

i made some research and i found this: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55 ( 0xC0000044 STATUS_QUOTA_EXCEEDED ) but i don`t understand at what QUOTA refers to.

can someone give me a clue? any help will be appreciated.

Thanks