ENDIAN 4i-edge-virtual-x64 6.8.3


-------------------------
Installation Instructions
-------------------------

When unzipping the .zip file you will get a directory containing a few files.

    endian_4i-edge-virtual-x64_6.8.3/
    endian_4i-edge-virtual-x64_6.8.3/endian_4i-edge-virtual-x64_6.8.3_virtual_softwarex86-64.vmdk
    endian_4i-edge-virtual-x64_6.8.3/License.txt
    endian_4i-edge-virtual-x64_6.8.3/Readme-KVM.txt

The .vmdk file is the VMware hard disk that contains the installed 4i-edge-virtual-x64 appliance.
The Readme-KVM.txt file contains this text.
The License.txt file contains the ENDIAN End User License Agreement.


Converting the .vmdk file
=========================

An additional step is required to convert the .vmdk file in a .qcow2 file that is supported by KVM.

- Convert the .vmdk file to a .qcow2 file. This can be done by using
  the qemu-img tool like this:
  
  qemu-img convert -O qcow2 \
        endian_4i-edge-virtual-x64_6.8.3_virtual_softwarex86-64.vmdk \
        endian_4i-edge-virtual-x64_6.8.3_virtual_softwarex86-64.qcow2


Starting the virtual machine
============================

- An example command line for an appliance with two virtual
  network interfaces would look like the following:

    /usr/bin/kvm \
        -drive file=endian_4i-edge-virtual-x64_6.8.3_virtual_softwarex86-64.qcow2,if=virtio,index=0,boot=on \
        -M pc \
        -vga cirrus \
        -parallel none \
        -usb \
        -usbdevice tablet \
        -name "ENDIAN 4i-edge-virtual-x64" \
        -cpu qemu32 \
        -m 512 \
        -smp 1 \
        -vnc :1 \
        -boot c \
        -net nic,macaddr=00:00:16:96:01:00,model=virtio,vlan=0 \
        -net tap,script=no,downscript=no,vlan=0,ifname=kvm0 \
        -net nic,macaddr=00:00:16:96:01:01,model=virtio,vlan=0 \
        -net tap,script=no,downscript=no,vlan=0,ifname=kvm1 \
        -monitor unix:monitor,server,nowait


----------------------
Additional information
----------------------

- This virtual machine comes already pre-installed. When booting
  the machine will first be configured using the IP address 
  192.168.0.15/24 on the GREEN interface. During the boot process
  the system will also start a DHCP client on the GREEN interface.
  This means, that if there is a DHCP server running in your GREEN
  zone you will then be able to access the virtual appliance
  on the newly assigned IP address.
  If you do not have the possibility to find out which IP address
  has been assigned to the system you can use the console
  to login with the default password and then execute the
  command that will show you the IP address. This procedure looks
  like the following:

    > login
    enter root@hostname's password:
    > ip a show br0
    2: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
        link/ether 00:3d:42:ec:72:1a brd ff:ff:ff:ff:ff:ff
        inet 192.168.0.15/24 brd 192.168.0.255 scope global eth0
        inet6 fe80::21d:92ff:feec:521a/64 scope link 
           valid_lft forever preferred_lft forever

