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 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.
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.
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
239 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
241 :Type: system ioctl, vm ioctl
252 It is thus encouraged to use the vm ioctl to query for capabilities (available
253 with KVM_CAP_CHECK_EXTENSION_VM on the vm fd)
274 :Type: vm ioctl
286 :Type: vm ioctl
328 4.8 KVM_GET_DIRTY_LOG (vm ioctl)
333 :Type: vm ioctl
368 :Type: vm ioctl
617 Reads the values of MSR-based features that are available for the VM. This
792 :Type: vm ioctl
805 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
814 :Type: vm ioctl
883 :Type: vm ioctl
908 :Type: vm ioctl
933 :Type: vm ioctl
961 :Type: vm ioctl
994 :Type: vm ioctl
1198 :Type: vm ioctl
1220 :Type: vm ioctl
1235 :Type: vm ioctl
1256 VM. The maximum allowed slots can be queried using KVM_CAP_NR_MEMSLOTS.
1304 :Type: vm ioctl
1330 :Type: vm ioctl
1371 The vcpu ioctl should be used for vcpu-specific capabilities, the vm ioctl
1372 for vm-wide capabilities.
1449 :Type: vm ioctl
1473 :Type: vm ioctl
1664 :Type: vm ioctl
1677 using the device tree or other means from vm context.
1694 :Type: vm ioctl
1739 type, specifies that the devid field contains a valid value. The per-VM
1874 :Type: vm ioctl
1956 :Type: vm ioctl
1981 liobns will cause a vm exit and must be handled by userspace.
1995 :Type: vm ioctl
2613 :Type: vm ioctl
2632 KVM_MSI_VALID_DEVID: devid contains a valid value. The per-VM
2652 :Type: vm ioctl
2669 PIT timer interrupts may use a per-VM kernel thread for injection. If it
2685 :Type: vm ioctl
2711 :Type: vm ioctl
2726 :Type: vm ioctl
2801 :Type: vm ioctl
2840 :Type: vm ioctl
2877 :Type: vm ioctl, vcpu ioctl
2882 (vm ioctl) or per cpu (vcpu ioctl), depending on the interrupt type.
2906 KVM_S390_INT_VIRTIO (vm)
2909 KVM_S390_INT_SERVICE (vm)
2915 KVM_S390_INT_IO(ai,cssid,ssid,schid) (vm)
2920 KVM_S390_MCHK (vm, vcpu)
2932 :Type: vm ioctl
2986 :Type: vm ioctl
3006 in the current vm).
3023 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3025 :Type: device ioctl, vm ioctl, vcpu ioctl
3058 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3060 :Type: device ioctl, vm ioctl, vcpu ioctl
3167 :Type: vm ioctl
3223 :Type: vm ioctl
3272 :Type: vm ioctl
3472 :Type: vm ioctl
3504 :Type: vm ioctl
3676 :Type: vm
3702 :Type: vm ioctl
3735 :Type: vm ioctl
3762 :Type: vm ioctl
3796 :Type: vm ioctl
3833 :Type: vm ioctl
3869 :Type: vm ioctl
3924 :Type: vm ioctl
4035 :Type: vm ioctl
4055 to be enabled via the KVM_REQ_START_MIGRATION VM property.
4136 :Type: vm ioctl
4184 :Type: vm ioctl
4231 :Type: vm
4284 :Type: vm ioctl
4406 :Type: vm ioctl
4429 4.117 KVM_CLEAR_DIRTY_LOG (vm ioctl)
4434 :Type: vm ioctl
4582 :Type: vm ioctl
4616 :Type: vm ioctl
4679 :Type: vm ioctl
4697 Allocate memory and register the VM with the Ultravisor, thereby
4711 Deregister the VM from the Ultravisor and reclaim the memory that
4717 Pass the image header from VM memory to the Ultravisor in
4732 :Type: vm ioctl
5175 VM. Userspace is not obliged to honour this, and if it does honour
5176 this does not need to destroy the VM synchronously (ie it may call
5178 - KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
5183 to ignore the request, or to gather VM memory core dump and/or
5184 reset/shutdown of the VM.
5264 the instruction from the VM is overly complicated to live in the kernel.
5267 the VM. KVM assumed that if the guest accessed non-memslot memory, it was
5275 this capability at VM creation. Once this is done, these types of errors will
5298 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
5378 whether this is a per-vcpu or per-vm capability.
5533 :Target: vm
5627 you can find a list of capabilities and what their effect on the VM
5653 handling of an hcall is effective across the VM. On creation, an
5823 Enabling this capability on a VM provides userspace with a way to set
5830 subsequently queried for the VM. This capability is only supported by
5861 Enabling this capability on a VM provides userspace with a way to no
5876 or cmma is enabled, or the VM has the KVM_VM_S390_UCONTROL
5880 through hugetlbfs can be enabled for a VM. After the capability is
5885 While it is generally possible to create a huge page backed VM without
5886 this capability, the VM will not be able to run.
5907 virtualization, which provides a way for a guest VM to run guests that
5909 state). Enabling this capability on a VM depends on the CPU having
5920 emulated VM-exit when L1 intercepts a #PF exception that occurs in
5922 the emulated VM-exit when L1 intercepts a #DB exception that occurs in
5993 If present, this capability can be enabled for a VM, meaning that KVM
6001 :Target: VM
6006 target VM.
6011 the maximum halt time to specified on a per-VM basis, effectively overriding
6012 the module parameter for the target VM.
6018 :Target: VM
6096 KVM_VM_MIPS_* type must be passed to KVM_CREATE_VM to create a VM which
6099 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
6100 available, it means that the VM is using full hardware assisted virtualization
6101 capabilities of the hardware. This is useful to check after creating a VM with
6127 to KVM_CREATE_VM to create a VM which utilises it.
6129 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
6130 available, it means that the VM is using trap & emulate.
6141 kvm VM handle correspond roughly to the CP0_Config.AT register field, and should
6166 that if userspace creates a VM without an in-kernel interrupt controller, it
6168 which can generate virtual interrupts, presented to the VM.
6174 least one return to userspace before running the VM. This exit could either
6371 environment the control program is running in (e.g. Linux, z/VM...), and the
6384 writes to user space. It can be enabled on a VM level. If enabled, MSR
6395 may be rejected. With this capability exposed, KVM exports new VM ioctl