• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2892
  • Last Modified:

Cannot add second vNIC to Hyper-V virtualized guest

Using VMM and clustered 2012R2 Hyper-V hosts.

The virtualized guest machine is also the VMM server in our environment.

1. I try to add a vNIC via VMM to the guest machine, but that is not possible when it is turned on.
2. I turn it off, and try to add a vNIC to the guest machine via the Hyper-V manager on the host where the VM is running. This is not possible due to the error below:
Error"Some settings cannot be modified because the virtual machine is clustered. To modify a setting that is unavailable, use the Faileover Cluster Manager."
3. I install the Failover Cluster Manager on the host and connect to the cluster it is a part of, but I can't see any option there to configure the VM guests vNIC and virtual hardware(as I expected).

So I am stuck. How is this done?
0
itnifl
Asked:
itnifl
  • 3
  • 2
1 Solution
 
Shabarinath RamadasanInfrastructure ArchitectCommented:
As far as I know, HotAdd of Virtual network interface is not yet supported on Hyper-V. You can only change the interface configuration while the VM is On.

Have a look on what all are supported as HotAdd in Hyper-V.

http://blogs.technet.com/b/kevinremde/archive/2013/03/05/you-want-to-hot-add-what-20-days-of-server-virtualization-part-2-of-20.aspx

Cheers!
Shaba
0
 
itniflAuthor Commented:
So there is no way for me to add the second vNIC? I really need one. I have already tried to turn off the VM, but then I don't have a VMM server to connect to because it is the VMM server. Using the Hyper-V manager on the host doesn't work.
0
 
Shabarinath RamadasanInfrastructure ArchitectCommented:
You could add if the VM is OFF.
Go to failover manager -> Right click on the VM -> Settings -> Add Hardware -> Network Adapter

Let me know if you have any challenge on this.

Cheers.
0
 
Shabarinath RamadasanInfrastructure ArchitectCommented:
Once the VM is added to Failover Cluster, majority of the changes related with the configuration will be available only through Failover Cluster Manager. If its a standalone node, Hyper-V Manager could handle all such changes.
0
 
itniflAuthor Commented:
Yes, you are right about that. I looked too quickly when looking through the 'Failover Cluster Manager.' I found the VM via <ClusterName>->Nodes->SCVMM <VMName>. I added the vNIC there after turning the VM off. Then booted it, connected to it as the VMM server with the VMM console, and configured the vNIC to my liking.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now