Archives

Microsoft

Hyper-V VM export

Hello,

We have one Hyper-V VM with 100 GB C drive and 8 TB of D Drive. We are planning to migrate this VM to Azure with Azure ASR. Since, Azure ASR does not support this VM due to data disk size, we want to export the VM locally with only boot drive and then upload
the VHD to Azure.

Is it possible to export the Hyper-V VM with only C drive and exclude D drive ?


suhag

Read full post . . . .

Hyper-V S2D Cluster and Network Interface usage

Hi,

I have 2 nodes Hyper-V in S2D cluster with 2 interfaces in teaming for the OS and 2 FC interfaces for storage replication and VM networks. I would like to be sure that both FC interfaces are used for storage and VM networks and I would like to know the amount
of traffic on each interface dedicated on each services (Storage, Replication, VM Networks …)

Is it possible to have a chart with perfmon or powershell ?

Thank you for your help

Read full post . . . .

Failover Clustering – Hyper-V – WS 2019 Issues Migrating VMs (Flickering States)

Hello,

We currently are seeing the following issues when migrating VMs from Windows Server 2016 clusters or Windows Server 2019 cluster to Windows Server 2019 newly built cluster. We are building out these clusters as usual and have been running/migrating from
cluster to cluster in 2016 without any issues (3000+ VMs). New 2019 clusters are being validated with 100% success on every single parameter. We are using Mellanox RMDA cards in a 4 node HCI or non-HCI clusters.

When VMs are moved from 2016 cluster to 2019 cluster or 2019 to 2019, some VMs start flickering between states in Failover Cluster Manager. They are going between Resuming/Pausing/Paused/Starting and the FOC crashes. However, on the Hyper-V on the owner
node, they are showing up fine as running. We have tried to migrate these VMs via VMM, or by un-clustering and bringing it in via Move on Hyper-V and once they are in FOC, the flickering starts.

In event viewer, I keep seeing the events for the following:

‘XXX-HCTXXX-01’: Virtual hard disk resiliency successfully recovered drive ‘XXX-XX-XXXX-02.contoso.comCSV03Hyper-VVirtual DisksXXX-HCTXXX-01.vhdx’. Current status: No Errors.

‘XXX-HCTXXX-01’: Virtual hard disk ‘XXX-XX-XXXX-02.contoso.comCSV03Hyper-VVirtual DisksXXX-HCTXXX-01.vhdx’ received a resiliency status notification. Current status: Disconnected. (Virtual machine ID DXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX)

‘XXX-HCTXXX-01’: Virtual hard disk ‘XXX-XX-XXXX-02.contoso.comCSV03Hyper-VVirtual DisksXXX-HCTXXX-01.vhdx’ has detected a recoverable error. Current status: Disconnected. (Virtual machine ID XXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX)

I checked the storage permissions for where it resides from NODE to SOFSC, no issues. Old cluster has access and new one does too. I have full control from NODE that is now hosting the flickering server and the old host node does too.

It does not matter if the storage is moved along or not, the problem still arises.

Is there something happening in Server 2019 that we are not aware off that results in such behavior? The fix has essentially been to drain all roles except the faulty one, stop the cluster services, reboot node and bring the VM back, it then stops acting
in such way.

Thanks for your help!

Read full post . . . .

HyperV manager Mobile guide

The hyperV virtual machine management server was unable to establish a
connection for the virtual machine migration because the correct protocol was not supported by the target host

Read full post . . . .

Server 2019 – SET – NDIS reset Network card

Dear all

Environment:

3 node HyperV Failover cluster

each node:

- 2x Intel Xeon Gold 6138
- 512 GB RAM
- 1x 2 Port Intel X722
- 3x 2 Port Intel X710
- latest NIC driver and firmware
- Windows Server 2019 17763.805

SET:

Hash algorithm: dynamic

