...
If the command completes successfully reboot the vm normally. Be aware that future kernel updates may require this maneuver be done again.
Enabling Interfaces on Virtualbox
On Virtualbox, it is needed to configure the interface manually. It is required to create the config file: /etc/sysconfig/network-scripts/ifcfg-enp0s3
The content of this config file is as follows:
| Code Block | ||
|---|---|---|
| ||
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s3
UUID=91c122a2-39d6-4928-860b-59f4d87faea1
DEVICE=enp0s3
ONBOOT=yes
NM_CONTROLLED=yes |
Once the config file has been created, a VM reboot is needed.
Other Hypervisors
To use OVF/OVA files with other virtualisation systems like KVM you may have to convert the OVF file to a native format; Two well-known tools for this purpose are virt-v2v (available in CentOS6/RHEL) and virt-convert (in Debian).
MVware Fusion 11
Even though, there are no caveats in relation to importing the Virtual Appliance using VMware Fusion, it is important to remind users to grant permission to VMware Fusion to fully execute on OSX, specially after installing it.
The following message is displayed while running the VM without the permission granted.
The permission should be granted on System Preferences > Security & Privacy
Hyper-V
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.
...