Hypervisor Installation Guide: Linux

Table of Contents

  1. Introduction
  2. Prerequisites
    2.1 Required Software
    2.2 Required Hardware
    2.3 GPOS
    2.4 Necessary Accessories
    2.5 Hardware Specific Requirements
  3. Steps to Install Hypervisor
    3.1 Update the BIOS (if necessary)
    3.2 Configure the BIOS
    3.3 Install B&R Installation Packages (Only Required for Non-B&R Linux Image)
    3.4 Shrink the Linux Volume (If Not Done During Linux Installation)
    3.5 Plan Ethernet and USB Interfaces
    3.6 Configure the Automation Studio Project for Hypervisor
    3.7 Generate the Hypervisor USB Install Drive
    3.8 Install the B&R Hypervisor Driver
    3.9 Install Hypervisor
    3.10 Connect to ARembedded via Automation Studio
  4. Appendices
    4.1 Appendix A – Hardware Specific BIOS/UEFI Setting Requirements
    4.2 Appendix B - Hyperthreading
    4.3 Appendix C – FAQ
    4.4 Appendix D – Troubleshooting Tips
    4.5 Appendix E - Known Issues
    4.6 Appendix F - B&R Support

1 Introduction

B&R Hypervisor makes it possible to run B&R Automation Runtime parallel to Windows or Linux on a B&R PC. Each operating system runs directly and exclusively on the hardware allocated to it. All of the configuration for Hypervisor is done in Automation Studio.

The purpose of this document is to provide a step-by-step guide for B&R Hypervisor installation with Windows as the GPOS. It is assumed that the user has basic knowledge of B&R systems and Automation Studio.

For a full overview of the details and theory behind B&R Hypervisor, refer to the following location in the AS Help: Real-time operating system → Target systems → Target systems – SG4 → B&R Hypervisor.

2 Prerequisites

Before you get started with the Hypervisor installation, verify that you are using supported hardware / software and that you have the necessary accessories at your disposal.

2.1 Required Software

B&R Hypervisor is available beginning with the following Automation Studio / Automation Runtime versions, depending on your target:

PLC Family Minimum AS/AR Versions
PC9xx AS 4.4 / AR F4.44
PC21xx AS 4.4 / AR F4.44
PC22xx AS 4.6 / AR E4.61
PC31xx* AS 4.4.5 / AR B4.45
MPC3100 AS 4.10 / AR B4.91
APC4100 AS 6.0 / AR 6.0

* requires hardware upgrade 2.0.0.0 or newer

2.2 Required Hardware

  • x86 architecture with BIOS/CSM support
  • At least one logical CPU must be available for each configured operating system
  • RAM: 4 GB (technically 2 GB can be sufficient, but 4 GB is highly recommended)

2.3 GPOS

GPOS stands for General Purpose Operating System. The GPOS (Linux) runs parallel to ARembedded. The GPOS must already be installed on the target system prior to Hypervisor installation.

Supported GPOSs:

  • B&R (Debian) Linux 9 64bit (legacy boot)
  • B&R (Debian) Linux 9 64bit (UEFI boot). Supported with AS4.7 and up.
  • B&R (Debian) Linux 10, 64-bit (UEFI boot)

This installation guide is designed for the case that Linux is the GPOS. If you need the installation guide for Windows as the GPOS, please contact the B&R Support team (Appendix F).

2.4 Necessary Accessories

  • USB mass storage device (note that all existing contents will be overwritten!)
  • USB keyboard
  • A USB hub is helpful if your PC only has 2 USB ports total (e.g. the PC2100 / PC2200)

2.5 Hardware Specific Requirements

See Appendix A.

3 Steps to Install Hypervisor

3.1 Update the BIOS (if necessary)

