We go into a little more detail on memory oversubscription in Chapter This is a unique name for the domain. This is one of the few non-optional directives. Every domain needs a name. These two arguments are used by the kernel when booting via NFS. We describe setting up an NFS root in Chapter 4. This option is deprecated, but you may see it referenced in other documentation.
It specifies the number of virtual NICs allocated to the domain. In practice, we always just rely on the number of vif stanzas to implicitly declare the NICs. Allowed values are:. Similarly, these two items control how the domain will react to xend exiting. Because xend sometimes needs to be restarted, and we prefer to minimize disruption of the domUs, we leave these at the default: ignore. This adds a PCI device to the domain using the given parameters, which can be found with lspci in the dom0.
We give an example of PCI forwarding in Chapter The ramdisk option functions like the initrd line in GRUB; it specifies an initial ramdisk, which usually contains drivers and scripts used to access hardware required to mount the root filesystem. We go into more detail on that subject in Chapter This specifies the root device for the domain. We usually specify the root device on the extra line.
Set this option to true to enable a framebuffer console over SDL. Again, we prefer the vfb syntax. This is the domain shadow memory in MB. PV domains will default to none. Xen uses shadow memory to keep copies of domain-specific page tables. We go into more detail on the role of page table shadows in Chapter These are active VCPUs. This specifies the number of virtual CPUs to report to the domain. For performance reasons, we strongly recommend that this be equal to or fewer than the number of physical CPU cores that the domain has available.
Valid options for the vfb line are: vnclisten, vncunused, vncdisplay, display, videoram, xauthority, type, vncpasswd, opengl , and keymap. We discuss more details about virtual framebuffers in Chapter 14 and a bit in Chapter The videoram option specifies the maximum amount of memory that a PV domain may use for its frame buffer. Each vif specification can include many options, including bridge, ip, and mac.
For more information on these, see Chapter 5. Allowable options in the vif line are backend, bridge, ip, mac, script, type, vifname, rate, model, accel, policy , and label.
Set vnc to 1 to enable the VNC console. The repository has numerous topic branches to track individual lines of development, and a couple of roll-up branches which contain everything merged together for easy compilation and running.
All active git branches require at least Xen 4. The primary version control system used for Linux kernel development is git. For more information on git see:.
If you are using xentip's tree then you most probably want to use the linux-next branch:. Configure as normal; you can start with your current. PAE is not needed for 64 bit kernels. For more current Xen related config options check the example. After having downloaded and configured the kernel source as above building the kernel is as simple as:.
The kernel contains several makefile targets which can create packages in various formats. These packages include a baseline level of integration with the relevant distros although not likely to be as good as the distros own packages they are good enough.
For example, "phy" does not support formats other than "raw". Normally this option should not be specified, in which case libxl will automatically determine the most suitable backend. The bug occurs due to a mismatch between the backend-visible lifetime of pages used for the Xen PV network protocol and that expected by the backend kernel's networking subsystem.
This can cause crashes when using certain backends with certain underlying storage. However, this workaround has performance and scaling implications, and it is only necessary if the underlying device is a network filesystem. If the underlying device is not, then it is good to disable it; that is what this option is for. This option simply requests that the workaround be disabled. However, not all backends versions which use the workaround understand this option, so this is on a best effort basis.
Otherwise specifying it is safe and can give better performances. The real benefit of this option is to be able to force it off rather than on. It can be used to disable "hole punching" for file based backends which were intentionally created non-sparse to avoid fragmentation of the file. They may change incompatibly in future versions of Xen.
Secondary port. We will run a nbd server on secondary host, and the nbd server will listen this port. Deprecated forms are acceptable and are intended work compatibly with xend and xl from xen 4. In future they may print a warning.
0コメント