1x SET with the 2 Ports of Intel X722 for Cluster and LiveMigration
1x SET with the first Port of all 3 Intel X710 Networkcards for iSCSI Traffic
1x SET with the second Port of all 3 Intel X710 Networkcards for Data Traffic

After some time (with traffic faster than without) i can see the following events:

———-
Failed to move RSS queue 2 from VMQ 1 of switch 95AD556E-D325-46BB-87EC-AFDEA4ACE8F7 (Friendly Name: SET iSCSI), ndisStatus = -1073741823 .
———-
The network interface "Intel(R) Ethernet Controller X710 for 10GbE SFP+ #6" has begun resetting.  There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware
has stopped responding to commands. This network interface has reset 1 time(s) since it was last initialized.
———-
NIC /DEVICE/{F4B0FE78-B659-4D0E-AB0A-83E52D3A5419} (Friendly Name: Intel(R) Ethernet Controller X710 for 10GbE SFP+ #4) is no longer operational.
———-
Intel(R) Ethernet Controller X710 for 10GbE SFP+ #6
 Network link is disconnected.
———-

Then the network card comes back for a minute and the last 3 messages from above are written every minute.

The only way to get back to normal evacuate the vm to other hosts and reboot it.

Any idea what could be wrong here?

Thanks

Read full post . . . .

Question on import/export of VM

I have a 2012 R2 VM on a 2016 host.

The 2012 R2 VM is a domain member and running SharePoint.

I need to reload the 2016 host.

If I do an export to an extra hard drive in the server and reload the host, I can import it again without issue?

Thanks

Read full post . . . .

Merging snapshots.

I have a question i couldn’t find answer. So I have a virtual machines with vhdx and 2 avhdx drives. VHDX max size 500GB.

All those 3 files were on 1TB storage. Both AVHDX increased to that level that no room left on 1Tb storage. So i cant merge them as well. I have attached 4Tb storage and moved VM storage via VM settings to new storage. So now i have tons of space to merge
differentials to its parents. But one thing gives me worries.

Main parent is something like (1)-362Gb its child is (2)-235Gb and its child (3) is 457Gb.

I have to start merging 3 back to 2 so its mean 457 to 235 and i afraid that is will make more then 500 what is the limit and a it will fail destroying data. Could someone with more experience to bring in some light?

By the way if its safe to merge can I do it while VM is online?

Read full post . . . .

Hyper v VM not able to start after vSAN

Hi,

Not able to start the Virtual machine after configured vSAN getting the below error, we have 2 physical host, and 1 storage. i’m trying to do configure SQL failover cluster in the VM, so shared storage planning to attach from storage.  created the lun
in the storage and created virtual san in the Hyper v manager and assigned the vSAN in fiber channel adapter in the VM. but when trying to start the VM i’m getting the below error. 

 

Regards,

Manikandan

Read full post . . . .

Hyper-V Cluster – iSCSI and MPIO / TEAM Interface

Hi,

We have two HP servers with 2*10G network ports. Can anyone provide the best practice to use both the 10G NIC with redundancy config ? Can we use NIC Teaming or MPIO ? can both the interface be configured with same VLAN IPs ?

Thanks,


suhag

Read full post . . . .

Hyper-V 2019 Checkpoint Operations fails after a day

We backup our  Hyper-V 2019/16 servers containing couple of virtual machines, with Unitrend backup system, which requires checkpoints to be able to back the VM’s.  When we tested to create checkpoint, it would give the error "An error occured
while attempting to checkpoint the selected virtual machines. The operation cannot be performend while the object is in use". When we check the logs we get the following Event ID: 19100, 18012, 18014.
Normally when we reboot the Hyper-V servers , we are able to create checkpoints for a day or so after which the same issue recurs.

We have used ICACLS to grant the "NT Virtual Machine" user of each VM full access, and ensured that the VHD files and checkpoints are in the same folder. We also ovserved that the .avhdx files which are created would remain and are not able to automatically
get merged to the parent .vhdx file.

This is happening al all our Hyper-V 2019 servers which are part of a domain.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3361