Page tree
Skip to end of metadata
Go to start of metadata

Current beroNet Hypervisor State is Beta. Please see 0. Hypervisor State for more details.

Logging in

As soon as you have accessed the Hypervisor Web-interface you can login with the default credentials:

  • user: admin
  • password: beronet

Make sure to change the password later in the menu under "System->change password"

The Hypervisor GUI allows it to:

  • manage virtual machines
  • create and restore backups of machines
  • use the beroNet Appliance Market to download ready Apps and ISO Installation Media
  • discover a built in beroNet Gateway or beroNet Gateways in the local network

Virtual Machines

How to install an OS in a VM

To install an operating system as a VM you need to follow the steps:

  1. Download an ISO file which contains the operating system either from a web-rul or form the market; or upload an ISO file using the upload feature in the GUI
  2. Create a VM and define its metric and select your chosen ISO under "boot from ISO".
  3. Start the VM from the Dashboard
  4. Access the VNC console via the VNC link in the Dashboard
  5. Complete the installation using the prompts provide by your chosen OS. When completed, use the hypervisor dashboard to shutdown or poweroff the machine.
  6. On the Dashboard select "manage" next to your recently installed VM. Under "system" change the boot-device disk to "c (disk)"
  7. Restart the VM


The dashboard shows all VMs and all ISO files.

Each VM can be started by clicking the "start" link if they are in the state "STOPPED". If they are in the state "RUNNING" the VM can be accessed via VNC, halted via the "shutdown" link or powered off via the "Poweroff" link.

VNC - Console/Monitor for the VMs

By default each Virtual Machine starts a VNC Server on the Ports between 5900 - 5905. Any VNC tool can connect to this port, e.g. tightvnc for linux and windows: TightVNC

The Dashboard provides a built-In WebtRTC based WebVNC Client from Kanaka: noVNC Client. As the VNC Server of the VM is not a WebRTC Server, a WebRTC Proxy is used to connect the VM VNC Server and the noVNC Client. We're using again Kanakas Socket Proxy: websockify for that.

The Websockify Proxy opens a WebRTC Port on the Ports 6900 - 6905 corrresponding to the VNC Server ports. This needs to be understand and considered when creating NAT rules to the Hypervisors WebGui. It is easier to use an external VNC client like tightvnc in this case (the VNC port must still be natted).

The following picture shows how a browser can use the WebVNC on port 6900 and the Webserver on port 80 and how a VNC client can directly connect to the VMs VNC Server on port 5900:

Manage VMs

Under "Virtual Machines->Manage VMs" you create new VMs, delete or rename existing ones.

By clicking on New the VM Create wizard opens and allows to create a new vm.

After clicking on Create you can modify the VM Details in the VM Manager.

In the List of Virtual Machines you can always find a "manage" button which brings you to the VM Manager of this machine.

VM Details

The VM Manager divided in different sections:


Shows the current status of the VM and allows to do actions with it. The actions are:

  • Power On / OFF
  • Shutdown
  • Sleep / Wakeup
  • Clone

Additionally you can use the built-in WebVNC tool to connect to the console of the VM.


In the System Settings you can define:

* # CPUs               - The amount of CPUs for this virtual machine, one is reserved for the Hypervisor
* Memory in GB         - The amount of memory for this VM, 1GB is reseved for the Hypervisor
* Start on boot        - defines if the VM should be started automatically during boot
* Boot-Device          - defines if the VM boots from it's virtual hard-drive or from the ISO file for installation


Under the network settings you can define:

* NIC-Mode             - defines if the VM should access both the LAN and WAN port or only the LAN port of the appliance (NOTE: for LAN-WAN mode, LAN-WAN mode needs to be activaed under System->network)
* NIC-Model            - Realtek RTL8139 or Intel e1000 the emulated NIC Model for the VM

Also the MAC Addresses of the VM are visible here. The WAN Mac Address is only relevant in the lan-wan mode.


The Disks Manager allows to create, delete and reorder virtual disks. Also It defines if an ISO Intallation Medium is inserted in the VM. NOTE: a deleted disk can not be recovered!


Under other, you can mainly find the VNC and miscellaneous settings:

* VNC Display          - defines the VNC display number
* VNC Password         - defines the VNC access password
* VNC Keymap           - defines the VNC virtual Keyboard Keymap
* HV Options           - adds the possibility to add manually XEN option, for reference: xen options, multiple settings can be seperated by ; as 
* Windows-Tools        - if enabled the VM has another disk containing the PV driver for windows, which boost the performance of a windows VM (NOTE: preinstalled with the market windows images)


If the VM has clones or is a clone, it displays a list of its clones or a link of its parent.

Backup & Restore

The Hypervisor can backup & restore both full VMs and ISO files. In the Backpup & Restore-Manager the attached USB drivers are displayed.