If your MTCX version is insufficient, then it will be updated when Hypervisor is installed. On the contrary, if your BIOS version is insufficient, then you must update this manually.

  1. Determine the minimum required BIOS version for your PC according to the chart below. This information can also be found in the Help at the following path:

    Real-time operating system → Target systems → Target systems – SG4 → B&R Hypervisor → Configuration and installation → Preparations for installation

    PC Family Minimum BIOS Version
    xPC9xx-TS77 1.27
    xPC9xx-TS17 1.14
    xPC2100 1.40
    xPC2200 1.05
    xPC3100 1.12
    MPC3100 1.00
    APC4100 1.10
  2. Determine what keystroke is required to enter the BIOS on your PC. Refer to the chart below:

    PC Family Key to Enter BIOS
    xPC9xx F2 or Del
    xPC21xx F2
    xPC22xx F2, Del or Esc
    xPC31xx F2, Del or Esc
    MPC3100 F2, Del or Esc
    APC4100 F2, Del or Esc
  3. Cycle power on the PC. Repeatedly press the key identified in Step 2 while the PC is booting to enter the BIOS.

  4. The BIOS version can be viewed on the Main page of the BIOS with no additional user input for all PCs except for the PC2100. In the case of the PC2100, on the Main page you must click Enter on “System Information” and then you will see the BIOS version.

    If your BIOS version is less than the required BIOS version identified in Step 1, then it needs to be updated before Hypervisor is installed. If your BIOS version is already sufficient, skip to Section 3.2.

  5. The BIOS upgrade files and steps to perform the BIOS upgrade can be found on the B&R website (www.br-automation.com). Click the Downloads tab, then specify your PC family. For example, for the PPC2100:

    You may have to click “Load more” at the bottom of the download results to find the BIOS and User’s Manual. Then the BIOS will appear in the list:

    The manual will be found in the documentation section:

    The steps to update the BIOS are included in the PC User’s Manual. Refer to the “Software” chapter and update the BIOS.

  6. After the BIOS update is complete, repeat Steps 2 & 3 to go back into the BIOS in preparation for Section 3.2.

3.2 Configure the BIOS

At this point you should still be in the BIOS of your PC. If not, repeat Section 3.1 Steps 2 & 3 to enter the BIOS. Then:

  1. Restore BIOS defaults by pressing “F9” followed by “Enter”.

  2. Navigate to the following location in the AS Help to identify the required BIOS settings for your PC for Hypervisor:

    Real-time operating system → Target systems → Target systems – SG4 → B&R Hypervisor → Configuration and installation → Preparations for installation

  3. Make the necessary changes in the BIOS.

  4. Press “F10” to save changes and exit the BIOS. Wait for the PC to boot back into Linux.

3.3 Install B&R Installation Packages (Only Required for Non-B&R Linux Image)

If you have installed a generic Debian 9 image (as opposed to the B&R Linux 9 image which would be installed on the PC from the B&R factory), then at this point you need to install several installation packages to make the generic image equivalent to the B&R image. If you are already using the B&R Linux 9, then skip to Section 3.4.

A full list of required installation packages is shown below:

  • First Config: Contains the B&R First Config program for automatic configuration on the first boot.

  • Service Tool: Contains the B&R Service Tool program for easy configuration of common tasks.

  • Touch Screen: Contains the B&R Touch Screen program for setting and calibrating resistive and capacitive touch screens.

  • Touch Click: Contains the B&R Touch Click program.

  • MTCX driver: Contains the B&R MTCX driver for communicating with the MTCX on a B&R device.

  • ADI Library: Contains the B&R ADI library.

  • Display Brightness: Contains the B&R Display Brightness control.

  • License Viewer: Contains the B&R License Viewer program.

  • UPS Daemon: Contains the B&R UPS service.

  • UPS Control: Contains the B&R UPS Management program.

The installation packages can be found on the B&R website (www.br-automation.com) via the Downloads tab and the following download filters:

Once you have downloaded the installation packages, copy them to the Linux PC and install them via the GDebi Package Installer.

3.4 Shrink the Linux Volume (If Not Done During Linux Installation)

The size of the Linux volume needs to be decreased to make space for ARembedded. Various tools can be used to adjust the Linux partition. The steps below will use GParted Live, installed on a USB drive via Rufus.

GParted Live is the tool which can adjust the size of the Linux partition. The tool Rufus is used to create a bootable USB drive and install the GParted Live ISO.

