Build dedicated VM host configurations for single-tenant compute isolation and compliance.
Last verified: May 2026
Build dedicated VM host configurations for single-tenant compute isolation and compliance.
Required Fields
compartmentIddisplayNameavailabilityDomaindedicatedVmHostShapeOutput will appear here...The builder constructs Dedicated VM Host configurations with: host shape (DVH.Standard.E5 with specific OCPU + memory total), display name + compartment, fault domain placement, and instance shapes that can be launched on the host (validated against host capacity). Output is generated as oci compute dedicated-vm-host commands and Terraform oci_core_dedicated_vm_host resources, plus the recommended packing pattern showing how many of each VM shape fits on the host.
OCI Dedicated VM Hosts provide single-tenant physical servers where only your Compute instances run, offering hardware isolation for compliance, licensing, and performance requirements. Dedicated hosts are essential for workloads governed by regulations requiring physical separation or for bring-your-own-license (BYOL) scenarios with per-socket or per-core licensing. This builder helps you configure Dedicated VM Hosts with shape selection, fault domain placement, and instance packing strategies.
Your team is migrating Oracle Database workloads from on-prem to OCI. The Oracle license is per-core BYOL on dedicated hardware. The builder generates: 2 Dedicated VM Hosts (DVH.Standard.E5 with 64 OCPUs each), distributed across 2 fault domains. Pack 4 large database VMs (16 OCPU each) on each host. Total cost: ~$3K/month for the dedicated hosts vs $7K/month for equivalent capacity on standard VMs (because BYOL eliminates ~$5K/month in license-included pricing). Net savings: $4K/month while satisfying Oracle's licensing requirements.
Dedicated VM Hosts are a niche feature — only justified by HARD compliance, BYOL licensing, or noisy-neighbor concerns. The cost premium is significant and instance density rarely justifies it for general workloads. Most teams over-think isolation and end up paying for dedicated hosts when standard VMs would suffice.
BYOL Oracle Database licensing is the most-common dedicated host use case. Oracle's per-core licensing model traditionally required dedicated hardware; Dedicated VM Hosts on OCI satisfy this with much better economics than self-managed bare metal in your DC.
Pack instances on dedicated hosts to maximize utilization. The cost is fixed per host regardless of instance count up to capacity. A dedicated host running 1 small VM costs the same as one running 30 small VMs. Plan instance shapes to fit cleanly on the host.
Dedicated VM Hosts give you a physical server on which you run multiple VM instances — you manage the instances individually but the host guarantees hardware isolation. Bare metal instances give you direct access to the physical hardware without a hypervisor, providing maximum performance for workloads that need hardware-level access (DPDK, SR-IOV, real-time computing). Choose dedicated hosts for multi-VM isolation and licensing compliance; choose bare metal for single-workload, hypervisor-free performance.
You pay for the Dedicated VM Host shape on a per-hour basis regardless of how many VMs you place on it. The host has a fixed number of OCPUs and memory, and you can launch instances up to that capacity. This model is cost-effective when you fully utilize the host. If you only place a few small instances, dedicated hosts can be more expensive per OCPU than standard instances. Plan your instance packing to maximize utilization.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.