portugalfuturista/universalisos
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
universalisos/docs-extracted/releasenotes/releasenotes-hwvirt-5.0.3.md
Fábio Coutada ae6144a1c5 feat(docs): extract all extractable PikeOS PDF manuals to markdown 
- Extract 37 of 45 PDFs under docs/ to docs-extracted/
- Preserve directory structure (apex, cdk, development, platform, etc.)
- Add docs-extracted/index.md with navigation table
- 8 PDFs were 0-byte/empty and could not be extracted
2026-07-06 23:07:19 +01:00

18 KiB
Raw Blame History

title source category pages extracted
Releasenotes Hwvirt 5.0.3 docs/releasenotes/releasenotes-hwvirt-5.0.3.pdf releasenotes 8 2026-07-06T23:05:51.032623

Releasenotes Hwvirt 5.0.3

Extracted from docs/releasenotes/releasenotes-hwvirt-5.0.3.pdf (8 pages). Figures, diagrams, and tables may not render accurately in plain text.

                                                                                              Release Notes

1 Product Release Information Product Name: Hardware Virtualization for PikeOS 5.0

Release and Build Number: 5.0.3/D5879

Release Date: 20.08.2019

2 Introduction This document contains the release notes for Hardware Virtualization for PikeOS 5.0, build D5879. The following sections describe the release in detail and provide information that supplements the main documentation. Users of previous releases should check section 3.3 for instructions on how to use existing data with this new release. For further information refer to the hardware virtualization (hardware-virtualization.pdf) manual which has been updated.

3 Installation and Upgrade News 3.1 Installation

Please see the manual PikeOS Installation Guide for more details.

3.2 Release Features

3.2.1 TrustZone support removed

The TrustZone support has been removed starting with this version of Hardware Virtualization for PikeOS.

3.2.2 Changes in the P4Bus/VMM protocols

The P4Bus and VMM protocols used to communicate between guests and their Hardware Virtualization for PikeOS manager has been updated and enhanced with this version of Hardware Virtualization for PikeOS. As a consequence your guest P4Bus and VMM drivers must be updated to be compatible with this release. Please check the hardware virtualization manual for more information.

3.3 Compatibility to Other Versions

Some configuration parameters have been renamed or removed in the components so it is recommended to update the configuration files of your guests in your integration project.

4 Enhancements introduced by this release 4.1 Enhancements introduced by this Release

Issue P00101-16987, [HWVIRT] New parameter to select file accesses of a vmfile for p4bus devices A new parameter was added in p4bus device component to select file accesses of a vmfile. The different accesses

c Copyright 2019 1 All rights reserved. SYSGO GmbH Release Notes

    available are 0 = No Access, 1 = Read Only, 2 = Write Only, 3 = Read Write, 4 = Read Write Map. The user can now
    easily configure device access from Codeo.

4.2 Problems fixed with this Release

None.

4.3 Known Problems

None.

5 Frequently Asked Questions Answers to frequently asked questions (FAQ) and resolutions to known issues are updated on a regular basis. These are available online at http://www.sysgo.com/support/

6 Updates and Support Updates will be provided on https://www.sysgo.com/downloadserver/. Please login using your account as stated on the delivery document. Product support is available online at http://www.sysgo.com/support/

c Copyright 2019 2 All rights reserved. SYSGO GmbH Release Notes

A Previous Release 5.0.2 S5804 A.1 Enhancements introduced by this Release

Issue P00101-12936, [HWVIRT] Policy violations by guest generates standard HM events Each different guest error generates a standard Health Monitoring event. Theses errors can be managed by group (by using filters) or individually. The group action is done first, groups are like filters to easily configure HM actions to do in error case. If P4_HM_PAC_IGNORE is selected for the group and a manual configuration exists for the error, the manual action will be done otherwise default action will be performed. If the error is tagged as fatal and all configurations are set as P4_HM_PAC_IGNORE, the partition will be automatically shutdown.

Issue P00101-14199, SMMU driver does not manage correctly partition reboot. SMMU driver free correctly page tables if partition is shutdown and tables are reallocate when the partition is restarted. SMMU transactions are disabled during partition reboot.

Issue P00101-15149, Enhance Virtio Memory HWVIRT Exception handler configurability The handler example can now be configured with several areas defined by:

        • A Name: used for logging and for property file system organization.
        • A Verbosity: used to log access to a particular area
        • A Guest physical start address
        • A Size in Bytes
        • A type: NULL or Memory

Issue P00101-15420, P4Bus-vmnet multicast support The p4bus-vmnet linux driver now properly support multicast when used with a PikeOS Driver supporting it.

Issue P00101-15932, [HWVIRT] Check for the state of a p4bus operation before executing it. The state of a p4bus operation is not checked before executing it, without raising any error to the user. The p4bus protocol shall check the status of the operation before executing it, and raise an event if the operation is not ready. When an operation to be executed by the P4BUS is not ready, a Health Monitoring event is raised (P4HWVIRT_E_MNG_P4BUS_INVAL_OP_STATUS).

Issue P00101-15933, [HWVIRT] P4BUS devices size can be greater than 32 bits It is now possible to use a P4BUS device with a size greater than 2GB.