If you prefer an alternate method of installing GParted Live which does not involve Rufus, refer to the methods described at the following link and then skip to step 7: http://gparted.sourceforge.net/liveusb.php

  1. Navigate to: GParted -- Download

  2. Download the ISO for the Stable Release labelled for amd64 (e.g. “Download gparted-live-1.0.0-5-amd64.iso”).

  3. Navigate to: https://rufus.ie

  4. Download Rufus. This download will yield an executable (e.g. rufus-3.8.exe).

  5. Plug your first USB drive into the development PC (laptop). Note that all contents will be overwritten.

  6. Run the Rufus executable. Then in Rufus:

    a. Set the “Device” dropdown to your USB drive.

    b. Set the “Boot selection” dropdown to “Disk or ISO image”. Click the “SELECT” button to navigate to the GParted Live ISO file that you downloaded in Step 2.

    c. The rest of the Rufus settings can be left at the default value. Click the “START” button at the bottom.

    d. Click “Yes” to the subsequent pop-up to download the necessary Syslinux files:

    e. Select “Write in ISO Image mode (Recommended)” in the next pop-up, and then click “OK”:

    f. Click “OK” for the last pop-up:

    g. Wait for the process to complete. Once the status bar says “READY”, click close:


  7. Boot the B&R PC off the USB drive which was prepared by Rufus in Step 6. To do so:

    a. Determine what keystroke is required to enter the boot menu on your B&R PC. Refer to the chart below:

    PC Family Key to Enter Boot Menu
    PC9xx F11
    PC21xx F5
    PC22xx F2, Del or Esc → Select “Boot Manager”
    PC31xx F2, Del or Esc → Select “Boot Manager”
    MPC3100 F2, Del or Esc → Select “Boot Manager”
    APC4100 F2, Del or Esc → Select “Boot Manager”

    b. Power up the B&R PC. Repeatedly press the key identified in Step A on the USB keyboard while the PC is booting to enter the Boot Menu.

    c. Once you are in the Boot Menu, select the USB drive from the list. This will cause the B&R PC to boot from the USB drive and launch the GParted Live tool.

  8. Once the PC boots from the USB drive you will see the Gnome Partition Editor. Select the first option for “GParted Live (Default Settings)” and press Enter:

  9. Wait several seconds for the next menu to load. Then select “Don’t touch keymap” and press Enter:

  10. When asked “Which language do you prefer?”, press Enter to select the default value of 33 (US English).

  11. When asked “Which mode do you prefer?”, press Enter to select the default value of 0 (“Continue to start X to use GParted automatically”).

  12. Next, the GParted tool will load automatically. Right click on the main partition (/dev/sda1) and select “Resize/Move”. Alternatively, you can select the main partition and then go the Partition menu at the top to select “Resize/Move”.

  13. Set the “Free space following (MiB)” to at least 1024 MB (2048 MB is recommended). Then click “Resize/Move”.

    Note that you cannot set the free space so high that the “New size (MiB)” is less than the “Minimum size” listed at the top.

  14. Afterwards, you will see that there is one operation pending to shrink the drive. Click the green checkbox at the top to execute the operation.

  15. Click “Apply” to confirm the operation:

  16. After a few moments, you will see a message indicating that “All operations successfully completed”. Click “Close”.

  17. Afterwards, you will see that the unallocated space has increased to the size allocated in Step 13. The size of the Linux partition has decreased accordingly. Close out of GParted by clicking the square icon in the far right at the top (not pictured).

  18. Double-click on the “Exit” icon on the top left. Then select “Shutdown” and click “OK”.

  19. Cycle power on the PC to boot back into Linux and login.

3.5 Plan Ethernet and USB Interfaces

The physical Ethernet and USB ports on the B&R PC must be assigned to either ARembedded or Linux. They cannot be accessed by both operating systems. Therefore, at this point you must decide which interfaces will correspond to which operating system. Take note of the following:

  • At least one USB port must be assigned to ARembedded

  • At the moment, any USB ports integrated into the panel will always be assigned to the GPOS

  • You must use a USB port which is assigned to ARembedded for your Technology Guard dongle

For example, the PPC2100 has two Ethernet ports and two USB ports. Therefore, one of each port can be assigned to each operating system:

Interface Address Example OS Assignment
ETH1 IF3 ARemb
ETH2 IF4 Linux
USB1 IF5 ARemb
USB2 IF6 Linux

3.6 Configure the Automation Studio Project for Hypervisor

At this point it is assumed that an Automation Studio project has been created with the relevant hardware.

  1. Confirm that the correct PC hardware has been set in the Physical View.

  2. Open the CPU configuration (Physical View, right-click on CPU, select “Configuration”). At the bottom, expand “B&R Hypervisor configuration” and make two changes:

    a. Set “Activate B&R Hypervisor” to “on”.

    b. Set the “Size of DRAM” to a value between 256 MiB and 2048 MiB. This corresponds to the amount of DRAM assigned to ARembedded. The remaining DRAM on your PC gets assigned to Linux.

    For example, a 5PPC2100.​BY48-000 has 8GB of DRAM (refer to the Technical Data of the datasheet). If 1GB is assigned to ARembedded in the CPU configuration, then 7GB are left for Linux.

  3. Assign the Ethernet interfaces according to the planning from Section 3.5. To do so:

    a. From the Physical View, right click on an Ethernet interface and select “Configuration”.

    b. Assign the interface to either ARembedded or Linux (GPOS) via the “Operating system” dropdown.

    c. If you assign the interface to ARembedded, set the IP parameters as needed for the application. This will be the IP address that you use to connect to ARembedded via Automation Studio.

    d. Repeat for all Ethernet interfaces.

  4. Assign the USB interfaces according to the planning from Section 3.5. To do so:

    a. From the Physical View, right click on a USB interface and select “Configuration”.

    b. Assign the interface to either ARembedded or Linux (GPOS) via the “Operating system” dropdown.

    c. Repeat for all USB interfaces. Remember that at least one USB interface must be assigned to ARembedded.

Any interfaces that are assigned to the GPOS (Linux) will appear grayed out in the Physical View and will be indicated by “–> GPOS” (with the exception of USB ports integrated directly into the panel).

3.7 Generate the Hypervisor USB Install Drive

  1. Plug your second USB drive into your development PC (laptop). Any USB flash drive (USB2.0 or USB3.0) with sufficient storage space will suffice. Note that in the following steps, all of the existing contents of the USB drive will be destroyed. Be sure to copy any pertinent files from the USB drive to another storage medium as needed.

  2. Rebuild the project (Project → Rebuild Configuration). After the build completes, select “Don’t Transfer” on the transfer pop-up.

  3. Go to “Project” → “Project Installation” → “Create USB Install Drive”.

  4. In the resulting pop-up, confirm the drive letter corresponding to your USB drive has been selected in the drop-down. Then click “Install on application storage”. You will then see a pop-up reminding you that the USB drive will be formatted, and all existing data will be lost. Click “Yes” to this pop-up.

  5. Once the install finishes, click “Close”. Remove the USB drive from your development PC.

3.8 Install the B&R Hypervisor Driver

The B&R Hypervisor Driver installer was automatically added to your USB drive when you created the Hypervisor USB Install Drive in Section 3.7. To install:

  1. Plug the USB drive into the B&R PC and boot the PC into Linux.

  2. Copy/paste the Hypervisor driver installer from the USB drive onto the PC (e.g. the Desktop). The installer will be located on the USB drive at the following path:

    D:\BRHypervisor\GPOSDrivers\Linux

  3. Open the GDebi Package Installer via the Start menu → System Tools → GDebi Package Installer:

  4. Go to File → Open and then navigate to the brhypervisor_1.3.0-1_amd64.deb file that you copied in Step 2. Click “Open”:

  5. Click “Install Package”:

  6. Provide the administrative password if/when prompted.

  7. The B&R Hypervisor driver is installed. Once installation is complete, you will see a message indicating that the installation has finished. Click “Close” and then close the Package Installer.

3.9 Install Hypervisor

