----------------------------------------------------------------------------------------------
BIOS
"Intel Virtualization Technology"
VT-x or VT-d.
If there are any issues, have another look at the BIOS settings. My board (Asus Sabertooth X79) has a VT-x or "Intel Virtualization Technology" option, as well as a VT-d option. However, the VT-d section is under a different menu, you probably have to search for that. Normally VT-d would be disabled on most boards.
Intel's VT-d extensions are for IOMMU or directed I/O. An extension of the standard VT-x extensions, this allows a guest operating system to have direct access to the memory and other resources of many different types of devices
Under Xen, in order to check if VT-d works, just pass through a USB controller (use the pciback script in the Xen how-to) and check with
This means you likely have an Intel CPU with Trusted Execution Technology. Enabling this feature in your BIOS can have a negative impact on the availability of VT-d, which is a prerequisite of running HVM guests. Please disable TXT in the BIOS and you will be able to boot your HVM guests.
xl pci-list-assignable-devices
----------------------------------------------------------------------------------------------
Start with the Xen hypervisor and the basic toolset first:
[root@localhost ~]# dnf install libxc
[root@localhost ~]# dnf install xen xen-hypervisor xen-libs xen-runtime
//[root@localhost ~]# dnf remove xen xen-hypervisor xen-libs xen-runtime
//systemctl enable xend.service
//systemctl enable xendomains.service
[root@localhost ~]# systemctl enable xen-qemu-dom0-disk-backend.service
Get GRUB2 in order:
// grep -E --color "multiboot|module" /boot/grub2/i386-pc/command.lst
[root@localhost ~]# grep ^menuentry /boot/grub2/grub.cfg | cut -d "'" -f2
Fedora (4.6.4-301.fc24.x86_64) 24 (Workstation Edition)
Fedora (4.5.5-300.fc24.x86_64) 24 (Workstation Edition)
Fedora (0-rescue-5a7811782f504e58b061fcc2863b9246) 24 (Workstation Edition)
Fedora, with Xen hypervisor
[root@localhost ~]# grub2-set-default 'Fedora (4.6.4-301.fc24.x86_64) 24 (Workstation Edition)'
[root@localhost ~]# grub2-editenv list
saved_entry=Fedora, with Xen hypervisor
[root@localhost ~]# grub2-mkconfig -o /boot/grub2/grub.cfg
Now reboot. When the server restarts, verify that Xen is running:
[root@localhost ~]# xl dmesg | head
----------------------------------------------------------------------------------------------
As I’ve mentioned before, I enjoy using virt-manager to manage my VM’s. Let’s get started:
----------------------------------------------------------------------------------------------
[root@localhost ~]#
dnf install virt-manager dejavu* xorg-x11-xauth
dnf install libvirt-daemon-driver-network libvirt-daemon-driver-storage libvirt-daemon-xen
systemctl enable libvirtd.service
systemctl start libvirtd.service
systemctl status libvirtd.service
By this point, you have the Xen hypervisor running and you have VM management tools available from virt-manager and libvirt. Enjoy!
[root@localhost ~]#
xl dmesg | head
xl info
xl list
xl list
xl suspend guestname
xl resume guestname
libxl: error: libxl.c:116:libxl_ctx_alloc: cannot open libxc handle: No such file or directory
refer to: https://major.io/2014/02/27/installing-xen-on-fedora-20/
