Lines Matching full:as

22 hosting, as well as traditional data center and desktop virtualization.  These
36 real-world use cases and treated as security bugs if this is the case.
43 the non-virtualization use case should meet the same security requirements as
63 virtual machine.  Isolation also includes resource limits such as throttling of
109 launch QEMU, such as libvirt.  They are also platform-specific so they are only
112 The fundamental isolation mechanism is that QEMU processes must run as
113 unprivileged users.  Sometimes it seems more convenient to launch QEMU as
116 unprivileged QEMU process access to host devices without running QEMU as root.
117 It is also possible to launch QEMU as a non-root user and configure UNIX groups
127   limits on key resources such as CPU time, memory, and I/O bandwidth.
154 their content to the guest as a virtual disk.
156 Unless QEMU is otherwise confined using technologies such as SELinux, AppArmor,
172 QEMU and as such should only be made accessible to a trusted management