If no disk was found, attach a USB drive and click on "scan for new devices". If the drive is not yet a "backup-space" for the Hypervisor, the drive needs to be formatted as backup space.

To make a backup or restore already made backups click on the USB drive link.

In the restore tab, previously backuped ISO files and Apps (VMs) can be restored back to the hypervisor disk. This may take several minutes and even hours depending on the file size and if the file is compressed. The backups can also be deleted here.

In the "Backup-Tab" local VMs and ISO files can be backuped. VMs can be compressed in order to save drive space.

Make sure that the drive is large enough to hold a compelete VM. Creating a backup can take several minutes and even hours, depending on the filesize and wether compression is used or not.

ISO Manager

The iso manager shows the lokal stored ISO files which can be used to boot a VM to install the OS provided in the ISO file (e.g. an Ubuntu ISO for installing Ubuntu in a VM). Isos can be deleted via the "delete" link.

There are 3 ways to get an ISO on the appliance:

  1. Web-Download
    1. The Web-URL of the ISO can be provided. If it is protected with basic auth, a username and password can be provided in the syntax "user:password". NOTE: this can take several minutes and even hours, depending of the size of the ISO and the internet speed.
  2. Upload 
    1. An iso of up to 8GB can be uploaded directly via the browser. NOTE: this can take several minutes and even hours, depending of the size of the ISO
  3. Windows Share Download
    1. With Window share credentials:
      * Domain        e.g.  beroNet 
      * Share Name    e.g.  //beronas/ISOs   (the share is only one Folder on the Server, like //SERVER/SHARE and SHARE does not have subfolders) 
      * user          e.g.  beroUser
      * password      e.g.  beroPassword

      a windows share, fileserver or NAS can be browsed. After clicking on an ISO File, the file will be downloaded. NOTE: this can take several minutes and even hours, depending of the size of the ISO

beroNet Appliance Market

The beroNet Appliance Market allows it to download pre-installed Virtual Machines. These machines can be started directly in the Hypervisor. The Market also allows to donwload ISO Installation Media for setting up new Virtual Machines.

Each VM or ISO has additional Meta Information like the version and the size. By clicking the download icon the VM or ISO will be downloaded to the lokal appliance.

NOTE: this can take several minutes or even hours, depending on the size and internet speed

How-to use clones / snapshots

The beroNet hypervisor GUI allows to create thin clones of existing VMS. A clone is not a full copy of a VM. The disks of the clone reference back to the parent so that only the differences for each clone are stored within the clone, while the main data resides within the parents disk. The mechanism used here is copy-on-write. The parents disk is not modified while the clones run, this means the parents VM state is saved as a snapshot. When the clones are deleted the parent can run again from the moment on when the first clone was created. At later times other clones can be created from the parent or even from clones.

The result is a tree, like in this example:

NOTE: only the orange leaves of the tree can actually run. But indeed they can run at the same time!

"Parent" and "clone 2" can be seen as snapshots as they preserve the VM state at the time when they ran at last.

To create a clone you need to go to the VM Manager of a VM on the STATUS Tab and click on "clone" and then provide a name of the clone (You can only create clones of powered of VMs).

After that the cloned VM becomes a parent and is in the STATUS CLONED:

Also a list of all clones of this VM is displayed:

You can always create new clones from this parent VM. These clones will have the state of the parent last time it was powered off.


Update Hypervisor

To update the hypervisor, simply click on the Version which you want to install.

Network Settings

The Network Manager allows to choose the Interface Mode of the appliance:

  • LAN - Both LAN Ports are bridged into a single network bridge
  • LAN-WAN - the 2 LAN Ports are put into seperate bridges, VMs which have LAN-WAN mode have the WAN Bridge as additional Network adapter

The LAN Mode can be defined as DHCP or static. If it is static the LAN Settings need to be defined. These settings do only apply to the LAN interface of the Appliance. The WAN Port however can only be controlled from within a VM which has the LAN-WAN mode enabled.

Cloud Settings

The cloud manager allows to register the appliance into the beroNet cloud or into a private beroNet cloud. After successfull registration a cloud key appears. The appliance starts communication with the beroNet cloud after enabling the cloud and after clicking "cloud enable".

NOTE: a reboot of the hypervisor might be needed to register the appliance in a different cloud'

Reboot & Halt

By clicking "CLICK HERE FOR REBOOTING THE APPLIANCE", the appliance does a reboot.

NOTE: all VMs will be halted ungracefully

By clicking "CLICK HERE FOR SYSTEM SHUTDOWN", the appliance will turn itself off.

NOTE: it is not possible to turn on the appliance from remote

Change password

Under System->change password, the password of the admin GUI User can be changed.


The Gateways Manager starts a bfdetect in the background and shows a list of all local appliances and Gateways with their Serials, Firmware Versions, IP Addresses and MAC Addresses.

By clicking on the IP Address, the browser will be redirected to the gateway/appliance GUI.

Write a comment…