Issue P00101-16225, [HWVIRT]: P4Bus ioctl interface for linux user clarified with new headers All p4bus defines and structures useful for Linux user have been extracted into a new driver header p4bus-vmchar.h.

Issue P00101-16307, Document Hypervisor Errors The hardware-virtualization document now describes the hypervisor errors code, symptoms and possible root cause.

Issue P00101-16368, [HWVIRT] Rework the P4BUS stat interface. P4BUS_IOCTL_STAT interface was reworked to support a size of 64 bits for each field. The structure is described in documentation.

Issue P00101-16444, Make HWVIRT Hypervisor Kernel Driver available for PikeOS 4.2.3 The HWVIRT Hypervisor Kernel Driver can be integrated in a Cortex A5x BSP fusion project of PikeOS 4.2.3.

Issue P00101-16681, [HWVIRT] Manager supports now standard coding style - Fix compiler warnings (strict) - Fix indentation - Fix headers

Issue P00101-16786, Linux Kernel 4.15 to 4.20 support The p4bus drivers provided with PikeOS are now compatible with Linux kernel up to the version 4.20.

c Copyright 2019 3 All rights reserved. SYSGO GmbH Release Notes

Issue P00101-16797, [HWVIRT] Two compatibility matrix between PikeOS and ELinOS has been added to the documentation Two matrix has been added to the documentation to explain compatibility between PikeOS and ELinOS. One describes the compatibility of P4BUS drivers included in ELinOS and the second one describes the compatibility of P4BUS drivers included in PikeOS.

Issue P00101-16992, Change default KMEMSIZE in guest process component The default value, i.e. the minimum value, of the thread info size (thrinfo_size) as doubled. This led to an increase of the memory consumption of the Hardware Virtualization. The solution has been to increase the default value of the Kernel Memory Size (KMEM) in the Guest process component.

Issue P00101-17027, [HWVIRT] Add original return code of the PikeOS driver in vmchar IOCTL A field containing the original return code of the PikeOS driver was added in the P4bus IOCTL native structure in the vmchar IOCTL API. The documentation has been modified accordingly.

Issue P00101-17044, [HWVIRT] vmblock p4bus linux driver automatically uses the good IOCTL api version by getting the block api version. To use the right PikeOS driver API, vmblock p4bus linux driver check the block device API version during the open of the device to automatically use the good IOCTL API.

A.2 Problems fixed with this Release

Issue P00101-14486, HWVIRT: Impossible to map non contiguous shared memory The manager is now supporting mmap operations with non contiguous shared memory on guest.

Issue P00101-15092, Linux Kernel 4.14 support The p4bus drivers provided with PikeOS are now compatible with Linux kernel up to the version 4.14.

Issue P00101-15169, HWVIRT: Impossible to map shared memory without cache attribute The manager is now supporting all SHM types (cache and non cached) for mmap operations on guest.

Issue P00101-15417, echo on /proc/vmapi looping infinitely An echo command done on the /proc/vmapi entry of a Linux guest was looping due to an invalid return code. This is fixed in the Linux P4Bus vmapi driver with this version of PikeOS.

Issue P00101-15418, Linux 4.14 supported by HWVIRT The p4bus drivers now properly support Linux 4.14. The code was changed to properly support the Stack remapping feature from the Linux kernel that is now activated by default on 4.14 and following Linux versions.

Issue P00101-15723, ARM hardware virtualization: virtual machine monitor misses preemption requests In some scenarios, the virtual machine monitor may have missed a preemption request when the execution was interrupted shortly before entering a virtual machine. In this case, the virtual machine executed until the next VM exit before scheduling again. A new function p4_kernel_is_preempt_pending() was added for the virtual machine monitor to check for pending preemption requests before entering a VM.

Issue P00101-15852, VMBLOCK driver not working with volume providers vmblock didn’t get the proper size with PikeOS block drivers. The problem is now fixed in vmblock driver with an IOCTL to get the size.

Issue P00101-16226, [HWVIRT] Configure script for ELinOS feature fails on Cygwin environment The issue is that the rule file used to compile the p4bus features are not correctly installed when using Cygwin as host environment. The rules are now correctly installed.

Issue P00101-16382, Binary not found in hwvirt-guest-pikeos Demo The issue was coming from the bad path given in ’Filename’. Indeed, it was looking for a dom file which did not exist. Fixed by : - modifying the Hardware Virtualization documentation and the readme of the hwvirt-guest-pikeos demo. - fixing the path of guest application (64bit for armv8 and 32bit for armv7).

c Copyright 2019 4 All rights reserved. SYSGO GmbH Release Notes

Issue P00101-16405, [HWVIRT] Missing directio component in ls1046 Some Guest OS might need to access the FlexTimer and the TMU, which led to an error as there were no directio components related to these devices. This issue has been fixed by adding the relevant direct IO configuration.

Issue P00101-16464, Manager: wrong documentation of virtio_handle The documentation of virtio_handle did not correspond to the function. The description is now fixed.

