Moved to the correct forum
↧
Internet becomes slow when External Vswitch is created with Intel Wifi card
↧
Hyper-V 2019 Slow Network Performance compared to 2012 R2
We run a combination of 2012 R2 and 2019 servers in separate clusters. We are experiencing a frustrating issue with our 2019 Hyper-V Servers. VM to VM network speeds are inferior on the 2019 hosts compared to identical VMs on the 2012 R2 Servers (around 1/3 of the speed)
We approached Microsoft and they suggested that they could see a number of network errors on the external NICs, so I approached the vendor (Dell). They suggested a couple of firmware updates to the NICs and the FC cards, which we performed. They also suggested a downgrade of the Intel NIC drivers – I had already tried the ones from the Intel site to see if this improved matters.
When this didn’t fix the issue Dell then wanted to go down the route of replacing hardware, which I resisted since we were having the same performance issues on all 6 hosts & it simply isn’t possible that all the hosts have the same hardware fault.
I then decided to create a Private VSwitch on one of the 2019 hosts. I connected my test VMs to this switch and experienced the same poor network speeds, which leads me to believe that the issue is unrelated to the NIC hardware or drivers, but the issue lies more fundamentally with how 2019 handles VSwitch traffic compared to 2012 R2
I have tried a number of "Fixes" suggested online, such as disabling VMQ and RSC, but these made no difference.
Has anyone else experienced this issue?
↧
↧
how to fixed An error Occurred while trying to retrieve a list of virtual switches?
How to Fix An error Occurred while trying to retrieve a list of virtual switches ? (Hyper V error Message Box)
↧
Hyper-V Manager over a VPN not able to connect
I have setup a Hyper-V server in a workgroup setup.
I have used the following steps to achieve this, which is all working on my local LAN.
My router supports multiple LANs, and I am able to use the Hyper-V manager between them as well.
What I have not been able to get to working is when trying to access the server with the Hyper-V Manger over my VPN.
Steps I used to allow Management access for WorkGroup:
On the Hyper-V Server:
Ran PowerSHell as Administrator
Ran: SConfig.cmd
Selected options 4 Configure Remote Management, then 1 Enable Remote Management
Selected option 3 Add Local Administrator, added Windows Username being used on the Remote Computer
On the Remote Client PC:
Ran PowerShell as Administrator
Ran the following commands to add Hyper-V server as turster host, and add administrator password
Set-Item WSMan:\localhost\Client\TrustedHosts -Value 192.168.1.100 -Concatenate
cmdkey /add:192.168.1.100 /user:administrator /pass:
Ran this to check host were added:
Get-Item WSMan:\localhost\Client\TrustedHosts
Ran: dcomcnfg
Open component services --> computers
Right-click -> my computer -> properties
Select "COM SECURITY" tab
Under "ACCESS PERMISSIONS" select "edit limits"
Select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
So on my local LAN, I can use the Hyper-V to access the server 192.168.1.100 from other LAN on 192.168.5.10.
But when I try this from a remote PC via a VPN, which is on IP 10.0.0.10, it does not seem to be able to even see the Hyper-V service running.
I can ping and RDP to the server hosting the Hyper-V system, but the Hyper-V manager is not able to connect.
I tried turning off all the firewalls, but still could not get any joy.
All my desktop logins are using the same Username and Passwords.
Thought to try and see if someone could suggest anything that may assist me with this.
Thanks in advance for any comments.
I have used the following steps to achieve this, which is all working on my local LAN.
My router supports multiple LANs, and I am able to use the Hyper-V manager between them as well.
What I have not been able to get to working is when trying to access the server with the Hyper-V Manger over my VPN.
Steps I used to allow Management access for WorkGroup:
On the Hyper-V Server:
Ran PowerSHell as Administrator
Ran: SConfig.cmd
Selected options 4 Configure Remote Management, then 1 Enable Remote Management
Selected option 3 Add Local Administrator, added Windows Username being used on the Remote Computer
On the Remote Client PC:
Ran PowerShell as Administrator
Ran the following commands to add Hyper-V server as turster host, and add administrator password
Set-Item WSMan:\localhost\Client\TrustedHosts -Value 192.168.1.100 -Concatenate
cmdkey /add:192.168.1.100 /user:administrator /pass:
Ran this to check host were added:
Get-Item WSMan:\localhost\Client\TrustedHosts
Ran: dcomcnfg
Open component services --> computers
Right-click -> my computer -> properties
Select "COM SECURITY" tab
Under "ACCESS PERMISSIONS" select "edit limits"
Select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
So on my local LAN, I can use the Hyper-V to access the server 192.168.1.100 from other LAN on 192.168.5.10.
But when I try this from a remote PC via a VPN, which is on IP 10.0.0.10, it does not seem to be able to even see the Hyper-V service running.
I can ping and RDP to the server hosting the Hyper-V system, but the Hyper-V manager is not able to connect.
I tried turning off all the firewalls, but still could not get any joy.
All my desktop logins are using the same Username and Passwords.
Thought to try and see if someone could suggest anything that may assist me with this.
Thanks in advance for any comments.
↧
Unable to Live migrate server
Hi
I'm having a issue live migrating a server to another hyper-v cluster.
It is this specific server as other servers can be moved without any issues.
the error message i get in VMM is:
'VirtualMachine'
Failed to transfer log files information: The data is invalid. (0x8007000D)
Log files information transfer failed for virtual machine 'SADA1': The data is invalid. (0x8007000D).
Unknown error (0x8011)
on the destination server i get event id 20940 in Hyper-v-vmms event log:
'VirtualMachine' Failed to transfer log files information: The data is invalid. (0x8007000D).
I have not seen this error before and have been unable to find any info regarding the event ID.
Anyone have any insight?
↧
↧
Error Setting VMQ MaxProcessors on LBFO Switch Independent Team
We are attempting to set the VMQ for both NICs on a dual-port Intel X520. They are currently in a LBFO team with Switch Independent and Dynamic set.
However when using Set-NetAdapterVMQ with the 'MaxProcessors' property, it gives an error:
Set-NetAdapterVMQ : No matching keyword value found. The following are valid keyword values: 1, 2, 4, 8, 16
At line:1 char:1
+ Set-NetAdapterVMQ -Name "NIC1" -BaseProcessorNumber 2 -MaxProcessors ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (MSFT_NetAdapter...426E65C8AE98}"):ROOT/StandardCi...rVmqSettingData) [Set-NetAdapterVmq], CimException
+ FullyQualifiedErrorId : Windows System Error 87,Set-NetAdapterVmq
I find several sites using that command with many values without issue. I did find a single post here that states that this error would only appear for those using Switch Dependent on their team.
https://blog.apps.id.au/hyper-v-and-vmqs-mythbusting/
So why are we getting this error for a Switch Independent team? Is it because these NIC ports are on the same single card?
↧
Win10 2004 Hyper-V now creates vEthernet interface for every physical NIC?
I updated to Win10 2004 (Build 19041.208 as of this writing) and I've noticed that on my system with Hyper-V installed, I now have an auto-created vEthernet interface for every physical Ethernet interface on my system, including interfaces with no connectivity. Each one is named "vEthernet (Physical interface name)". This is occurring despite that fact that only virtual switch I have on my host system is the Default Switch.
All of these vEthernet interfaces have auto-assigned 172.x.x.x IP addresses. These vEthernet interfaces cannot be deleted in Network Connections (option is grayed out) and if I use Device Manager to uninstall the actual Hyper-V Virtual Ethernet adapter device associated with these interfaces, they reappear on reboot.
Strangely, when I installed Win10 2004 in a guest VM with 3 virtual NICs and installed Hyper-V within that VM (after enabling nested virtualization), I was NOT able to reproduce this behavior. The guest VM's Hyper-V environment did not create 3 new vEthernet interfaces, even after multiple reboots.
Is anybody else seeing this? Does anybody have any idea why this is occurring or what the purpose of these vEthernet interfaces are? Previously I only ever had one vEthernet interface for the Default Switch, and then I would get one more for each Internal or External virtual switch I created. I have no idea why Hyper-V feels the need to give me one per physical interface at this point, each with a 172 IP address.
↧
Hyper-V API for getting the VM, Counter and VmProcessor pro grammatically using c++
I have an old program where I have been using Power Shell commands like Gt-VM, Get-Counter, Get-VMProcessor. These PS commands are archaic and very slow and I want to move to Hyper-V API's. Could someone kindly point me to an sample program(s) which would give me an idea as to how to get the same job done using Hyper-V API's
thanks a lot in advance.
↧
Win10Pro Hyper-V VM - extremely slow desktop performance with 4k Display
My work laptop is a Lenovo Thinkpad X1 Carbon w/16GB of Ram, 4c/4T intel 8th gen CPU, integrated GFX & SSD.
The laptop performs reasonably well and I use it for running a single VM connected to a Thunderbolt Lenovo Docking Station (that supports 4k) and a 4k DP monitor.
I connect to the VM by using VMConnect and I noticed significant lack of desktop performance (during normal usage)only when the VM screen is Maximised.
- Why is that? Can anything be done to improve its Full Screen 4k Desktop performance?
NOTES.
- VM Resources maximised as follows:
CPU = 8 Virtual Processors (Physical CPU has 4 cores + HT).
RAM = 10752 MB - No Dynamic Memory (DynMem Disabled).
Pagefile.sys = fixed size, 4GB.
- Host Win10 Pro OS set to prioritise Background processes.
- When the VM runs on a 1920x1080 window, it is usable.
- When the VM is Full Screen, it becomes unusable (the issue occurs both On VMConnect & RDP Client).
↧
↧
Server 2016 SET team SRIOV for host ManagamentOS vNIC not available
HI I am running server 2016 with a SRIOV enabled SET team and I am trying to enable SRIOV for the host managementOS vNICs, is this possible in server 2016? I see SRIOV for all other VM vNICs but not the managementOS vNIC even when I | fl* on the
vNIC the IOV options are not there, is this expected behavior, is IOV not available to host vNICs?
↧
Plex GPU Transcoding on Hyper-V Failover Cluster
Does anyone know a way to pass a graphics card to a VM in a Hyper-V 2019 cluster? Discrete Device Assignment does not work in a cluster according to Microsoft.
↧
Need to access a USB thumb drive in Hyper V
What is the easiest way to connect a USB thumb drive in Hyper V version 10.0.18362.1? I need to move some info from into (Windows 7) running in my Hyper V. I have used another virtual machine and the USB would show up, you had to tell it to connect. I
cant even find it in Hyper V.
↧
A virtual disk support provider for the specified file was not found. (0xC03A0014).
Hello All,
I was getting below errors after rebooting Hyper V 2012 server, Now everything is fine but looking for RCA & precaution for future issues & I got few article but these are for windows 2008 server .
https://support.microsoft.com/en-ie/help/2628135/a-system-center-virtual-machine-manager-2008-p2v-fails-with-a-device-a
https://support.microsoft.com/en-in/help/2013544/error-message-when-you-manage-a-vhd-file-in-windows-server-2008-a-virt
Note : ---The affected hyper-v host is Windows 2012 and no backup running.
As far as AV scans, I have not seen / experienced that Symantec locking the vm configuration and vm disks folders.
Symantec have KB to exclude the hyper-v settings ‘vm configuration and vm disk folders’ with OS Windows 2008 R2 for vm live migration
2 Hyper V on Standalone
==========================================================
Below are the events.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:25:59 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:57:52 AM
Event ID: 12620
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL': Cannot get information for attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
=======================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:01:30 AM
Event ID: 32086
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V suspended replication for virtual machine 'NMii' due to a non-recoverable failure. (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211). Resume replication after correcting the failure.
==========================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:01:36 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
=========================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:02:49 AM
Event ID: 15266
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to create the virtual hard disk.
Event Xml:
================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 14140
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL' failed to add device 'Virtual Hard Disk'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
=======================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:26:18 AM
Event ID: 12010
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\C9225EDB-AFE2-47BA-BEF4-DDD78A803003
Computer: LANDserver.contoso.waycorp.com
Description:
'LANDC01' Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID C9225EDB-AFE2-47BA-BEF4-DDD78A803003)
Event Xml:
===============================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:26:18 AM
Event ID: 12140
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\C9225EDB-AFE2-47BA-BEF4-DDD78A803003
Computer: LANDserver.contoso.waycorp.com
Description:
'LANDC01': Failed to open attachment 'E:\VM Machine\LANDC01\Virtual Hard Disks\LANDC01 C-Drive.vhdx'. Error: 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID C9225EDB-AFE2-47BA-BEF4-DDD78A803003)
====================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Storage
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 27000
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to open attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. Error: 'A virtual disk support provider for the specified file was not found.'.
==================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 12620
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL': Cannot get information for attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
===========================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:13:18 AM
Event ID: 12140
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\51567C34-DE69-4B3D-8731-A2CDF4679E69
Computer: LANDserver.contoso.waycorp.com
Description:
'LANPRD01 - Paulson Software': Failed to open attachment 'H:\VM Machine\LANPRD01\Virtual Hard Disks\LANPRD01 C-Drive.vhdx'. Error: 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID 51567C34-DE69-4B3D-8731-A2CDF4679E69)
Event Xml:
======================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:59:16 AM
Event ID: 15268
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to get the disk information.
Event Xml:
=====
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:59:29 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
I was getting below errors after rebooting Hyper V 2012 server, Now everything is fine but looking for RCA & precaution for future issues & I got few article but these are for windows 2008 server .
https://support.microsoft.com/en-ie/help/2628135/a-system-center-virtual-machine-manager-2008-p2v-fails-with-a-device-a
https://support.microsoft.com/en-in/help/2013544/error-message-when-you-manage-a-vhd-file-in-windows-server-2008-a-virt
Note : ---The affected hyper-v host is Windows 2012 and no backup running.
As far as AV scans, I have not seen / experienced that Symantec locking the vm configuration and vm disks folders.
Symantec have KB to exclude the hyper-v settings ‘vm configuration and vm disk folders’ with OS Windows 2008 R2 for vm live migration
2 Hyper V on Standalone
==========================================================
Below are the events.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:25:59 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:57:52 AM
Event ID: 12620
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL': Cannot get information for attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
=======================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:01:30 AM
Event ID: 32086
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V suspended replication for virtual machine 'NMii' due to a non-recoverable failure. (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211). Resume replication after correcting the failure.
==========================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:01:36 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
=========================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:02:49 AM
Event ID: 15266
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to create the virtual hard disk.
Event Xml:
================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 14140
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL' failed to add device 'Virtual Hard Disk'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
=======================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:26:18 AM
Event ID: 12010
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\C9225EDB-AFE2-47BA-BEF4-DDD78A803003
Computer: LANDserver.contoso.waycorp.com
Description:
'LANDC01' Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID C9225EDB-AFE2-47BA-BEF4-DDD78A803003)
Event Xml:
===============================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:26:18 AM
Event ID: 12140
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\C9225EDB-AFE2-47BA-BEF4-DDD78A803003
Computer: LANDserver.contoso.waycorp.com
Description:
'LANDC01': Failed to open attachment 'E:\VM Machine\LANDC01\Virtual Hard Disks\LANDC01 C-Drive.vhdx'. Error: 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID C9225EDB-AFE2-47BA-BEF4-DDD78A803003)
====================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Storage
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 27000
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to open attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. Error: 'A virtual disk support provider for the specified file was not found.'.
==================================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 7:18:15 AM
Event ID: 12620
Task Category: None
Level: Error
Keywords:
User: Tech
Computer: LANDserver.contoso.waycorp.com
Description:
'W2008STD_64_TEMPL': Cannot get information for attachment 'E:\VM Machine\W2008STD_64_TEMPL\Virtual Hard Disks\W2K8STDR2-64.vhd'. (Virtual machine ID 3D6E5677-DA69-470F-9F8F-00B21EABA002)
===========================
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 6/1/2018 7:13:18 AM
Event ID: 12140
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\51567C34-DE69-4B3D-8731-A2CDF4679E69
Computer: LANDserver.contoso.waycorp.com
Description:
'LANPRD01 - Paulson Software': Failed to open attachment 'H:\VM Machine\LANPRD01\Virtual Hard Disks\LANPRD01 C-Drive.vhdx'. Error: 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID 51567C34-DE69-4B3D-8731-A2CDF4679E69)
Event Xml:
======================
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:59:16 AM
Event ID: 15268
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Failed to get the disk information.
Event Xml:
=====
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 6/1/2018 6:59:29 AM
Event ID: 32026
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: LANDserver.contoso.waycorp.com
Description:
Hyper-V failed to generate delta for virtual machine 'NMii': A virtual disk support provider for the specified file was not found. (0xC03A0014). (Virtual Machine ID 9DE486A1-1679-47BB-BCAF-B8E7853A4211)
↧
↧
provisioning RAM, not enough ?
Hi,
I have a hyper-V server with several virtual machines on it.
The Hyper-v server is a Xeon Silver 4110, with 144Gb RAM in it.
following machines are running (and the RAM) :
- DNSproxy - 4Gb
- ESS server - 16Gb
- FOTO server - 8Gb
- FPS server - 8Gb
- RDS server - 8Gb
- SQL server - 32Gb
- VDI server - 16Gb
In total my VM's are using 92Gb of the 144Gb available (minus the hyper-v ofcourse)
Now if i want to adjust the RAM on the VDi-server from 16Gb to 32Gb, which should be possible.
i get a warning that i do not have enough RAM available ?
I don't seem to figure it out, has anyone some clues or hints where i can start looking ?
Thanks in advanced
Some screenshots :
↧
Set input parameters for "GetSummaryInformation" method of "Msvm_VirtualSystemManagementService" - VC++
Hi,
I want guest OS name of all running VMs on my hyper-V server.
I am using VC++ to achieve my task.
Following steps completed successfully.
1.CoInitializeEx
2.CoInitializeSecurity
3.CoCreateInstance
4.ConnectServer
5.CoSetProxyBlanket
6.GetObject of class "Msvm_VirtualSystemManagementService"
7.GetMethod "GetSummaryInformation"
8.SpawnInstance
Now how to set input parameters for "GetSummaryInformation" & call "ExecMethod" for the same.
I don't get any idea from C# code sample.
Thanks,
D V
I want guest OS name of all running VMs on my hyper-V server.
I am using VC++ to achieve my task.
Following steps completed successfully.
1.CoInitializeEx
2.CoInitializeSecurity
3.CoCreateInstance
4.ConnectServer
5.CoSetProxyBlanket
6.GetObject of class "Msvm_VirtualSystemManagementService"
7.GetMethod "GetSummaryInformation"
8.SpawnInstance
Now how to set input parameters for "GetSummaryInformation" & call "ExecMethod" for the same.
I don't get any idea from C# code sample.
Thanks,
D V
↧
UUID Solution for Hyper-V
Hello Fellow Hyper-V Engineers,
I am trying to find a solution in my org at my company to find a method of tracking meta-data that could be used as a UUID for an automation system where VMs would be decommed and deleted via a customer facing portal. My problem here is that
Hyper-V does not have legit UUIDs for VMs as they can be changed when migrated across clusters, be empty (due to error ) or be copied from a clone.
I am trying to find an easy and practical solution like perhaps parsing the licensing meta-data of a VM when trying to identify the correct VM to delete .
Thank you for your time.
↧
Cannot convert physical disk to VHDX
I create a new virtual disk and choose to copy the contents of the physical disk and get an error.
Event ID 27266 Hypev-V-VMMS
The description for Event ID 27266 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:
\\?\mpio#disk&ven_dell&prod_md38xxf&rev_0820#1&7f6ac24&0&3630304130393830303036383431364130303030303243333536434343453331#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
%%2147942401
0x80070001
The locale specific resource for the desired message is not present
---------
Event ID 15278 Hypev-V-VMMS
Failed to convert the virtual disk.
↧
↧
CSVs fail when nodes rejoin the cluster
Going to jump right in because I'm just completely stuck with what's going on and Microsoft has been zero help under our SA contract.
I have an eight (8) node Server 2016 Hyper-V cluster. The nodes are split between two Dell chassis, if that matters, with a dedicated host management network/private network, iSCSI network and fiber channel connection to each blade using individual switches in the chassis. The CSVs consist of six (6) iSCSI all-flash backed LUNs and six (6) FC spinning-disk backed LUNs, with one iSCSI flash LUN for a quorum disk. Most of the VMs are held on the iSCSI disks, for performance reasons, with data VHDs being held on the FC LUNs.
When a machine is properly paused/drained to be rebooted, for any reason (patching, maintenance, etc.), when it rejoins the cluster after being rebooted, all of the cluster disks in the GUI start to flash. The stats, such as the size of the disk, disappear and then reappear quickly. In the events, on the rebooted node, I can start to see "'STATUS_BAD_NETWORK_PATH(c00000be)'. All I/O will temporarily be queued until a path to the volume is reestablished." error messages. This event throws for seemingly random CSVs, as it could be all of them, or a subset of disks, but it never seems to be consistent. Mind you, the node is still paused, it has all of its networking capabilities and is properly communicating with the other cluster nodes.
At this point, the other nodes begin to throw errors on the same disks the rebooted node was complaining about, especially the nodes that are the owner of those disks. Then, the majority of times, the CSV will fail and run through recovery options to come back up on another node, causing several VMs to crash in the process.
One last odity in this is that even though the rebooted node complains about a BAD_NETWORK_PATH for some of the FC disks, none of the FC data disks have ever failed, only the iSCSI all-flash LUNs. This is more detrimental to me though, because the majority of OS disks are held on these LUNS.
Any help is greatly appreciated, thanks!
↧
Hyper V Powershell - memorymaximumbytes does not accept input from read-host
Hi
I am trying to create a script which will copy a vhdx file and create a new vm using the hyperv cmdlets however I keep getting the following error message on the memorymaximumbytes
cannot bind parameter memorymaximumbytes. cannot convert value "4GB" to type "System.Int64". Error: "Input was not in correct format"
I have the 4GB value bound to a variable of $maxmem which is prompted for using the read-host cmdlet.
Any ideas on how I can get this working?
Thanks
↧
Backing up a Hyper-V virtual machine fails due to Volume Shadow Copy Service
The full error is:
Backup failed to complete. A Volume Shadow Copy Service operation failed. Please check "VSS" and "SSP" application event logs for more information. Detailed error: The operation ended before completion.
Upon checking the event log, it says:
The backup operation that started at '2020-05-08T21:33:38.477000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x807800A1'.
What am I trying to do?
I'm running Windows Server 2016 as a Hyper-V host. I have some virtual machines that I would like to back up using the Windows Server Backup feature as shown here:
I am backing these VMs to a remote shared folder and eventually get these backed up on a schedule on a daily basis (but that's outside this post). The issue is that every time I try to backup these VMs, the above error message appears. For whatever reason, these backups work just fine in our test environment but do not work in our production environment.
I did some reading and found that the Volume Shadow Copy service has to be running in order for this to work. I looked in Services and found that it wasn't running. I started it and enabled Automatic startup. This did not work. I found that there are dependencies on this service (such as Microsoft Software Shadow Copy Provider service) that have be running too. These also did not correct the issue after I started them.
Our Windows firewall is turned off and antivirus is disabled too.
Does anyone have any suggestion or solution to this issue?
Thanks.
↧