|
version 1.52, 2014/12/26 23:46:22
|
version 1.53, 2014/12/26 23:58:18
|
|
Line 311 boot.)
|
Line 311 boot.)
|
| Configuring Xen |
Configuring Xen |
| --------------- |
--------------- |
| |
|
| |
Xen logs will be in /var/log/xen. |
| |
|
| Now, you have a system that will boot Xen and the dom0 kernel, and |
Now, you have a system that will boot Xen and the dom0 kernel, and |
| just run the dom0 kernel. There will be no domUs, and none can be |
just run the dom0 kernel. There will be no domUs, and none can be |
| started because you still have to configure the dom0 tools. The |
started because you still have to configure the dom0 tools. The |
|
Line 334 installed 4.1 or 4.2):
|
Line 336 installed 4.1 or 4.2):
|
| |
|
| For 4.1 (and thus xm; xl is believed not to work well), add to rc.conf: |
For 4.1 (and thus xm; xl is believed not to work well), add to rc.conf: |
| |
|
| xend=YES |
|
| xencommons=YES |
xencommons=YES |
| |
xend=YES |
| |
|
| TODO: Explain why if xm is preferred on 4.1, rc.d/xendomains has xl. |
TODO: Explain why if xm is preferred on 4.1, rc.d/xendomains has xl. |
| Or fix the package. |
Or fix the package. |
| |
|
| For 4.2 with xm, add to rc.conf |
For 4.2 with xm, add to rc.conf |
| |
|
| xend=YES |
|
| xencommons=YES |
xencommons=YES |
| |
xend=YES |
| |
|
| For 4.2 with xl (preferred), add to rc.conf: |
For 4.2 with xl (preferred), add to rc.conf: |
| |
|
| TODO: explain if there is a xend replacement |
|
| xencommons=YES |
xencommons=YES |
| |
TODO: explain if there is a xend replacement |
| |
|
| TODO: Recommend for/against xen-watchdog. |
TODO: Recommend for/against xen-watchdog. |
| |
|
| After you have configured the daemons and either started them or |
After you have configured the daemons and either started them (in the |
| rebooted, run the following (or use xl) to inspect Xen's boot |
order given) or rebooted, run the following (or use xl) to inspect |
| messages, available resources, and running domains: |
Xen's boot messages, available resources, and running domains: |
| |
|
| # xm dmesg |
# xm dmesg |
| [xen's boot info] |
[xen's boot info] |
|
Line 595 dom0. This is often appropriate when ru
|
Line 597 dom0. This is often appropriate when ru
|
| TODO: NAT appears to be configured by "vif = [ '' ]". |
TODO: NAT appears to be configured by "vif = [ '' ]". |
| |
|
| The MAC address specified is the one used for the interface in the new |
The MAC address specified is the one used for the interface in the new |
| domain. The interface in domain0 will use this address XOR'd with |
domain. The interface in dom0 will use this address XOR'd with |
| 00:00:00:01:00:00. Random MAC addresses are assigned if not given. |
00:00:00:01:00:00. Random MAC addresses are assigned if not given. |
| |
|
| Sizing domains |
Sizing domains |
|
Line 695 It is also desirable to add
|
Line 697 It is also desirable to add
|
| powerd=YES |
powerd=YES |
| |
|
| in rc.conf. This way, the domain will be properly shut down if |
in rc.conf. This way, the domain will be properly shut down if |
| `xm shutdown -R` or `xm shutdown -H` is used on the domain0. |
`xm shutdown -R` or `xm shutdown -H` is used on the dom0. |
| |
|
| Your domain should be now ready to work, enjoy. |
Your domain should be now ready to work, enjoy. |
| |
|
|
Line 753 See possibly outdated
|
Line 755 See possibly outdated
|
| PCI passthrough: Using PCI devices in guest domains |
PCI passthrough: Using PCI devices in guest domains |
| --------------------------------------------------- |
--------------------------------------------------- |
| |
|
| The domain0 can give other domains access to selected PCI |
The dom0 can give other domains access to selected PCI |
| devices. This can allow, for example, a non-privileged domain to have |
devices. This can allow, for example, a non-privileged domain to have |
| access to a physical network interface or disk controller. However, |
access to a physical network interface or disk controller. However, |
| keep in mind that giving a domain access to a PCI device most likely |
keep in mind that giving a domain access to a PCI device most likely |
| will give the domain read/write access to the whole physical memory, |
will give the domain read/write access to the whole physical memory, |
| as PCs don't have an IOMMU to restrict memory access to DMA-capable |
as PCs don't have an IOMMU to restrict memory access to DMA-capable |
| device. Also, it's not possible to export ISA devices to non-domain0 |
device. Also, it's not possible to export ISA devices to non-dom0 |
| domains, which means that the primary VGA adapter can't be exported. |
domains, which means that the primary VGA adapter can't be exported. |
| A guest domain trying to access the VGA registers will panic. |
A guest domain trying to access the VGA registers will panic. |
| |
|
| If the domain0 is NetBSD, it has to be running Xen 3.1, as support has |
If the dom0 is NetBSD, it has to be running Xen 3.1, as support has |
| not been ported to later versions at this time. |
not been ported to later versions at this time. |
| |
|
| For a PCI device to be exported to a domU, is has to be attached to |
For a PCI device to be exported to a domU, is has to be attached to |
![[BACK]](/icons/back.gif){kind=icon}
Return to howto.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc / ports / xen