NAME = test_ds
DS_MAD = virtiofs
TM_MAD = local
TYPE = IMAGE_DS
DISK_TYPE = FILESYSTEM
oneadmin@ubuntu2204-kvm-ssh-7-0-f4a9-0:~$ cat img.txt
NAME="test_fs"
TYPE="FILESYSTEM"
PATH="/var/tmp/sharedfs_test"
PERSISTENT="YES"
PERSISTENT_TYPE="SHAREABLE"
DISK=[
IMAGE_ID="21" ]
Notes:
* Same FS image cannot be used twice in the same VirtualMachine, nor the
same tag twice
* OpenNebula will generate a MOUNT_POINT = /mnt/one-fs-<image_id> and a
MOUNT_TAG = one-tag-<image_id>. Both can be overwritten at DISK level.
* When using Hugepages in the VM that will be used for virtiofs and
memory access will default to shared. Do not use
MEMORY_ACCESS='private'
* If not using hugepages the VM will use memfd as memoryBacking source
if it includes a filesystem.
* OpenNebula will map FS access (UID/GID) to a given user that can be
configured per host, cluster or globally in vmm_exec_kvm.conf. By
default all access is mapped to oneadmin account.
* Datastore monitorization will report 0 free/used/total size. Images,
representing the FS folder, reports size as the result of a du -sb
command.
* Most of the disk operations do not apply to filesystem disks: resize, snapshots,
save-as, backup.
co-authored-by: MarioRobres <mrobres@opennebula.io>
co-authored-by: Marco Mancini <mmancini@opennebula.io>
Signed-off-by: MarioRobres <mrobres@opennebula.io>
Signed-off-by: Marco Mancini <mmancini@opennebula.io>
- vmm,vnm: unify OVS DPDK vhost socket handling
- Use a shared /var/lib/one/vhost-sockets path for OVS DPDK interfaces in the KVM and Open vSwitch drivers, and create the directory when needed.
- Also fix DPDK NIC attach/detach to use the vhostuser device XML.
Add new attribute to prevent migrations on unsopported drivers. Add
migrator to add it to DS templates
coauthored-by: Guillermo Ramos <gramos@opennebula.io>
Signed-off-by: Guillermo Ramos <gramos@opennebula.io>
BRIDGE_TYPE can be now a comma separated list "openvswitch,
openvswitch_dpdk". When created a VNET any value from the list for that
driver can be set.
NOTE: This commit includes oned.conf changes
(cherry picked from commit aa33731c288ca928c9d13c18e1ca5a67ff692262)
add oned.conf
The following TM's now support storage live migrations:
- File system based (local and shared variants)
- LVM based (pure LVM, and LVM thin)
The LVM TM's does not support migrating a VM with disk snapshots.
co-authored-by: Guillermo Ramos <gramos@opennebula.io>
co-authored-by: josepselga <jselga@opennebula.io>
Author: Guillermo Ramos <gramos@opennebula.io>
This commit adds support for sharing IPs among several VMs. When a AR is
marked as shared several VMs can request the same IP address either
through a NIC or NIC_ALIAS.
- Shared AR's cannot assign IP address automatically, an specific IP
needs to be requested.
- Shared AR's have some restrictions:
- Shared AR cannot use external IPAM
- Shared AR can only be of type IP4 or IP6_STATIC
- Shared AR cannot update IPAM or SHARED attribute
- Shared AR cannot make reservations
- Shared AR cannot hold by mac
- NICs / NIC_ALIAS using Shared IP will include SHARED=YES
co-authored-by: Jorge Miguel Lobo Escalona <jlobo@opennebula.io>
co-authored-by: MarioRobres <mrobres@opennebula.io>
* Remove unneeded breaks, support Enum as slices
* use cassert instead of GPR_ASSERT
* Use pkg-config for grpc dependencies
* Make Client destructor virtual
* Support for "empty" NUMA nodes. Each GB200 GPU requires eight dedicated NUMA
nodes for MIG support. Nodes cannot be shared with other resources (i.e.
memory, CPU or other GPUs)
* FEATURES. New features attributes:
- GIC = General Interrupt Controller, aarch64 architectures uses GIC
through APIC interface
- RAS = Report host memory errors to a guest using ACPI and guest external abort exceptions
- PCIHOLE64 defines MMIO space for GPU support, GB200 needs aprox 4T
(4294967296 KiB)
* New PCIe topology for dedicated devices. It also removes the PCI
switches. Each numa node includes a pci-expander-bus with 8 pci-root
ports.
* PCI. New attributes for PCI passthrough devices:
- ACPI_NODESET = <libvirt nodeset> NUMA nodes for ACPI
- ROOT = <dedicated|shared> to attach the PCI to its own expander bus
or the common one
- IOMMUFD= <Yes|No> enables iommufd in the hostdev driver to propagate DMA
mappings to the kernel for VM-assigned host device.
- IOMMU = <Yes|No> add a dedicated iommu device.
* IOMMU. New attribute to add a iommu device, includes:
- MODE = <single|device> Add a single iommu device or one for each PCI
passthrough device that request it
- MODEL = <smmuv3|intel|amd|virtio> for the iommu device
- OPTIONS = <whitespace-separated list of options> for the driver
element
* NUMA_NODE. New attribute, uses the node-set syntax with distance
e.g. 0:254,3-15:20,23:10
- DISTANCE to set cross NUMA node distance
co-author: Pavel Czerny <pczerny@opennebula.io>
This commit introduces a new API server based on the gRPC/Protobuf. The
API follow the design of the existing xml-rpc to ease the transition to
the new server and support the current state management engine.
Both API servers can be run in parallel.
Main changes:
- Decouple Generic and XMLRPC specific logic and add gRPC classes.
- Source code re-structure to include logic for each server
- New compilation options to generate gRPC stubs
- Client code for C++, Ruby, Python and Go
co-authored-by: Jan Orel <jorel@opennebula.io>
co-authored-by: Pavel Czerny <pczerny@opennebula.io>
co-authored-by: MarioRobres <mrobres@opennebula.io>
Setting the MACHINE default when parsing VM attributes make the default
available when assigning the CD-ROM prefix.
NOTE: This prvents to set MACHINE at host or cluster level.
- pf-440 VMs uses IDE
- virt and q35 uses SATA/iSCSI
- arm64/vmm_exec_kvm.conf defaults ARCH set to aarch64
IMPORTANT: DEV_PREFIX in CD-ROM Images is now ignored and cleared for
new images. Users can still force a CD-ROM bus/prefix by setting it in the
DISK/CONTEXT attribute.
This commit adds support for memory encryption. It includes:
* A new VM template attribute to set memory encryption
* A host probe to gather the memory extensions available (SEV,
SEV-ES...)
* When selected AUTOMATIC_REQUIREMENTS include memory encryption as a
requirement
* Domain XML generation has been updated to include memory encryption
attributes
* A kvm.conf attribute MEMORY_TUNE_OFFSET to add an additional memory
offset for encryption.
Author: MarioRobres <mrobres@opennebula.io>
Author: Daniel Clavijo Coca <dclavijo@opennebula.io>
When using q35 machines and NUMA pinning a specialized PCIe topology is
generated to resemble the one presented by the host. In this case PCI
devices can be mapped to the incorrect node, missmatching CPU+Mem and PCI pinning.
(cherry picked from commit 52ba320d0dd27f85131da7e681d98dbef748eaeb)
This commit adds support for remote execution of commands in a VM through qemu Guest Agent (GA). The feature includes:
* New API calls so create, cancel and retry command execution
* Command results are included in VM information
* Command line tool exposing this functionality
* Monitor probe to reap execution of commands
This commit adds support for PCI device quotas. It includes the following new attributes:
- PCI_NIC (and RUNNING_PCI_NIC), to account for PCI devices of TYPE = NIC
- PCI_DEV (and RUNNING_PCI_DEV), to account for generic PCI devices
This commits also includes:
- Simpler naming of the onegroup/oneuser quota names (RUNNING is now just label as RUN and SYSTEM_DISK_SIZE is now DISK SIZE)
- Consolidation of some duplicated logic in oned
- Golang bindings has been extended to include the new quota
- fsck update for the new quotas
- migrator for 7.2.0 release
This commit reverts the backup_incremental test. Now we check for not supported
configurations:
- qcow2 disks with snapshots
- raw disks in local/shared TM's
- lvm with lvm thin disabled
(cherry picked from commit 5c693d6741)
Add LAST_BRIDGE To the backup operation. OpenNebula oned selects and stores the bridge in the BACKUP metadata. The drivers can use the selected bridge to perform the different backup phases (on the same bridge)
This commits adds support for generating a NUMA PCIe hierarchy by adding
a pcie-expander-bus in each virtual node. When a PCI passthrough or
SR-IOV device is added is attached to the same virtual node as the
physical server. Changes include:
- Generate VM_* device parameters when the allocation is performed
- Generate CONTEXT PCIi_ADDRESS parameters at deployment time
- Refactor of the HostSharePCI to simplify argument passing.
The hierarchy created is as follows (example 2 NUMA nodes):
+-----------+
| |
| PCIe Root |
| |
+--+-----+--+
| ... |
+-----+ +-----+
NUMA node 0 | | NUMA node 1
+----+-----+ +----+-----+
| expander | | expander |
| bus | | bus |
+----+-----+ +----+-----+
| |
| ...
|
+------> port (0)
| ...
+------> port (3)
|
| +-----------+
| up | PCIe +-----> downstream port (0)
+----+ Switch | ...
| +-----> downstream port (8)
+-----------+
Two new attributes are supported for the Host/Cluster template:
- PCI_FILTER. Format is vendor:device:class with "*" as wild card. Example PCI_FILTER="10de:*,386e:0edc"
- PCI_SHORT_ADDRESS. Comma separated list of short PCI address. Example
PCI_SHORT_ADDRESS="c1:00.2,c1:00.3,01:00.5"
When any of these attributes are defined any PCI device returned by the monitor system is filtered using this attributes. If the device does not match PCI_FILTER and PCI_SHORT_ADDRESS it is discarded.
Signed-off-by: Valentyn Bohdan <vbohdan@opennebula.io>
Co-authored-by: Ruben S. Montero <rsmontero@opennebula.org>
Ruben S. Montero