Now that the Hypervisor driver has been installed, Hypervisor itself as well as Automation Runtime and the application project need to be installed. To do so:

  1. Shut down Linux and power down the B&R PC.

  2. Plug the USB drive that was prepared in Section 3.7 into a USB port which was assigned to ARembedded in Section 3.6 Step 4. This is very important: you must plug the USB drive containing the Hypervisor installation into a USB port which is assigned to ARembedded. Hypervisor will not install properly if you plug the USB drive into a USB port which is assigned to Linux!

  3. Determine what keystroke is required to enter the boot menu on your PC. Refer to the chart below:

    PC Family Key to Enter Boot Menu
    PC9xx F11
    PC21xx F5
    PC22xx F2, Del or Esc → Select “Boot Manager”
    PC31xx F2, Del or Esc → Select “Boot Manager”
    MPC3100 F2, Del or Esc → Select “Boot Manager”
    APC4100 F2, Del or Esc → Select “Boot Manager”
  4. Power up the PC. Repeatedly press the key identified in Step 3 while the PC is booting to enter the Boot Menu.

  5. Once you are in the Boot Menu, select the USB drive from the list. This will cause the B&R PC to boot from the USB drive.

  6. You will see a black screen with a lot of vertically scrolling white text. Wait for this process to finish.

  7. Next, you will see a box with two options. Highlight option 1 for “Install” and press Enter to select this option.

  8. On the subsequent selection box, highlight “Install” and press Enter.

  9. On the final message box, press Enter to trigger the PC to restart:

  10. Hypervisor is installed. This process will take at least 4 minutes. The PC will reboot 5 times. Once installation is complete, the PC will boot back into Linux.

    If the PC does not boot back into Linux after about 10 minutes, refer to Section 4 for troubleshooting steps.

3.10 Connect to ARembedded via Automation Studio

Now that Hypervisor is installed, ARembedded can be accessed via Automation Studio just like a standard ARembedded target (i.e. X20CPU). Go to to “Online” → “Settings” to either manually connect to the IP address that you configured in Section 3.6 Step 3c or browse for the target. If you have trouble connecting to ARembedded, contact B&R Support (Appendix F).

4 Appendices

Seperated to accomodate character limit.

4 Likes

4.1 Appendix A – Hardware Specific BIOS/UEFI Setting Requirements

4.1.1 xPC9xx-TS77

APC910 (TS77)

  • Main BIOS Version: ≥ 1.27 (menu path: Main)

  • MTCX Version: ≥ 1.24

  • ARemb Upgrade: ≥ F4.44

  • Automation Studio: ≥ V4.4 (V4.8.2 for 5PC910.SX03-00)

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Intel Virtualization Technology: Enabled (menu path: Advanced / CPU configuration)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

  • Boot option sorting method: UEFI and Legacy (menu path: Boot / Boot configuration)

PPC900 (TS77) (Same as APC unless otherwise noted)

  • BIOS version: ≥ 1.26 (menu path: Main)

Additional information for APC910 & PPC900 (TS77):

  • Hardware support for virtualization technology (main BIOS version <1.30)

  • Hardware support for hypervisor operation (main BIOS version ≥1.30) (recommended)

  • UEFI GPOS is not supported on the target system.

4.1.2 xPC9xx-TS17

APC910 & PPC900 (TS17)

  • Main BIOS Version: ≥ 1.27 (menu path: Main)

  • MTCX Version: ≥ 1.24

  • ARemb Upgrade: ≥ F4.44

  • Automation Studio: ≥ V4.4 (V4.8.2 for 5PC910.SX03-00)

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

Additional information for APC910 & PPC900:

  • Hardware support for virtualization technology (main BIOS version <1.16)

  • Hardware support for hypervisor operation (main BIOS version ≥1.16) (recommended)

4.1.3 xPC2100

APC2100 & PPC2100

  • Main BIOS Version: ≥ 1.27 (menu path: Advanced / OEM Features)

  • MTCX Version: ≥ 1.13

  • ARemb Upgrade: ≥ F4.44

  • Automation Studio: ≥ V4.4

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

Additional information for APC2100 & PPC2100:

  • Hardware support for virtualization technology (main BIOS version <1.40)

  • Hardware support for hypervisor operation (main BIOS version ≥1.40) (recommended)

  • Set the boot type according to the GPOS type (see Appendix 4.3.6)

