---
title: Charmhub | Deploy OpenStack Hypervisor using Charmhub - The Open Operator Collection
description: Deploy the latest version of OpenStack Hypervisor on any cloud.
url: https://charmhub.io/openstack-hypervisor/configurations
---

# OpenStack Hypervisor

[OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

* [OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

Platform:

24.04

22.04

2024.1/stable 060d2288

```
juju deploy openstack-hypervisor --channel 2024.1/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

* [debug](https://charmhub.io/openstack-hypervisor/configurations#debug)
* [dns-servers](https://charmhub.io/openstack-hypervisor/configurations#dns-servers)
* [dpdk-control-plane-cores](https://charmhub.io/openstack-hypervisor/configurations#dpdk-control-plane-cores)
* [dpdk-datapath-cores](https://charmhub.io/openstack-hypervisor/configurations#dpdk-datapath-cores)
* [dpdk-driver](https://charmhub.io/openstack-hypervisor/configurations#dpdk-driver)
* [dpdk-enabled](https://charmhub.io/openstack-hypervisor/configurations#dpdk-enabled)
* [dpdk-memory](https://charmhub.io/openstack-hypervisor/configurations#dpdk-memory)
* [experimental-devmode](https://charmhub.io/openstack-hypervisor/configurations#experimental-devmode)
* [external-bridge](https://charmhub.io/openstack-hypervisor/configurations#external-bridge)
* [external-bridge-address](https://charmhub.io/openstack-hypervisor/configurations#external-bridge-address)
* [ovs-provider](https://charmhub.io/openstack-hypervisor/configurations#ovs-provider)
* [pci-device-specs](https://charmhub.io/openstack-hypervisor/configurations#pci-device-specs)
* [physnet-name](https://charmhub.io/openstack-hypervisor/configurations#physnet-name)
* [reserved-host-memory-mb-for-sev](https://charmhub.io/openstack-hypervisor/configurations#reserved-host-memory-mb-for-sev)
* [resume-on-boot](https://charmhub.io/openstack-hypervisor/configurations#resume-on-boot)
* [snap-channel](https://charmhub.io/openstack-hypervisor/configurations#snap-channel)
* [use-data-binding](https://charmhub.io/openstack-hypervisor/configurations#use-data-binding)
* [use-migration-binding](https://charmhub.io/openstack-hypervisor/configurations#use-migration-binding)

[Learn about configurations >](https://juju.is/docs/juju/configuration#heading--application-configuration)

* debug | boolean
* dns-servers | string

  Default: 8.8.8.8
* dpdk-control-plane-cores | int

  The number of cores allocated to OVS control plane processing. A dedicated
  list of cores will be obtained from the EPA service and passed to OVS
  through "other\_config:dpdk-lcore-mask.
* dpdk-datapath-cores | int

  The number of cores allocated to OVS datapath processing. A dedicated
  list of cores will be obtained from the EPA service and passed to OVS
  through "other\_config:pmd-cpu-mask".
* dpdk-driver | string

  Default: vfio-pci

  The driver used for DPDK physical ports.
* dpdk-enabled | boolean

  Enable OVS DPDK data path, handling packets in userspace. This provides
  improved performance compared to the standard OVS kernel data path.
  DPDK capable network interfaces are required.
* dpdk-memory | int

  The total amount of memory in MB to allocate from hugepages for OVS DPDK.
  The charm will distribute this memory across NUMA nodes based on the
  bridged network interfaces and then pass it to OVS using
  "other\_config:dpdk-socket-mem".
* experimental-devmode | boolean

  Temporary flag to enable devmode snap install. This is needed
  until openstack-hypervisor interfaces are all stable.
* external-bridge | string

  Default: br-ex
* external-bridge-address | string

  Default: 10.20.20.1/24
* ovs-provider | string

  Default: auto

  Specifies the OVS provider to use. Allowed values are:
  auto: Automatically detect whether microovn is present (default behaviour).
  microovn: Treat microovn as present (either already installed or will be
  deployed). The hypervisor will integrate with microovn for OVS.
  hypervisor: Use the OVS bundled with the openstack-hypervisor snap,
  ignoring any installed microovn snap.
* pci-device-specs | string

  A list of device specs used to set the `pci.device_spec` option in
  nova.conf, which allows PCI passthrough of specific devices to VMs.

  Example applications: GPU processing, SR-IOV networking, etc.

  NOTE: For PCI passthrough to work IOMMU must be enabled on the machine
  deployed to. This can be accomplished by setting kernel parameters on
  capable machines in MAAS, tagging them and using these tags as
  constraints in the model.

  Examples:

  + specify the PF address, exposing all the corresponding VFs:
    [{"physical\_network": "physnet1", "address": "0000:1b:00.0"}]
  + pick VFs individually:
    [{"physical\_network": "physnet2", "address": "0000:1b:10.0"},
    {"physical\_network": "physnet2", "address": "0000:1b:10.2}]
  + address wildcards:
    [{"physical\_network": "physnet1", "address": "*:1b:10.*"},
    {"physical\_network": "physnet1", "address": ":1b:}]
  + address regex patterns:
    [{"physical\_network": "physnet1",
    "address":
    {"domain": ".\*", "bus": "1b", "slot": "10", "function": "[0-4]"}}]
  + vendor and product id:
    [{"physical\_network": "physnet1", "vendor\_id": "8086", "product\_id": "1563"}]
* physnet-name | string

  Default: physnet1
* reserved-host-memory-mb-for-sev | string

  Memory to be reserved for host for SEV enabled compute
  hosts. This memory will be used for instances. The compute
  usage report deducts this memory from the available
  memory sent to the placement service.
* resume-on-boot | boolean

  Default: True

  Whether to resume the guest VMs when the host boots.
* snap-channel | string

  Default: 2024.1/edge
* use-data-binding | boolean
* use-migration-binding | boolean