Lines Matching refs: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 althought 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.
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.
160 On arm64, the physical address size for a VM (IPA Size limit) is limited
165 address used by the VM. The IPA_Bits is encoded in bits[7-0] of the
185 Creation of the VM will fail if the requested IPA size (whether it is
617 Reads the values of MSR-based features that are available for the VM. This
1256 VM. The maximum allowed slots can be queried using KVM_CAP_NR_MEMSLOTS.
1739 type, specifies that the devid field contains a valid value. The per-VM
2632 KVM_MSI_VALID_DEVID: devid contains a valid value. The per-VM
2669 PIT timer interrupts may use a per-VM kernel thread for injection. If it
4043 to be enabled via the KVM_REQ_START_MIGRATION VM property.
4691 Allocate memory and register the VM with the Ultravisor, thereby
4705 Deregister the VM from the Ultravisor and reclaim the memory that
4711 Pass the image header from VM memory to the Ultravisor in
5169 VM. Userspace is not obliged to honour this, and if it does honour
5170 this does not need to destroy the VM synchronously (ie it may call
5172 - KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
5177 to ignore the request, or to gather VM memory core dump and/or
5178 reset/shutdown of the VM.
5258 the instruction from the VM is overly complicated to live in the kernel.
5261 the VM. KVM assumed that if the guest accessed non-memslot memory, it was
5269 this capability at VM creation. Once this is done, these types of errors will
5292 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
5621 you can find a list of capabilities and what their effect on the VM
5647 handling of an hcall is effective across the VM. On creation, an
5817 Enabling this capability on a VM provides userspace with a way to set
5824 subsequently queried for the VM. This capability is only supported by
5855 Enabling this capability on a VM provides userspace with a way to no
5870 or cmma is enabled, or the VM has the KVM_VM_S390_UCONTROL
5874 through hugetlbfs can be enabled for a VM. After the capability is
5879 While it is generally possible to create a huge page backed VM without
5880 this capability, the VM will not be able to run.
5901 virtualization, which provides a way for a guest VM to run guests that
5903 state). Enabling this capability on a VM depends on the CPU having
5914 emulated VM-exit when L1 intercepts a #PF exception that occurs in
5916 the emulated VM-exit when L1 intercepts a #DB exception that occurs in
5987 If present, this capability can be enabled for a VM, meaning that KVM
5995 :Target: VM
6000 target VM.
6005 the maximum halt time to specified on a per-VM basis, effectively overriding
6006 the module parameter for the target VM.
6012 :Target: VM
6090 KVM_VM_MIPS_* type must be passed to KVM_CREATE_VM to create a VM which
6093 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
6094 available, it means that the VM is using full hardware assisted virtualization
6095 capabilities of the hardware. This is useful to check after creating a VM with
6121 to KVM_CREATE_VM to create a VM which utilises it.
6123 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
6124 available, it means that the VM is using trap & emulate.
6135 kvm VM handle correspond roughly to the CP0_Config.AT register field, and should
6160 that if userspace creates a VM without an in-kernel interrupt controller, it
6162 which can generate virtual interrupts, presented to the VM.
6168 least one return to userspace before running the VM. This exit could either
6365 environment the control program is running in (e.g. Linux, z/VM...), and the
6378 writes to user space. It can be enabled on a VM level. If enabled, MSR
6389 may be rejected. With this capability exposed, KVM exports new VM ioctl