4.1.4 xPC2200

APC2200 & PPC2200

  • Main BIOS Version: ≥ 1.05 (menu path: Main)

  • MTCX Version: ≥ 1.05

  • ARemb Upgrade: ≥ F4.63

  • Automation Studio: ≥ V4.6.2

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

  • EFI device first (menu path: Boot): Dependent on GPOS Type (see Appendix 4.3.6)

    • Legacy Boot: Disabled

    • UEFI Boot: Enabled

4.1.5 xPC3100

APC3100 & PPC3100

  • Main BIOS Version: ≥ 1.12 (menu path: Main)

  • MTCX Version: ≥ 4.19

  • ARemb Upgrade: ≥ B4.45

  • Automation Studio: ≥ V4.4.5

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

  • EFI device first (menu path: Boot): Dependent on GPOS Type (see Appendix 4.3.6)

    • Legacy Boot: Disabled

    • UEFI Boot: Enabled

4.1.6 MPC3100

APC Mobile

  • Main BIOS Version: ≥ 1.00 (menu path: Main)

  • MTCX Version: ≥ 1.00

  • ARemb Upgrade: ≥ B4.91

  • Automation Studio: ≥ V4.10

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

  • EFI device first (menu path: Boot): Dependent on GPOS Type (see Appendix 4.3.6)

    • Legacy Boot: Disabled

    • UEFI Boot: Enabled

4.1.7 APC4100

APC4100

  • Main BIOS Version: ≥ 1.10 (menu path: Main)

  • ARemb Upgrade: ≥ 6.0

  • Automation Studio: ≥ V6.0

  • Real-time environment: Enabled (menu path: Advanced / OEM features)

  • Hypervisor environment: Enabled (menu path: Advanced / OEM features)

4.2 Appendix B - Hyperthreading

Starting with Automation Runtime A4.71, hyperthreading can be used if the hardware supports it. To do this, setting “Real-time environment” must be disabled. This enables hyperthreading in a hypervisor system and preserves all other settings necessary for real-time operation. Automation Runtime also uses a physical core exclusively for hyperthreading. It is possible to enabled “shared mode” in Automation Runtime A4.91 and later.

4.3 Appendix C – FAQ

A few frequently asked questions are listed below. For an additional list of FAQ, refer to the AS Help:

Real-time operating system → Target systems → Target systems – SG4 → B&R Hypervisor → FAQ

4.3.1 How to Uninstall Hypervisor

To uninstall Hypervisor, repeat Section 3.9 steps 1 – 5 using the same USB drive you used to install Hypervisor. After you boot from the USB stick you will see the menu shown below. Select option 1 to “Deinstall” Hypervisor and press Enter. After uninstallation is complete, the PC will reboot.

4.3.2 What is ETHinternal?

ETHinternal is a virtual Ethernet port which provides a connection between ARembedded and Linux. By default, ETHinternal is configured to act as a DHCP server. It can be used to assign the IP addresses to the Ethernet ports on the Linux side (provided that they are configured to receive their IP addresses from a DHCP server). This interface can be used to communicate via sockets, with the AsTCP and AsUDP libraries.

4.3.3 Why does Linux reboot when AR restarts?

ARembedded is not affected when Linux is restarted. However, if ARembedded is restarted (via a warm restart, for example), then Linux will restart. The reason this happens is because a power fail is executed by AR, which prompts the GPOS to also shut down.

This behavior only occurs if the application was developed with AS 4.4 – AS 4.6. The behavior was improved with AS4.7 so that a restart of ARembedded does not trigger a restart of the GPOS.

4.3.4 How do you access the mapp View visualization?

There are no differences in the way that mapp View is developed or configured in the Automation Studio project when Hypervisor is in use. Once the project has been transferred to ARembedded, the mapp View visualization can be accessed on the Linux side by using the IP address of ETHinternal in Google Chromium.

If you are connecting to mapp View using an external client, then connect to an Ethernet port assigned to ARembedded and use the IP address of that ARembedded Ethernet port. If you only have the option to connect to an Ethernet port which is assigned to Linux, then contact the B&R Support team (Section 6) for the additional steps required to access the mapp View visualization.

