I am setting up a home server for my father who has, up until this point in time, clung to the Windows Server 2003-based Windows Home Server 1.0 product.  The box I'm using is an AMD A8 based machine with an ASUS AMD A88X based motherboard.  I'm running Hyper-V Server 2019 as the host OS and I have a single VM running Windows Server 2019 Essentials.

The drive configuration is as follows:

60GB SSD - OS drive for Hyper-V Server 2019

256GB SSD - VMs drive for Hyper-V VM (currently it's only housing the aforementioned VM with Windows Server 2019 Essentials)

4TB HDD - One of four HDDs being used as pass-through disks for the WIndows Server 2019 Essentials VM

4TB HDD - "

6TB HDD - "

4TB HDD - "

As stated above, I was using the four hard drives as pass-through disks for the Server 2019 Essentials VM.  I was going to create a storage spaces drive pool from them on which my father would serve files to his other computers and then slowly add or remove drives as he saw fit.

Now for the problem: Everything was running well.  I had finished setting up everything and so I shut down the VM and then the host in preparation to move it to where it would operate most of the time.  Nothing unusual happened during any of this.

When I went to turn on the host this morning, it powered on just fine, but my Server 2019 Essentials VM failed to start.  I have no indication as to why it won't start other than the fact that neither the host, nor Hyper-V Manager, nor Windows Admin Center will recognize the four hard drives.  It's like they vanished.  The BIOS of the box sees them just fine and I have verified that they're still connected.  But nothing within Hyper-V Server 2019 itself nor any console connected to it can see it.  DiskPart only sees the two SSDs and I've even tried changing the SAN policy to Online with no avail.

Any advice in getting my drives back up and running (and hopefully the Windows Server 2019 Essentials VM with it) would be seriously appreciated.  Thanks in advance!

Good day,

I have network bridge made with 2 ethernet adapters on my Windows 2012r2 server.

Am I able to do virtual switch based on network bridge? Right now I can choose only single network adapter while switch creating :<

Hello!

So I currently have a virtual windows 2012 R2 server and the VHD that holds configuration as well the boot files is about to run out of space, is there anyway to make a new partition and copy the current setup of the server to a new VHD to avoid running out space and then setting that new VHD to take the place of the old one?

Thanks!

Steve

Hi community, 

after your authorization,

i m very happy to present you my contribution, 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 welcom,

this is the link :

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

if someone have the suggestions or an improvement he can tell me .

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 team,

I've been experienced an issue that is affected the performance of my environment. I have the following scenario:

1 - Server Dell R720

1 - SAN DELL MD3220i

1 - Switch Cisco 3750G

As the picture shows, I just have a switch, I'm pretty know that the recommended setting is with two switches, however I just have one of them. A personal of Cisco has configured this device with different vlan's so that means that the connection between the storage and the host works so nice.

The problem is the latency that the virtual machines are experiencing. I have Windows Server 2012 and I'm using Hyper-v to virtualize my virtual machines.

Does anyone know which parameters May I need to modify, enable or disable on Windows Server 2012 - Hyper V to work fine?

I would appreciate your help in this regard!

Thank you in advance!

Regards,

Paul Mendoza.

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

Hi Team 

I have created a new cluster of 6 hosts DL380 G10 with Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz processors in them, they are on same ROM update as well. 

if I try to Live migrate via SCVMM following message occurs in Select host tab. 

"The Virtual Machine (VM Name) is not compatible with the virtualization host (Host name). the virtual Machine may not start or operate correctly on the Host. This may be due to inconsistent processor combability information. "

When I Try with the Failover Cluster Manager it gives me following error 

Live migration of 'SCVMM DCUTL01' failed.Virtual machine migration operation for 'VMNAME' failed at migration destination 'HOSTNAME'. (Virtual machine ID xxxxxxxxxxxxxxxxxxx)The processor settings for virtual machine 'VMNAME' are not compatible with physical computer 'HOSTNAME'. To migrate this virtual machine, you must first shut it down. After shutdown, you can migrate this virtual machine or export it and then import it on the destination physical computer with the correct processor settings. (Virtual machine ID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

I have not tried it with allow from compatibility mode on as that will not be a resolution. all my processors are the same.

Thanks

Saqib Ahmed

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

Helou guys,

pls for help with managing a non-domain Hyper-V server from domain joined PC.

Client= Windows 10 1903 (Domain Joined) IP= 192.168.20.52

Hyper-V host= Hyper-V Core Server 2019 (Workgroup) IP= 192.168.20.177

Here is a config from Server (Workgroup)

Here is a config from Client (Domain Joined)

  When I'm trying to connect to Hyper-V, I'm getting an error

Thanks for advice guys!

Symptom

You use Hyper-V on a computer that is running Windows Server 2008 or Windows Server 2008 R2.

• In Hyper-V Manager, you try to try to export a virtual machine to a network share.
• You have the full control permissions on the network share.

In this scenario the export may fail with an error that resembles the following:

An error occurred while attempting to export the virtual machine.

Failed to copy file during export.

Failed to copy file from ‘<source path of VHD file>’ to ‘<network share>’: General access denied error (0x80070005)

Cause

When you export a virtual machine in Hyper-V manager, it is the System account of the Hyper-V host that executes the export. This problem occurs because the Hyper-V host does not have permission on the network share

Resolution

Ensure the permissions allow the Computer account of the Hyper-V host performing the Export to update the shared folder.

Note: While following steps are specific to 2008, the idea is the same for updating the share and NTFS permissions if the share is hosted on other versions of Windows. You can adjust the steps accordingly.

Updating the NTFS level permissions:

1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Security tab. 
3.  Click Edit button and click the Add button in the permissions dialog box. 
4.  Click Oject Types and select Computers if not already done and click OK.
5.  In the dialog "Enter the object names to select" provide the name of Hyper-V host machine and click Check Names.
6.  With the Hyper-V host machine name select, click Allow by "Full control" and click OK.

Updating the share level permissions:

1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Sharing tab. 
3.  Click Advanced Sharing...
4.  On the Advanced Sharing dialog, click Permissions  and then Add.

5. Click Oject Types and select Computers if not already done and click OK.
6.  In the dialog "Enter the object names to select" provide the name of Hyper-V host machine and click Check Names.
7.  With the Hyper-V host machine name select, click Allow by "Full control" and click OK.

Applies to

Cannot connect to the RPC service on computer 'Servername'.  Make sure your RPC service is running.

We were originally getting this error from Hyper-V Manager sporadically, but now we aren't able to manage our Hyper-V servers with Hyper-V Manager at all.

I can still RDP to the hypervisors, and can ping them, but we cannot connect using any remote management tools (server manager, computer management, etc.).  I've disabled all firewalls on every PC involved.  I have tried enabling remote management through sconfig, and have done countless reboots.  I've read through John Howard's 5 part guide about setting up permissions to Hyper-V, and have followed some of the applicable steps, to no avail.

I've also confirmed that the RPC service is running on all PCs and servers involved.

It should also be noted that I am able to connect to the virtual machines via RDP.

The hypervisors are running Server 2008 R2 Enterprise with a core install, and the client computers we are attempting to connect with are running Windows 7.  All machines are set up in a single domain.

Any thoughts?

*Just a quick edit - I also did a chkdsk /r on one of the hypervisors to try and resolve this.  I thought corruption could be the culprit, although it seems I was mistaken.

I have a problem. Changes were done to the content of a vhdx by the guest os and important files are damaged. Can I undo the latest changes using the .rct file?

In other words: Does A .rct file only consist of "Off new_data" or does it contain "Offset new_data old_data" ?

Hi all 

I am working on a project with special requirement and need suggestions on how to achieve it.

Following is current configuration 

Hyper-V Infrastructure A 

1. Domain:aa.co
2. No of Hyper-V hosts: 3 
3. Failover Cluster Configured for VMs: Yes
4. No of VMs: 20
5. Networks:Management NW(192.168.2.0), iSCSI NW(192.168.1.0), Cluster Live Migration NW ( 172.18.1.0), Cluster NW (172.18.2.0)
6. SCVMM Installed: Yes, running as Virtual Machine
7. Domain Controllers : 1 Physical , 2 Virtual Machine 
8. DC OS Version : Windows Server 2012 R2 
9. Hyper-V Host OS Version : Windows Server 2012 R2 (GUI)
10. Storage Type : iSCSI ( Dell EMC)

Hyper-V Infrastructure B

1. Domain:bb.co
2. No of Hyper-V hosts: 3
3. Failover Cluster Configured for VMs : Yes
4. No of VMs: 10
5. Networks: Management NW(192.168.3.0),iSCSI NW(192.168.1.0), Cluster Live Migration NW (172.16.1.0), Cluster NW (172.16.2.0)
6. SCVMM Installed: Yes, running as Virtual Machine
7. Domain Controllers: 1 Physical, 2 Virtual Machines
8. DC OS Version : Windows Server 2016 
9. Hyper-V Host OS Version : Windows Server 2016 Data Center (Core)
10. Storage Type : iSCSI ( Pure Storage)

Additional Information 

• Hyper-V hosts in both infrastructure has access to Storage Network 
• Hyper-V hosts in aa.co domain can reach Hyper-V hosts in bb.co
• Hosts in both domains have similar number of NICs ( NIC teaming is also configured). Hosts in bb.co have more capacity in terms of CPU, RAM and Storage
• All hosts are in one rack, connected to same switch stack, external traffic is routed by one firewall.

Requirement 

• Move all VMs from aa.co domain / cluster to bb.co domain / cluster in new Hyper-V infrastructure. The reason is that aa.co infrastructure is old and had couple of hardware parts failure. 
• They don't want two domains to talk to each other but consolidate everything in one Hyper-V infrastructure for simplicity and management purpose. one domain (aa.co) will be for internal purpose and (bb.co) for external purpose.

Questions

• What do I need to do in bb.co Hyper-V Cluster in terms of physical and virtual network in order to facilitate aa.co Hyper-V VMs to continue communication in same subnet after move. The goal is not to change anything on subnet level since this is production network and have live internal clients connected to DC and other applications.
• What method of Hyper-V migration I should use in this scenario ?
• Do I need to configure anything on VMM in both cluster ? Is there any other consideration I should undertake since all VMs are managed by VMM in both infrastructure ?

I have worked with Hyper-V in limited scale such as same domain, replication, export and import of VMS etc. This is new large scale migration for me and would like to explorer my options and maintain best practice as well. 

Your suggestions and ideas are appreciated. 

I have installed Windows 10 Evaluation and necessary softwares. Now I would like to use this copy for future purpose once 90 evaluation done. 

Basically I want to make copy of it. 

ItsMeSri SP 2013 Foundation

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