variables:
# needed by libvirt-gitlab-executor
DISTRO: centos-stream-8
- # can be overriden in forks to set a different runner tag
+ # can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG: redhat-vm-host
tags:
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
variables:
# needed by libvirt-gitlab-executor
DISTRO: centos-stream-9
- # can be overriden in forks to set a different runner tag
+ # can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG: redhat-vm-host
tags:
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
variables:
# needed by libvirt-gitlab-executor
DISTRO: fedora-34
- # can be overriden in forks to set a different runner tag
+ # can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG: redhat-vm-host
tags:
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
variables:
# needed by libvirt-gitlab-executor
DISTRO: fedora-35
- # can be overriden in forks to set a different runner tag
+ # can be overridden in forks to set a different runner tag
LIBVIRT_CI_INTEGRATION_RUNNER_TAG: redhat-vm-host
tags:
- $LIBVIRT_CI_INTEGRATION_RUNNER_TAG
The ``<qemu:device>`` sub-element groups overrides for a device identified via
the ``alias`` attribute. The alias corresponds to the ``<alias name=''>``
property of a device. It's strongly recommended to use user-specified aliases
-for devices with overriden properties.
+for devices with overridden properties.
Sub element ``<qemu:frontend>`` encapsulates all overrides of properties for the
device frontend and overrides what libvirt formats via ``-device``.
:since:`Since 8.2.0`.
-The individual properties are overriden by a ``<qemu:property>`` element. The
+The individual properties are overridden by a ``<qemu:property>`` element. The
``name`` specifies the name of the property to override. In case when libvirt
doesn't configure the property a property with the name is added to the
commandline. The ``type`` attribute specifies a type of the argument used. The
to startup the VM.
*Note:* The libvirt project doesn't guarantee any form of compatibility and
-stability of devices with overriden properties. The domain is tainted when
+stability of devices with overridden properties. The domain is tainted when
such configuration is used.
Example:
QEMU_CAPS_DIRTYRATE_MODE , /* calc-dirty-rate accepts mode parameter */
/* 425 */
- QEMU_CAPS_BLOCKDEV_NBD_TLS_HOSTNAME, /* tls hostname can be overriden for NBD clients */
+ QEMU_CAPS_BLOCKDEV_NBD_TLS_HOSTNAME, /* tls hostname can be overridden for NBD clients */
QEMU_CAPS_MEMORY_BACKEND_PREALLOC_THREADS, /* -object memory-backend-*.prealloc-threads */
QEMU_CAPS_LAST /* this must always be the last item */
if (STREQ(prop->name, "id")) {
virReportError(VIR_ERR_XML_ERROR, "%s",
- _("property with name 'id' can't be overriden"));
+ _("property with name 'id' can't be overridden"));
return -1;
}