XenServer - Unplug a NIC
-
So this is just something I'm working on, and it's more of an annoyance than anything. Is there a way to specify which NIC's are "connected" within a VM.
This way I don't have to remove a NIC, and re-add it as I make changes to it?
-
Great question - I'm working on VMWare right now doing exactly this.
-
@DustinB3403 said:
So this is just something I'm working on, and it's more of an annoyance than anything. Is there a way to specify which NIC's are "connected" within a VM.
This way I don't have to remove a NIC, and re-add it as I make changes to it?
What do you mean exactly?
I ask because you can see at the XS level which NICs have an actual connection.
In my VMs, I've been deleting all the NICs I do not use on a VM by VM basis.
But I am assuming this is not what you mean.
-
Lets use for example a Windows System with multiple NICs.
I want only 1 nic to be active and the other to show the disconnected symbol. While not having to actually remove the NIC from the system. Otherwise all NICs are active unless I boot into the OS and disable it.
I'm looking for a way to toggle the active NICs outside of the VM, without having to remove the NIC from the VM.
-
Found it. While look at the VM, Scroll down to the Interface section. hover over it, and the disconnect button appears - not sure why this needs to auto hide though?
-
@Dashrender Hrm, testing.
-
I was going to say there were a bunch of articles on Google about this, but they all seemed to come up with workarounds that didn't quite do what their OP was looking for.,
So make sure that does what you are looking for.
-
@BRRABill Yeah I'm going to test it now.
If this VM attempts to PXE boot it doesn't do what I want it to.
-
Now what I'm equally interested in learning.. how do I create virtual switches, and how do I assign NICs to a specific one?
and while I'm interested.. I won't be working on it.. because I have two other things I'm working on today.
-
So this works on XO versions (xo-web 4.15.1 - xo-server 4.15.1), but not on the version I'm on at the moment.
Guess it's time to upgrade.
-
I'm on 4.14.1 and its well.
-
I'm on 4.13, which might be where the issue lies.
In the Vm it actually "removes" the device, (not sure about in the device manager) but it's still accessible to the VM to be enabled later.
So that works for me.
