Microsoft Hyper-V

Windows Server type-1 hypervisor with generation 2 UEFI virtual machines and Secure Boot on by default.

Provider: default
Kind: Virtual machine
Category: Compute
Official docs: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v

Properties · 1 set by this component

property	type	values	required	kind default	this component
diskEncryption	boolean	—	no	—	inherited
failoverClustering · component property	boolean	—	no	false	inherited
generation · component property	enum	generation-1 \| generation-2	no	generation-2	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ false
memoryGib	integer	—	no	—	inherited
nestedVirtualization · component property	boolean	—	no	false	inherited
os	enum	linux \| windows \| aix \| ibm-i	no	linux	inherited
publicIp	boolean	—	no	—	inherited
secureBoot · component property	boolean	—	no	true	inherited
sizeVcpu	integer	—	no	—	inherited
zoneRedundant	boolean	—	no	—	inherited

Rules that apply · 1

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "hyper-v", component: "hyper-v" }

Other Virtual machine products · 60

Auto Scalingalibaba-auto-scalingalibabacloudvirtual-machine Elastic Compute Servicealibaba-ecsalibabacloudvirtual-machine Edge Node Servicealibaba-ensalibabacloudvirtual-machine Simple Application Serveralibaba-simple-application-serveralibabacloudvirtual-machine Amazon EC2aws-ec2awsvirtual-machine Amazon EC2 Auto Scalingaws-ec2-auto-scalingawsvirtual-machine Amazon EC2 Dedicated Hostsaws-ec2-dedicated-hostawsvirtual-machine Amazon Elastic VMware Serviceaws-evsawsvirtual-machine Amazon Lightsailaws-lightsailawsvirtual-machine AWS Nitro Enclavesaws-nitro-enclaveawsvirtual-machine Azure BareMetal Infrastructureazure-baremetal-infrastructureazurevirtual-machine Azure Compute Fleetazure-compute-fleetazurevirtual-machine Azure Dedicated Hostazure-dedicated-hostazurevirtual-machine Azure Data Science Virtual Machineazure-dsvmazurevirtual-machine Nutanix Cloud Clusters on Azureazure-nutanix-cloud-clustersazurevirtual-machine Azure Virtual Machinesazure-virtual-machineazurevirtual-machine Azure Virtual Machine Scale Setsazure-vm-scale-setazurevirtual-machine Azure VMware Solutionazure-vmware-solutionazurevirtual-machine Crusoe Cloud VMcrusoevirtual-machine Firecrackerfirecrackervirtual-machine KubeVirtkubevirtvirtual-machine Lambda Cloud instancelambda-labsvirtual-machine KVM with libvirtlibvirtvirtual-machine Nebius AI Cloud VMnebiusvirtual-machine Nutanix AHVnutanix-ahvvirtual-machine OpenStack Novaopenstack-novavirtual-machine oVirtovirtvirtual-machine Proxmox VEproxmoxvirtual-machine Runpod Podrunpodvirtual-machine Vast.ai instancevast-aivirtual-machine Generic virtual machinevirtual-machinevirtual-machine VMware vSpherevspherevirtual-machine XCP-ngxcp-ngvirtual-machine XenServerxenservervirtual-machine DigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpudigitaloceanvirtual-machine Dropletsdigitalocean-dropletdigitaloceanvirtual-machine Droplet Autoscale Pooldigitalocean-droplet-autoscaledigitaloceanvirtual-machine Bare Metal Solutiongoogle-bare-metal-solutiongcpvirtual-machine Cloud TPUgoogle-cloud-tpugcpvirtual-machine Compute Enginegoogle-compute-enginegcpvirtual-machine

and 20 more → Virtual machine page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Microsoft Hyper-V, the Windows Server type-1 hypervisor. Per "Should I create a generation 1 or 2 virtual
3# machine in Hyper-V?" Secure Boot is enabled by default for generation 2 virtual machines and a machine's
4# generation cannot be changed after it is created.
5schemaVersion: "1"
6type: "component"
7id: "hyper-v"
8kind: "virtual-machine"
9provider: "default"
10docs: "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v"
11defaults:
12  managed: false
13properties:
14  generation:
15    type: "enum"
16    values: ["generation-1", "generation-2"]
17    default: "generation-2"
18  secureBoot:
19    type: "boolean"
20    default: true
21  failoverClustering:
22    type: "boolean"
23    default: false
24  nestedVirtualization:
25    type: "boolean"
26    default: false

The same page as markdown, for an agent: /catalogue/components/hyper-v.md