Page History

...

The Windows Hyper-V technology does not fully support the OVF industry standard. Microsoft documents a complex and somewhat limited procedure on their page about converting OVF files to Hyper-V. There are third-party conversion tools available that simplify this deployment scenario, for example StarWind's free V2V Converter  which worked well in our tests.

Fire up the VM and set the IP Address, DNS (optional)

At this point the VM has DHCP enabled, and therefore it will receive a dynamic IP address suitable for your environment. The easiest way to access the VM at that point is from the virtualization software terminal. So go ahead and boot the VM, after the VM is finished booting you will be welcomed by a login prompt. First, log in using the default credentials.

...

• manual configuration
  The VM appliance is a normal CentOS 6 system, hence all the mechanisms for network configuration in CentOS are available.
  Most specifically you'll be interested in the  files /etc/hosts, /etc/sysconfig/network, /etc/sysconfig/iptables and /etc/sysconfig/network-scripts/ifcfg-eth0.
• use our example network configuration files
  

  Root's home directory contains 2 example network configurations, one for static IP's and one for DHCP.  Copy the one you require to /etc/sysconfig/network-scripts/ and edit it to suit:

  Code Block
  cp ifcfg-eth0.static /etc/sysconfig/network-scripts/ifcfg-eth0

  Now set the IP, netmask, gateway, and DNS if you like ( to add DNS you can add two lines, one for each server: DNS1=ip , DNS2=ip); finally, run service network restart to activate.

• use the menu-based tool system-network-config
  Simply type  in system-network-config and follow the prompts.
  Please note: in Opmantek VM appliances before 8.5.12G the  tool is not preinstalled and you have to run yum install system-config-network-tui first.

Set Up Firewall (optional)

Please note that by default the Opmantek VM Appliance does NOT have a firewall enabled. If you would like local firewalling on your VM, you can easily enable that:

The standard iptables tools are installed, and all you would have to do, is enter your desired rules in /etc/sysconfig/iptables, followed by service iptables restart AND a final one-off run of chkconfig iptables on.  The service call enables your firewall rules, while the chkconfig call enables activation of the firewall rules on boot. Until and unless the chkconfig step is taken, your firewall rules won't persist when the VM is rebooted. Besides this, somewhat low-level, method of configuring an iptables firewall there are also various user-friendly frontends available for installation with yum.

Troubleshooting Network Problems

...