原因: This Note is not very meaningful without a link to a bug report.(在 Talk:Xen 中讨论) disable-werror -enable-targets=x86_64-pep ![]() Using the archway of doing things you would use the Arch Build System and add -enable-targets=x86_64-pep to the build options of the binutils PKGBUILD file: It's possible to boot the Xen hypervisor though the bare UEFI system on a modern computer but requires you to first recompile binutils to add support for x86_64-pep emulation. Install the xen-docs AUR package from the Arch User Repository for the man pages and documentation. The multilib repository needs to be enabled and the multilib-devel 包组 package group installed to compile Xen. Both packages provide the Xen hypervisor, current xl interface and all configuration and support files, including systemd services. To install the Xen hypervisor install either the current stable xen AUR or the bleeding edge unstable xen-git AUR packages available in the Arch User Repository. ![]() Modification of the bootloader to boot the Xen hypervisor.The following configuration steps are required to convert a standard installation into a working dom0 running on top of the Xen hypervisor: If you are building a new host from scratch, see the Installation guide for instructions on installing Arch Linux. This installation can be a minimal install with only the base package and does not require a Desktop environment or even Xorg. Before attempting to install the Xen hypervisor, the host machine should have a fully operational and up-to-date install of Arch Linux. The Xen hypervisor relies on a full install of the base operating system. In order to use PCI passthrough, the CPU must support IOMMU/VT-d. The Xen hypervisor also supports PCI passthrough where PCI devices can be passed directly to the domU even in the absence of dom0 support for the device. If such an option exists and is disabled, then enable it, boot the system and repeat the above command. If you believe the CPU supports one of these features you should access the host system's BIOS configuration menu during the boot process and look if options related to virtualization support have been disabled. If the above command does not produce output, then hardware virtualization support is unavailable and your hardware is unable to run HVM domU (or you are already running the Xen hypervisor). $ grep -E "(vmx|svm)" -color=always /proc/cpuinfo In order to verify this, run the following command when the Xen hypervisor is not running: To run HVM domU, the physical hardware must have either Intel VT-x or AMD-V (SVM) virtualization support. The Xen hypervisor requires kernel level support which is included in recent Linux kernels and is built into the linux 包 and linux-lts 包 Arch kernel packages. ![]() Xen supports both paravirtualized (PV) and hardware virtualized (HVM) domU. Once the dom0 has started, one or more domU (short for user domains, sometimes called VMs or guests) can be started and controlled from the dom0. ![]() Once the hypervisor is loaded, it starts the dom0 (short for "domain 0", sometimes called the host or privileged domain) which in our case runs Arch Linux. The hypervisor is started by the boot loader of the computer it is installed on. The Xen hypervisor is a thin layer of software which emulates a computer architecture allowing multiple operating systems to run simultaneously. 警告: Do not run other virtualization software such as VirtualBox when running Xen hypervisor, it might hang your system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |