Lines Matching full:guest

30 .Nd "run a guest operating system inside a virtual machine"
94 is a hypervisor that runs guest operating systems inside a
98 Parameters such as the number of virtual CPUs, amount of guest memory, and
102 is typically used with a boot ROM that can load the guest operating system.
104 If not using a boot ROM, the guest operating system must be loaded with
111 package provides a UEFI firmware that can be used to boot the guest;
114 package provides a U-Boot image that can be used to boot the guest.
117 runs until the guest operating system reboots or an unhandled hypervisor
122 The guest's local APIC is configured in xAPIC mode.
127 Include guest memory in core files.
129 Number of guest virtual CPUs
161 Destroy the VM on guest initiated power-off.
165 to exit when a guest issues an access to an I/O port that is not emulated.
184 Start a debug server that uses the GDB protocol to export guest state to a
261 Set the guest physical memory size.
283 Force the guest virtual CPU to exit when a PAUSE instruction is detected.
286 Pin guest's virtual CPU
290 Host CPUs and guest virtual CPUs are numbered starting from 0.
293 option is required for every guest vCPU to be pinned.
294 To map a 4 vCPU guest to host CPUs 12-15:
299 Resume a guest from a snapshot.
300 The guest memory contents are restored from
302 and the guest device and vCPU state are restored from the file
314 Wire guest memory.
367 in the guest's System Management BIOS System Information structure.
379 The guest's local APIC is configured in x2APIC mode.
385 Alphanumeric name of the guest.
401 This is usually configured at slot 0, and is required by most guest
421 to the guest in the form of simple char devices for simple IO
422 between the guest and host userspaces.
501 parameter can be specified to inform the guest about the largest MTU
527 The slirp backend can be used to provide a NATed network to the guest.
536 forwarded to the guest.
567 Disable emulation of guest trim requests via
574 The guest firmware may ignore or doesn't support this fwcfg file.
596 The guest firmware may ignore or doesn't support this fwcfg file.
628 allows unprivileged users to access the guest console, so ensure that
680 in the guest address space reserved for boot firmware.
684 is provided, that file is also mapped in the boot firmware guest
685 address space, and any modifications the guest makes will be saved
692 or ACPI tables to the guest firmware.
703 It currently reports only the CPU count to the guest firmware.
708 be passed to the guest.
710 many other things to the guest.
751 The guest firmware may ignore or doesn't support this fwcfg file.
755 Guest memory must be wired using the
803 to guest by VirtIO Input Interface.
871 An example of such a guest is
1053 The running guest can be interrupted by the debugger at any time
1060 guest may not work as expected due to timer interrupts firing while single
1086 If not using a boot ROM, the guest operating system must have been loaded with
1170 will write guest modifications to the given VARS file.
1171 Be sure to create a per-guest copy of the template VARS file from