Updated on 8/15/2019
All Product Installation and Upgrade Guides
Eyeglass Hyper-V Installation Guide
Direct link to topic in this publication:

Hyper-V Configuration for Eyeglass And Deployment

  1.  (On server Microsoft 2012 add role for HyperV)

Go to server manager

Select add roles and features

  1.  (Create Virtual Machine)

Connect to the hyper V manager and now go to the option Action, New , Virtual machine

Select Generation 1.

For RAM enter 1G and network connections one Ethernet adapter is required .

Make sure to select a NIC connection

Select use an existing virtual hard disk and choose the file previously converted to vhdx.

and finish.

Now the vm is on the Menu of the Hyper-v manager and can be turn On.

Follow the installation steps for the OS like agree to the license agreement and setup the network, the network parameters can be modified later using the command (yast).

  1.   (Setup network)

Go to the Hyper V manager and click Virtual Switch Manager.

Click Create Virtual Switch

The connection type will be external for our configuration

Should select the option (Allow Management operating system to share this network adapter) when you click apply you will be disconnected from the server and a new network interface will appear on Network connections.

This new network interface has now  the previous configuration for the network and the other  interface will disable all properties and enable only Hyper-V extensible virtual Switch.

Now with the new virtual switch created the vm that was created in step 3 can be connected to this network.

Virtual Machine setting:

  1. Configure Eyeglass networking in a Hyper -V Environment

  1. Once the Eyeglass VM is started
  2. Login to console with admin
  3. SU to root user
  4. type yast
  5. goto networking devices
  6. Then follow quick start guide Eyeglass Isilon Edition Quick Start Guide
  7. NOTE: The OS will detect a different NIC card and it can be configured as per normal boot install sequence with ip, mask, gateway, dns etc.. that works within the Hyper-V host configuration
  8. After completion the https://x.x.x.x/eyeglass login will work as expected and all other functions are the same as the VMware OVF version including OS patching and updates.

For additional information about the network configuration on HyperV:

The Virtual Switch Manager

In order for a virtual machine created with Client Hyper-V to connect to a network and to the Internet, it must have access to a virtual switch. So the first order of business is to launch the Virtual Switch Manager and create and configure how you want the virtual network connection to work. To begin, launch the Hyper-V Manager using the tile on the Start Screen, navigate to the Actions pane, and select the Virtual Switch Manager action, as shown in Figure B.

Figure B

You'll launch the Virtual Switch Manager to create a virtual network connection.

When you see the Virtual Switch Manager screen, as shown in Figure C, you'll notice that the first thing that you must do is choose what type of virtual switch you want to create. As you can see here are three options: External, Internal, and Private.

Figure C

The Virtual Switch Manager offers you three types of virtual switches to choose from.

Of course, the one you choose will depend on how you want to use your virtual machine and in most cases you'll choose the External option. However, let's take a moment to examine each of these options so that you have a good understanding of what each one does.

  • When you select an External virtual switch, your virtual machine will be able to access all resources available on your physical network including host machine and the Internet.
  • When you select an Internal virtual switch, your virtual machine will only have a network connection with the host machine. In other words, the virtual machine will not be able to access resources on your physical network nor will it have access to the Internet.
  • The only time that you would want to select the Private virtual switch, is if have more than one virtual machine running at one time and you only want a connection between your virtual machines.

Each of these types of virtual switches is illustrated in Figure D.

Figure D

Each type of virtual switch has specific uses.

Before I move on, I just want to point out that you can indeed have more than one virtual switch. For instance, you could have both an External virtual switch and an Internal virtual switch. You could then experiment with virtual machines in different types of network configurations.

Configuring an External virtual switch

As I mentioned, in most cases you'll choose to create an External virtual switch in Windows 8's Client Hyper-V. When you do, the Virtual Switch Manager will present you with the set of options shown in Figure E.

Figure E

You'll use the Virtual Switch Manager to set up your External virtual switch.

Starting from the top, you can assign your virtual switch a name and provide a description in the Notes section. As you can see, I have provided both a name and notes for my example virtual switch.

Moving down to the Connection type section, you'll notice that while the connection type that you selected previously is selected here, in this case External, you could change your mind and select one of the other two types of network switches.

When the Connection type is set to External network, you'll see that your system's network card is shown in the drop down text box and that the Allow management operating system to share this network adapter check box is selected. To simplify what this check box selection means, think of it as saying Allow host machine and virtual machine to use the same network card. In order for both machines to use the same network card to access the physical network, the Virtual Switch Manager actually creates two virtual network cards, one for the host machine and one for the virtual machine, and then connects these to the virtual switch. The virtual switch is then connected to the physical network card which is already connected to the physical network. This configuration is illustrated in Figure F.

Figure F

The host machine is actually connected to a virtual network card.

In most cases, you'll leave the default selections for the External network just as they are. However, let's examine how these options work. Let's suppose that your system has two network cards in it: an Ethernet card called NC1 and Wireless card called NC2. If so, you could separate the network connections of your virtual machine and your host machine such that each would use a separate network card. To do so, you would select the network card that you wanted to use for the External network, say NC2, and then clear the Allow management operating system to share this network adapter check box. Then, the host machine would use NC1 to connect to the physical network and the virtual machine would use NC2 to connect to the physical network.

As you can see, by default the Enable virtual LAN identification for management operating system in the VLAN ID section is not selected. Chances are that you won't use this feature in a typical Client Hyper-V configuration. If you had a VLAN, or Virtual Local Area Network, you could use this option to specify an identification number that could be used to isolate network traffic from the host machine.

Completing the configuration

When you are done configuring your External virtual switch, click OK. When you do, you'll see a warning message indicating that during the virtual network connection procedure, the network connection for the host machine may temporarily go offline. When you click Yes, the changes will be applied and you'll see a progress bar. These steps are illustrated in Figure I.

Figure I

When you are done configuring your External virtual switch, click OK.

Checking the connection

Many of the folks that I have spoken to about setting up an External switch find it surprising that the host machine is actually connected to a virtual network card after you set up a virtual switch for your virtual machine. But its true and you can see for yourself by investigating the Network Connections tool or even on the command line with IPConfig.

Figures J and K show before and after screenshots of the Network Connections tool and the results from running the IPConfig command on the host machine.

Figure J

Running the Network Connections tool on the host machine.

Figure K

Running the IPConfig command on the host machine.

Copyright Superna LLC