4.3.5 Why can’t I repartition the target via transfer?

With a UEFI hypervisor system, there is a limitation that prevents repartitioning from being performed while the system is running. This limitation is not present with legacy boot. Refer to the chart below:

4.3.6 How do I determine whether my Linux installation is UEFI or Legacy?

  • Open your terminal and run this single-line command:

    [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

    • If the output says UEFI, your system booted using UEFI mode.
    • If the output says BIOS, your system booted using legacy BIOS mode

4.4 Appendix D – Troubleshooting Tips

If Hypervisor does not install properly, check the following points in the provided order:

4.4.1 Confirm the USB Port

Confirm that the USB port you have plugged the Hypervisor Install Drive into has been assigned to ARembedded. Refer to Section 3.6 Step 4. If you try to install Hypervisor on a USB port that is assigned to Linux, then the installation will hang on a black screen with white text. The last line will likely read “/OS/1 Booting runtime 0” or “/OS/1 I/O access blocked”.

4.4.2 Re-generate the USB Install Drive

Repeat Section 3.7 (Generate the Hypervisor USB Install Drive) and 3.9 (Install Hypervisor). Sometimes this is all it takes to get Hypervisor to install correctly.

4.4.3 Try a Different USB Drive

Repeat Section 3.7, but use a different USB drive. Make sure it is not only a different drive, but also a different brand from the one you initially tried. Then repeat Section 3.9.

4.4.4 Check the BIOS

Confirm that the BIOS settings were set correctly (refer to Section 3.2).

4.4.5 Confirm the Hardware Configuration

Confirm that you configured the correct hardware for the PC in the Physical View of the Automation Studio project. If you did not, then correct the error and repeat Section 3.7 and 3.9.

4.4.6 Try a Different USB Port

Try installing Hypervisor via a different USB port on the PC. Note that this may require you to change some settings in the Automation Studio project and regenerate the USB install drive, since the USB port that you use for installation must be assigned to ARembedded. Refer to Section 3.6 Step 4.

4.4.7 Check the Available Log Files

There are three log files that can be consulted if Hypervisor does not install properly:

  1. There will be a log file on the root directory of the USB drive called “install_log.txt”.

  2. There will be another log file in the root directory of one of the partitions on the CFast card, called “log.txt”.

  3. Depending on how far AR was able to boot, you may be able to get the AR log file from AS or the SDM.

Check all logs that are available to you for errors or information which point to the problem. Depending on the situation, you may only have 1 or 2 of these logs at your disposal. If anything in the logs is unclear, contact the B&R Support team (see Section 6) and provide any available logs.

4.5 Appendix E - Known Issues

4.5.1 Freezing During Installation, ARemb in RUN/SERVICE

Symptoms

  • Shell (black screen with text) stuck at “/OS/1 Booting runtime 0”

  • OS doesn’t boot but ARemb is in RUN mode and can be connected to through assigned ETH por

  • Differences in the Online Software Comparison (Automation Studio → Online → Compare → Software)

  • GPOS will start when you download application from AS to the ARemb directly through ETH port

Possible Cause & Remedy

  • USB stick was plugged into the wrong port on the industrial PC. It is necessary to plug in the Hypervisor Installation USB stick in the USB port assigned to ARemb (not grayed out in Physical View)

  • Go to Online > Compare > Hardware and check used HW in the AS and really used HW on the target. If there are differences, resolve them

4.5.2 Installation Stuck at 30% and Welcome to Buildroot Message Appears

Symptoms

  • During installation the installer freezes at 30% and “Welcome to Buildroot” as well as “Buildroot login:” appear
  • After restart and start of the installation again you will see message that boot loader already exist.

Possible Cause & Remedy

  • The unallocated partition is not the last one in the list. It’s possible that the free space was created with “Free space preceding” instead of “New size”.

  • Linux may need to be reinstalled.

4.6 Appendix F - B&R Support

If you run into any problems installing Hypervisor which are not clarified by this document, please contact your local B&R Support team.

thanks for sharing..to others, this is wiki post, so to others, feel free to contribute and update it with your findings. :slight_smile:

2 Likes