Lines Matching full:vm
17 - VM ioctls: These query and set attributes that affect an entire virtual
18 machine, for example memory layout. In addition a VM ioctl is used to
21 VM ioctls must be issued from the same process (address space) that was
22 used to create the VM.
36 was used to create the VM.
44 handle will create a VM file descriptor which can be used to issue VM
45 ioctls. A KVM_CREATE_VCPU or KVM_CREATE_DEVICE ioctl on a VM fd will
58 It is important to note that although VM ioctls may only be issued from
59 the process that created the VM, a VM's lifecycle is associated with its
60 file descriptor, not its creator (process). In other words, the VM and
62 until the last reference to the VM's file descriptor has been released.
63 For example, if fork() is issued after ioctl(KVM_CREATE_VM), the VM will
65 put their references to the VM's file descriptor.
67 Because a VM's resources are not freed until the last reference to its
68 file descriptor is released, creating additional references to a VM
71 by and on behalf of the VM's process may not be freed/unaccounted when
72 the VM is shut down.
111 system, vm, or vcpu.
145 :Returns: a VM fd that can be used to control the new virtual machine.
147 The new VM has no virtual cpus and no memory.
153 Supported X86 VM types can be queried via KVM_CAP_VM_TYPES.
173 On arm64, the physical address size for a VM (IPA Size limit) is limited
178 address used by the VM. The IPA_Bits is encoded in bits[7-0] of the
198 Creation of the VM will fail if the requested IPA size (whether it is
252 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
254 :Type: system ioctl, vm ioctl
265 It is thus encouraged to use the vm ioctl to query for capabilities (available
266 with KVM_CAP_CHECK_EXTENSION_VM on the vm fd)
299 :Type: vm ioctl
341 4.8 KVM_GET_DIRTY_LOG (vm ioctl)
346 :Type: vm ioctl
641 Reads the values of MSR-based features that are available for the VM. This
839 :Type: vm ioctl
852 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
861 :Type: vm ioctl
930 :Type: vm ioctl
955 :Type: vm ioctl
980 :Type: vm ioctl
1026 :Type: vm ioctl
1076 :Type: vm ioctl
1301 :Type: vm ioctl
1323 :Type: vm ioctl
1338 :Type: vm ioctl
1359 VM. The maximum allowed slots can be queried using KVM_CAP_NR_MEMSLOTS.
1409 Returns -EINVAL if the VM has the KVM_VM_S390_UCONTROL flag set.
1410 Returns -EINVAL if called on a protected VM.
1417 :Type: vm ioctl
1443 :Type: vm ioctl
1484 The vcpu ioctl should be used for vcpu-specific capabilities, the vm ioctl
1485 for vm-wide capabilities.
1598 :Type: vm ioctl
1622 :Type: vm ioctl
1671 when invoked on the vm file descriptor. The size value returned by
1828 :Type: vm ioctl
1841 using the device tree or other means from vm context.
1858 :Type: vm ioctl
1905 type, specifies that the devid field contains a valid value. The per-VM
1972 :Type: vcpu ioctl / vm ioctl
1980 be used as a vm ioctl to set the initial tsc frequency of subsequently
1988 :Type: vcpu ioctl / vm ioctl
2057 :Type: vm ioctl
2139 :Type: vm ioctl
2164 liobns will cause a vm exit and must be handled by userspace.
2178 :Type: vm ioctl
2699 sets all the supported bits during VM initialization. The userspace can
2704 Note: These registers are immutable once any of the vCPUs of the VM has
2972 :Type: vm ioctl
2991 KVM_MSI_VALID_DEVID: devid contains a valid value. The per-VM
3011 :Type: vm ioctl
3028 PIT timer interrupts may use a per-VM kernel thread for injection. If it
3044 :Type: vm ioctl
3072 :Type: vm ioctl
3087 :Type: vm ioctl
3162 :Type: vm ioctl
3201 :Type: vm ioctl
3238 :Type: vm ioctl, vcpu ioctl
3243 (vm ioctl) or per cpu (vcpu ioctl), depending on the interrupt type.
3267 KVM_S390_INT_VIRTIO (vm)
3270 KVM_S390_INT_SERVICE (vm)
3276 KVM_S390_INT_IO(ai,cssid,ssid,schid) (vm)
3281 KVM_S390_MCHK (vm, vcpu)
3293 :Type: vm ioctl
3348 :Type: vm ioctl
3368 in the current vm).
3385 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3389 :Type: device ioctl, vm ioctl, vcpu ioctl
3422 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3425 :Type: device ioctl, vm ioctl, vcpu ioctl
3546 :Type: vm ioctl
3602 :Type: vm ioctl
3651 :Type: vm ioctl
3807 :Type: vm ioctl, vcpu ioctl
3813 Read or write data from/to the VM's memory.
3906 Absolute accesses are permitted for the VM ioctl if KVM_CAP_S390_MEM_OP_EXTENSION
3930 occurred. The cmpxchg op is permitted for the VM ioctl if
3952 :Type: vm ioctl
3984 :Type: vm ioctl
4156 :Type: vm ioctl
4241 part of VM-Enter/VM-Exit emulation.
4244 of VM-Enter/VM-Exit emulation. If an MSR access is denied on VM-Enter, KVM
4245 synthesizes a consistency check VM-Exit(EXIT_REASON_MSR_LOAD_FAIL). If an
4246 MSR access is denied on VM-Exit, KVM synthesizes a VM-Abort. In short, KVM
4248 the VM-Enter/VM-Exit MSR list. It is platform owner's responsibility to
4269 :Type: vm ioctl
4302 :Type: vm ioctl
4329 :Type: vm ioctl
4363 :Type: vm ioctl
4400 :Type: vm ioctl
4454 :Type: vm ioctl
4565 :Type: vm ioctl
4585 to be enabled via the KVM_REQ_START_MIGRATION VM property.
4666 :Type: vm ioctl
4714 :Type: vm ioctl
4761 :Type: vm
4814 :Type: vm ioctl
4936 :Type: vm ioctl
4959 4.117 KVM_CLEAR_DIRTY_LOG (vm ioctl)
4964 :Type: vm ioctl
5119 :Type: vm ioctl
5212 Via this API, KVM userspace can also control the behavior of the VM's fixed
5235 :Type: vm ioctl
5298 :Type: vm ioctl
5324 Allocate memory and register the VM with the Ultravisor, thereby
5337 Deregister the VM from the Ultravisor and reclaim the memory that had
5340 previous protected VM had been prepared for asynchronous teardown with
5343 together with the current protected VM.
5346 Pass the image header from VM memory to the Ultravisor in
5382 struct kvm_s390_pv_info_vm vm;
5425 protected VM.
5439 Initializes the dump process of a protected VM. If this call does
5469 Prepare the current protected VM for asynchronous teardown. Most
5470 resources used by the current protected VM will be set aside for a
5471 subsequent asynchronous teardown. The current protected VM will then
5473 one protected VM prepared for asynchronous teardown at any time. If
5474 a protected VM had already been prepared for teardown without
5486 Tear down the protected VM previously prepared for teardown with
5501 :Type: vm ioctl
5543 Sets the ABI mode of the VM to 32-bit or 64-bit (long mode). This
5544 determines the layout of the shared_info page exposed to the VM.
5624 :Type: vm ioctl
5628 Allows Xen VM attributes to be read. For the structure and types,
5671 As with the shared_info page for the VM, the corresponding page may be
5766 :Type: vm ioctl
5850 :Type: vm ioctl, vcpu ioctl
5861 The returned file descriptor can be used to read VM/vCPU statistics data in
6067 when invoked on the vm file descriptor. The size value returned by
6080 :Type: vm ioctl
6112 of a protected VM.
6125 :Type: vm ioctl
6154 KVM_S390_ZPCIOP_REG_AEN is used to register the VM for adapter event
6156 events directly to the vm, with KVM providing a backup delivery mechanism;
6172 :Type: vm ioctl
6176 This capability indicates that userspace is able to apply a single VM-wide
6191 for this VM.
6212 :Type: vm ioctl
6260 :Type: vm ioctl
6269 must point at a file created via KVM_CREATE_GUEST_MEMFD on the current VM, and
6296 state. At VM creation time, all memory is shared, i.e. the PRIVATE attribute
6303 Returns -EINVAL if the VM has the KVM_VM_S390_UCONTROL flag set.
6304 Returns -EINVAL if called on a protected VM.
6311 :Type: vm ioctl
6331 executed on a VM, KVM_CAP_MEMORY_ATTRIBUTES precisely returns the attributes
6332 supported by that VM. If executed at system scope, KVM_CAP_MEMORY_ATTRIBUTES
6347 :Type: vm ioctl
6423 In the case of confidential VM types where there is an initial set up of
6511 /* x86, set if bus lock detected in VM */
6652 filter. See the Documentation/virt/kvm/devices/vm.rst
6832 VM. Userspace is not obliged to honour this, and if it does honour
6833 this does not need to destroy the VM synchronously (ie it may call
6835 - KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
6840 to ignore the request, or to gather VM memory core dump and/or
6841 reset/shutdown of the VM.
6848 the VM.
6869 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
6881 - Honor the guest request to suspend the VM. Userspace can request
6888 - Deny the guest request to suspend the VM. See ARM DEN0022D.b 5.19.2
6969 the instruction from the VM is overly complicated to live in the kernel.
6972 the VM. KVM assumed that if the guest accessed non-memslot memory, it was
6980 this capability at VM creation. Once this is done, these types of errors will
6995 queried outside of a protected VM context, the feature will not be
6996 exposed if queried on a protected VM file descriptor.
7009 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
7120 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
7121 enabled, a VM exit generated if no event window occurs in VM non-root mode
7129 - KVM_NOTIFY_CONTEXT_INVALID -- the VM context is corrupted and not valid
7130 in VMCS. It would run into unknown result if resume the target VM.
7180 whether this is a per-vcpu or per-vm capability.
7335 :Target: vm
7429 you can find a list of capabilities and what their effect on the VM
7455 handling of an hcall is effective across the VM. On creation, an
7625 Enabling this capability on a VM provides userspace with a way to set
7632 subsequently queried for the VM. This capability is only supported by
7663 Enabling this capability on a VM provides userspace with a way to no
7678 or cmma is enabled, or the VM has the KVM_VM_S390_UCONTROL
7682 through hugetlbfs can be enabled for a VM. After the capability is
7687 While it is generally possible to create a huge page backed VM without
7688 this capability, the VM will not be able to run.
7709 virtualization, which provides a way for a guest VM to run guests that
7711 state). Enabling this capability on a VM depends on the CPU having
7722 emulated VM-exit when L1 intercepts a #PF exception that occurs in
7724 the emulated VM-exit when L1 intercepts a #DB exception that occurs in
7796 If present, this capability can be enabled for a VM, meaning that KVM
7804 :Target: VM
7809 maximum halt-polling time for all vCPUs in the target VM. This capability can
7820 :Target: VM
7852 :Target: VM
7861 Enabling this capability on a VM provides userspace with a way to select a
7866 This capability allows userspace to force VM exits on bus locks detected in the
7872 If KVM_BUS_LOCK_DETECTION_OFF is set, KVM doesn't force guest bus locks to VM
7877 bus locks in the guest trigger a VM exit, and KVM exits to userspace for all
7878 such VM exits, e.g. to allow userspace to throttle the offending guest and/or
7902 Type: vm
7903 Parameters: args[0] is the fd of the source vm
7906 This capability enables userspace to copy encryption context from the vm
7907 indicated by the fd to the vm this is called on.
7918 :Target: VM
7923 KVM_CAP_SGX_ATTRIBUTE enables a userspace VMM to grant a VM access to one or
7932 by running an enclave in a VM, KVM prevents access to privileged attributes by
7942 :Type: vm
7988 tags as appropriate if the VM is migrated.
8002 :Type: vm
8003 :Parameters: args[0] is the fd of the source vm
8006 This capability enables userspace to migrate the encryption context from the VM
8007 indicated by the fd to the VM this is called on.
8017 :Type: vm
8032 :Type: vm
8105 VM type isn't KVM_X86_DEFAULT_VM), KVM only
8116 :Target: VM
8117 :Parameters: args[0] - maximum APIC ID value set for current VM
8122 assigned for current VM session prior to the creation of vCPUs, saving
8137 :Target: VM
8140 VM exit is unsupported.
8148 This capability allows userspace to configure the notify VM exit on/off
8149 in per-VM scope during VM creation. Notify VM exit is disabled by default.
8152 a VM exit if no event window occurs in VM non-root mode for a specified of
8155 If KVM_X86_NOTIFY_VMEXIT_USER is set in args[0], upon notify VM exits happen,
8169 kvm_run.memory_fault if KVM cannot resolve a guest page fault VM-Exit, e.g. if
8187 :Target: VM
8193 This capability sets the VM's APIC bus clock frequency, used by KVM's in-kernel
8274 KVM_VM_MIPS_* type must be passed to KVM_CREATE_VM to create a VM which
8277 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8278 available, it means that the VM is using full hardware assisted virtualization
8279 capabilities of the hardware. This is useful to check after creating a VM with
8305 to KVM_CREATE_VM to create a VM which utilises it.
8307 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8308 available, it means that the VM is using trap & emulate.
8319 kvm VM handle correspond roughly to the CP0_Config.AT register field, and should
8344 that if userspace creates a VM without an in-kernel interrupt controller, it
8346 which can generate virtual interrupts, presented to the VM.
8352 least one return to userspace before running the VM. This exit could either
8549 environment the control program is running in (e.g. Linux, z/VM...), and the
8562 writes to user space. It can be enabled on a VM level. If enabled, MSR
8573 may be rejected. With this capability exposed, KVM exports new VM ioctl
8620 ring buffer, the less likely the ring is full and the VM is forced to
8660 calls the VM ioctl KVM_RESET_DIRTY_RINGS to notify the kernel about
8784 :Type: vm
8830 :Type: vm
8849 :Type: vm
8856 PMU virtualization capabilities that can be adjusted on a VM.
8859 PMU virtualization capabilities to be applied to the VM. This can
8860 only be invoked on a VM prior to the creation of VCPUs.
8863 this capability will disable PMU virtualization for that VM. Usermode
8871 :Type: vm
8881 :Type: vm
8894 :Type: vm
8911 :Type: vm
8923 on vm fd, KVM_S390_VM_CPU_TOPOLOGY.
8936 :Type: vm
8965 This capability returns a bitmap of support VM types. The 1-setting of bit @n
8966 means the VM type with value @n is supported. Possible values of @n are::