PPC3100 - Hypervisor network interface missing after BR9 to BR12 migration

Ask Questions B&R Software & Runtime
,
1

Greetings,

I am encountering an issue following the migration of a B&R machine from Linux B&R 9 to Linux B&R 12.

I have reinstalled the Hypervisor using the identical configuration that previously functioned seamlessly under B&R 9. Under B&R 9, all systems operated correctly:

  • The Hypervisor virtual network interface was present;
  • Visualization was fully accessible;
  • Chromium launched automatically at startup, displaying the HMI page hosted by the Runtime.

Since the transition to B&R 12, however:

  • The Hypervisor virtual interface no longer appears in the Linux network interfaces (as verified via “ip addr show”);
  • Only physical network interfaces are visible;
  • The IP address previously used to access the visualization is no longer identifiable;
  • Chromium no longer launches the HMI page automatically;
  • It remains unclear whether the visualization is still hosted or accessible.

A peculiar observation: I can still communicate with the CPU via an IP address that does not correspond to any interface visible under Linux, which appears anomalous.

Regarding the Hypervisor:

  • The “rth-virt.service” fails to start properly;
  • The device “/dev/rthBaseDrv” is absent;
  • During the installation of RTH components, I observed errors such as:
    • “could not insert ‘vnetDrvVirt’: Invalid argument”;
    • “could not insert ‘rthBaseDrvVirt’: Invalid argument”;
  • Additionally, PCI-related messages concerning 32-bit BARs appear during boot.

I would appreciate clarification on the following points:

  1. Should the Hypervisor virtual interface be automatically recreated under B&R 12?
  2. Could the absence of this interface account for the loss of access to the visualization?
  3. How can one identify the actual IP address utilized by the Runtime if it does not appear in the Linux network interfaces?
  4. Is there a specific procedure for migrating or restoring the Hypervisor between B&R 9 and B&R 12?

Thank you for your assistance.

2

A critical supplementary observation:

From Automation Studio, I can consistently establish a connection to the CPU and transfer programs without error, utilizing an IP address that remains invisible within the network interfaces exposed under Linux (as verified via “ip addr show”).

Communication with the CPU through Automation Studio operates flawlessly—including project uploads, downloads, and online access—indicating that connectivity to the Runtime is partially functional.

Nevertheless, the internal network interface of the Hypervisor/Runtime, which should be accessible under Linux, appears to be absent or unexposed at the system level. This discrepancy prevents alignment between the network configuration in Automation Studio and the interfaces visible within Linux.

In summary:

  • The connection from Automation Studio to the CPU succeeds via an IP address not visible in Linux.
  • Program transfers execute without issue.
  • However, the virtual network interface of the Hypervisor/Runtime is absent from the Linux environment.
  • The internal network configuration appears to be partially desynchronized between the Runtime and the Linux host.
3

Hello,

Have you properly installed B&R Hypervisor driver?

4

migration of a B&R machine from Linux B&R 9 to Linux B&R 12.

Which Automation Runtime you are using ?

5

I use automation studio J4.93

6

From my understanding you need at least a AR6 version if you want to use Linux 12.

You could try to use the driver package from a latest AR6.6 version and install that in Linux 12 but use an older runtime combination.

7

Yes, I just read the HMI report and all drivers have been installed.

8

What would be the address to access the visualization?

17805783245764761434990365519828
178057832457647614349903655198281920×2560 918 KB

9

default 192.168.137.1

10

Thank you. The issue stemmed from an outdated runtime version. I reinstalled the hypervisor with a more recent runtime, and the problem has been resolved.