The Xen Project hypervisor is an open-source type-1 or baremetal hypervisor,
which makes it possible to run many instances of an operating system or indeed
different operating systems in parallel on a single machine (or host). The Xen
Project hypervisor is the only type-1 hypervisor that is available as open
source. It is used as the basis for a number of different commercial and open
source applications, such as: server virtualization, Infrastructure as a Service
(IaaS), desktop virtualization, security applications, embedded and hardware
appliances
WWW: http://www.xenproject.org/
Please add the following entries in order to boot the xen kernel
In /etc/sysctl.conf:
vm.max_wired=-1
In /etc/ttys:
xc0 "/usr/libexec/getty Pc" xterm on secure
In /boot/loader.conf for a dom0 with 2G memory and 4 vcpus:
hw.pci.mcfg=0
xen_kernel="/boot/xen"
xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0=pvh com1=115200,8n1 guest_loglvl=all loglvl=all"
Add to the above xen_cmdline in order to activate the serial console:
console=com1
In /boot/menu.rc.local:
try-include /boot/xen.4th
emulators/xen-kernel411 & sysutils/xen-tools411: drop version number from port
Actually perform the rename of the directories missing in r494039.
Sponsored by: Citrix Systems R&D
Reviewed by: bapt
Differential revision: https://reviews.freebsd.org/D19284
emulators/xen-kernel411 & sysutils/xen-tools411: drop version number from port
I don't have the bandwidth to maintain multiple version of Xen, and
going forward all newer version of Xen should work on FreeBSD without
issues.
Sponsored by: Citrix Systems R&D
Reviewed by: bapt
Differential revision: https://reviews.freebsd.org/D19284
xen-kernel411: use an explicit build-only target in do-build
The xen target used previously will also call the install target,
leaving unwanted stuff in the staging directory.
Sponsored by: Citrix Systems R&D