Issue P00101-16569, Wrong faulty address is logged when a data abort is raised It appears that on LS1046a-rd board the Hypervisor IPA Fault Address Register (hpfar_el2) is not always updated after a data abort, and the hypervisor always forward directly the value of hpfar_el2 after a data abort. The problem has been corrected by first checking the validity of the hpfar_el2 register with the Exception Syndrome Register, and by translating the Guest Faulty Virtual Address to get the right IPA.

Issue P00101-16611, Wrong data abort decoding for aarch32 guest For a aarch32 guest, when an ASR instruction is used to compute the origin address of a data abort, the decoding of the instruction by the hypervisor is not implemented as expected and data abort information is wrong. ASR instruction is now handled as expected by the hypervisor.

Issue P00101-16816, HWVIRT Hypervisor does not handle wrong configuration of GIC CPU and DIST Hypervisor now uses default values when the configuration parameters are set to zero.

Issue P00101-16830, [HWVIRT] All necessary accesses are checked during probe function in p4bus drivers All necessary accesses are checked during probe function in p4bus drivers. If a necessary access is not allowed the driver return an EACCES error.

Issue P00101-16918, [HWVIRT] Fix Fusion name in project xml of bsp-pikeos-hwvirt The name attribute of the Fusion element in the project.xml of the bsp-pikeos-hwvirt contains a space. Typo fixed.

Issue P00101-16963, [HWVIRT] Special User Zero register is not emulated by the hypervisor The Context of a Guest might be corrupted as the XZR/WZR register is not handled during GIC load/store exception decoding, The XZR/WZR register is now included in the Guest Context and set to zero.

A.3 Known Problems

None.

c Copyright 2019 5 All rights reserved. SYSGO GmbH Release Notes

B Previous Release 5.0.1.1 S5500 B.1 Enhancements introduced by this Release

None.

B.2 Problems fixed with this Release

None.

B.3 Known Problems

None.

c Copyright 2019 6 All rights reserved. SYSGO GmbH Release Notes

C Previous Release 5.0.1 S5440 C.1 Enhancements introduced by this Release

Issue P00101-10697, New Watchdog VMM Driver A new VMM device has been added to have a watchdog managed by the manager for guests. This can be used to monitor Linux or PikeOS guests by forcing them to refresh the watchdog. An action can be defined using Health Monitoring (halt or reboot or ignore) to configure how to handle a guest that does not refresh the watchdog.

Issue P00101-13686, Exception Handler can be extended in the kernel The Hardware Virtualization can now be extended in kernel drivers or PSP with external exception handlers. Those handlers can do things like:

        • handling IO errors to simulate hardware
        • handling SMC instructions to simulate a firmware
        • creating new communication system by extending the HVC exception handler
        • handling access to forbidden cpu registers (cp15 or msr/mrs instructions) to simulate processor features not
            accessibles to guest
        • extend the exception handler to handle some unsupported exceptions, 2 examples are provided as kernel driver
            demos.

    The documentation of hardware virtualization has also been extended to include an API documentation for functions
    available to external exception handlers.
    You can check the hardware virtualization documentation for more information.

Issue P00101-14186, Update of p4bus/vmm linux drivers The p4bus/vmm drivers for linux guest have been upgraded:

        • optimize ioring usage in network driver (to reduce manager thread usage during init)
        • optimize network performances, better handing of race conditions
        • add a vmm-watchdog driver
        • cleanup tty and vmchar driver code

C.2 Problems fixed with this Release

Issue P00101-14340, MSR exception result not reported to guest MSR exceptions handled by the manager or an external exception handler are now properly updating the guest context with the value returned with the exception.

Issue P00101-14605, P4Bus Linux driver fixed to compile with newer GCC version The P4Bus Linux drivers have been fixed to handle warning coming from newer gcc versions due to wrong indentation.

Issue P00101-15114, [HWVIRT] Wrong Core redirection of interrupts A bug has been solved which made interrupts redirected on guest core 0 even though the interrupt cpu mask was not set to 1 by the guest.

C.3 Known Problems

None.

c Copyright 2019 7 All rights reserved. SYSGO GmbH Release Notes

D Previous Release 5.0 S5319 D.1 Enhancements introduced by this release

Issue P00101-13719, KDEV: per-CPU initialization callback The init_drv_cpu callback allows kernel drivers to perform a per-CPU setup at init time. The callback is called on each CPU after the context of the idle thread of the CPU has already been setup, after the other initialization callbacks have been invoked.

D.2 Problems fixed with this release

None.

D.3 Known Problems

Issue P00101-14232, HWVIRT guest devices are mapped without executable rights Direct-IO guest devices are mapped uncacheable but the XN bit is currently not set in the hypervisor MMU configu- ration. If a guest is running without MMU configured or without the XN bit set for devices mapping, this might lead to random guest asynchronous aborts if the speculative instruction fetch is trying to pre-load from a device area.

Issue P00101-14340, MSR exception result not reported to guest When an MSR exception is handled by the manager or an external exception handler, the guest register is not properly updated with the returned value. To workaround this issue the context must be updated manually by the handler.

c Copyright 2019 8 All rights reserved. SYSGO GmbH