Home
last modified time | relevance | path

Searched full:users (Results 1 – 16 of 16) sorted by relevance

/cloud-hypervisor/docs/
H A Dio_throttling.md6 feature, and highlights some internal implementations that can help users
35 example, to have a 1000 IOPS limit on a virtio-blk device, users should
40 actual rate limit users get can be as low as
43 (`cool_down_time`) to make sure the actual rate limit is close to users'
H A Dlogging.md6 - Users who want to debug issues with running their workloads in Cloud Hypervisor
22 Users should react to this error by checking their initial VM configuration.
H A Dreleases.md5 This document provides guidance to users, downstream maintainers and
84 … LTS release is supported for 18 months. This gives a 6 months window for users to move to the new…
H A Ddevice_model.md92 supported. Cloud Hypervisor supports multiple PCI segments, and users can
176 `cloud-hypervisor` users to plug a `vhost-user` based block device (e.g. SPDK)
198 backends. This enables `cloud-hypervisor` users to plug a `vhost-user` based
H A Dwindows.md163 - Click "Select Users" and add some user to the allow list
168 Add-LocalGroupMember -Group "Remote Desktop Users" -Member someuser
171 Administrators can always RDP, non administrator users have to be explicitly enabled.
H A Diommu.md53 device in order to provide a virtual IOMMU to its users. The reason being the
75 be `off` since we want to avoid the performance impact for most users who don't
H A Dbuilding.md9 We recommend users use the pre-built binaries that are mentioned in the README.md file in the root …
H A Dperformance_metrics.md4 binary for users to generate metrics data from their own
H A Dapi.md27 1. **The External API** This is the user facing API. Users and operators
211 form of a D-Bus signal to which users can subscribe. For more information,
216 This feature is not compiled into Cloud Hypervisor by default. Users who
/cloud-hypervisor/
H A Drelease-notes.md385 Now file-level locking is enforced for disk images, provided by users
392 Instead of returning a generic error `400` (e.g. `BadRequest`), users
394 pending VM resizing is not completed. This allows users to better handle
492 The `iommu_address_width` option has been added to `--platform` to allow users
713 * Josh Soref <2119212+jsoref@users.noreply.github.com>
807 Users now can throttle a group of block devices with the new
813 Users now have the option to pin virt-queue threads for block devices
837 Users now can set the vcpu affinity to a host CPU with index larger
884 segments on the guest, allowing users to have more 32-bit devices and
889 Named TAP devices now accepts IP configuration from users, such as IP
[all …]
/cloud-hypervisor/test_data/cloud-init/ubuntu/local/
H A Duser-data2 users:
/cloud-hypervisor/.github/workflows/
H A Ddco.yaml20 dco-check -e "49699333+dependabot[bot]@users.noreply.github.com"
/cloud-hypervisor/test_data/cloud-init/ubuntu/ci/
H A Duser-data2 users:
/cloud-hypervisor/vm-allocator/src/
H A Daddress.rs25 /// Use `AddressAllocator` whenever an address range needs to be allocated to different users.
/cloud-hypervisor/vmm/src/
H A Ddevice_manager.rs4767 // 1. Users will use direct kernel boot with device tree. in notify_power_button()
4768 // 2. Users will use ACPI+UEFI boot. in notify_power_button()
/cloud-hypervisor/tests/
H A Dintegration.rs3024 // Grant all users with write permission. in test_pci_multiple_segments()