Page MenuHomeFreeBSD

xen: miscellaneous fixes to the documentation
ClosedPublic

Authored by royger on Feb 7 2019, 3:22 PM.
Tags
None
Referenced Files
F161538468: D19106.id.diff
Sat, Jul 4, 3:54 PM
Unknown Object (File)
Fri, Jul 3, 1:58 PM
Unknown Object (File)
Sun, Jun 21, 2:31 AM
Unknown Object (File)
Mon, Jun 15, 3:52 PM
Unknown Object (File)
Mon, Jun 15, 3:52 PM
Unknown Object (File)
Sat, Jun 6, 3:05 AM
Unknown Object (File)
May 27 2026, 12:47 AM
Unknown Object (File)
May 25 2026, 5:45 AM
Subscribers
None

Details

Summary

Those include:

  • Clarify which FreeBSD versions support Xen 4.7 (PVHv1) and Xen 4.11 or greater (PVHv2),
  • Use onif for the Xen console.
  • Add a rune to load if_tap at boot.
  • Remove the restriction to use MMCFG PCI accesses for Xen >= 4.11.
  • Make the mention of /var/log/xen a tip so it's more visible.
  • Update the example guest creation to use FreeBSD 12.0 installer image.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Two suggestions, nothing major.

en_US.ISO8859-1/books/handbook/virtualization/chapter.xml
1512 โ†—(On Diff #53655)

The <tip> needs to have an empty line above it and the <para> inside should be indented. Run textproc/igor over your changed file to get some useful reports on what to change.

1579 โ†—(On Diff #53655)

I need to dig into whether we can use the &latest; or &latest2; variables to automatically reflect the latest FreeBSD releases here. That way, we don't need to remember to bump this every time a new release comes out. For now, you could wrap that release number in <replaceable>s to indicate that something else could be put in that position.

Thanks, all fixed :).

Apply requested fixes, run igor.

Looks good. Can you commit that directly or should I take care of it?

This revision is now accepted and ready to land.Feb 11 2019, 5:54 PM
This revision was automatically updated to reflect the committed changes.