Header Only - DO NOT REMOVE - Extreme Networks

run vm xos on vmware workstation 11


Hi All, I tried to set up a new virtual switch xos (xos 21.x)on vmware workstation 11 so I managed to get it installed but the network interfaces seem not te be UP although the are connected. I know that xos vm is supported on EXSi but what about workstation ? Is there any limitation du to the network type (E1000) ? thank you for your help !

9 replies

Userlevel 1
I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

Thanks for sharing your experience. that being said, I have many xos vm running on my virtual box and actually 4 interfaces it is enough for me but, indeed, whenever I want to increase network interfaces I had to do it on CLI so it is quite bothering... this is why I want to use it on vmware workstation inorder to add interfaces easy and graphically. could you try it out, install on vmware workstation ? thank you
Userlevel 4
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

I'm running EXOS 15.7 VM with 8 x 'e1000e' interfaces added in VMware Fusion 8.0 which is equivalent to VMware Workstation for Mac. It is working fine.
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

Hi, I'm quite astonished because on workstation, I'm not able to specify the e1000 network interface type. Do you know how can we change network interface type on vmware workstation 11 ? thank you.
Userlevel 4
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

I manually edited the .vmx file to change NIC type in VMware Fusion. I think VMware Workstation would be the same.

ethernet0.virtualDev = "e1000e"
ethernet1.virtualDev = "e1000e"
ethernet2.virtualDev = "e1000e"
ethernet3.virtualDev = "e1000e"
ethernet4.virtualDev = "e1000e"
ethernet5.virtualDev = "e1000e"
ethernet6.virtualDev = "e1000e"
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

Thank you so much for the hint and indeed I've done the same modifications on vmx file actually I've had to add these lines into the file and now the ports come up... thank you again for your help.
Userlevel 2
Darren Saliva wrote:

I never tried to use it in vmware workstation but i have created EXOS VMs using Oracle's VirtualBox and the same thing would happen and i would have to run the script to add extra interfaces every time it happened. It happened so many times that i finally stopped using VirtualBox and installed my VMs in ESXi using vswitch to connect my VMs and I no longer have that issue. With ESXi you can also have up to 10 interfaces on a VM which helped me out for what i was doing in my lab.

I have tried to installed XOS VM on VMWARE workstation and the interface will never come up no matter what. I did try to edit .vmx file but still failed. Using virtualbox, on the other hand, can perfectly run the VM. I also tried to run the VM on KVM, for first time installation, it failed to mount the flashdrive. But i tried to install the VM using virtualbox and import the image to KVM, it works perfectly
Userlevel 6
Thanks a lot for that thread - this helps me using EXOS virtual on vm workstation.
Userlevel 7
fwiw, I have created a whole virtual lab setup on virtualbox, scripting both topologies (up to 8 interfaces per VM) and config. Works like a charm on the with the latest version of VB (5.1) and EXOS.

Reply