General ⇒ Table of Contents Question

[xen_latex]

I have a document that has been around for a few years and I did some minor text changes and I am now not able to get the Table of Contents to appear in the final pdf document. When I run the "latex doc.tex" command I create several files including the doc.toc. When I review the doc.toc file it looks correct as it has all the chapters, etc. correctly listed.

Here is the Table of Contents content that I have in my main file:

% TABLE OF CONTENTS
\pagestyle{plain}
\pagenumbering{roman}
{ \parskip 0pt plus 1pt
\tableofcontents }
\cleardoublepage

Any thoughts would be greatly appreciated. Thanks.

[Stefan Kottwitz]

Hi,

did you compile two times? Because the first time the toc file will be created and this will be read and printed during the second run.

Stefan

[xen_latex]

Yes, I do the "latex doc.tex" first and then I run a Makefile which does the 2nd pass. The document created is perfect in all ways except it will not add the Table of Contents. I can post any files that you need if that would help. Appreciate the assistance.

[Stefan Kottwitz]

Do you get no table of contents at all or do you get the title "Contents" but no entries?
If you would post doc.log and doc.toc I would have a look at these.

Stefan

[xen_latex]

I got the word "Contents" and nothing underneath. Here are the files...

user.log

(28.21 KiB) Downloaded 286 times

[xen_latex]

.toc file:

\contentsline {chapter}{\numberline {1}Introduction}{1}
\contentsline {section}{\numberline {1.1}Usage Scenarios}{1}
\contentsline {section}{\numberline {1.2}Operating System Support}{2}
\contentsline {section}{\numberline {1.3}Hardware Support}{2}
\contentsline {section}{\numberline {1.4}Structure of a Xen-Based System}{3}
\contentsline {section}{\numberline {1.5}History}{3}
\contentsline {section}{\numberline {1.6}What's New}{4}
\contentsline {part}{I\hspace {1em}Installation}{5}
\contentsline {chapter}{\numberline {2}Basic Installation}{7}
\contentsline {section}{\numberline {2.1}Prerequisites}{7}
\contentsline {section}{\numberline {2.2}Installing from Binary Tarball}{8}
\contentsline {section}{\numberline {2.3}Installing from RPMs}{8}
\contentsline {section}{\numberline {2.4}Installing from Source}{8}
\contentsline {subsection}{\numberline {2.4.1}Obtaining the Source}{8}
\contentsline {subsection}{\numberline {2.4.2}Building from Source}{9}
\contentsline {subsection}{\numberline {2.4.3}Custom Kernels}{9}
\contentsline {subsection}{\numberline {2.4.4}Installing Generated Binaries}{10}
\contentsline {section}{\numberline {2.5}Configuration}{10}
\contentsline {subsection}{\numberline {2.5.1}GRUB Configuration}{10}
\contentsline {subsection}{\numberline {2.5.2}Serial Console (optional)}{11}
\contentsline {subsubsection}{Serial Console BIOS configuration}{11}
\contentsline {subsubsection}{Serial Console GRUB configuration}{11}
\contentsline {subsubsection}{Serial Console Xen configuration}{12}
\contentsline {subsubsection}{Serial Console Linux configuration}{12}
\contentsline {subsubsection}{Serial Console Login configuration}{13}
\contentsline {subsection}{\numberline {2.5.3}TLS Libraries}{14}
\contentsline {section}{\numberline {2.6}Booting Xen}{14}
\contentsline {chapter}{\numberline {3}Booting a Xen System}{15}
\contentsline {section}{\numberline {3.1}Booting Domain0}{15}
\contentsline {section}{\numberline {3.2}Booting Guest Domains}{16}
\contentsline {subsection}{\numberline {3.2.1}Creating a Domain Configuration File}{16}
\contentsline {subsection}{\numberline {3.2.2}Booting the Guest Domain}{16}
\contentsline {section}{\numberline {3.3}Starting / Stopping Domains Automatically}{17}
\contentsline {part}{II\hspace {1em}Configuration and Management}{19}
\contentsline {chapter}{\numberline {4}Domain Management Tools}{21}
\contentsline {section}{\numberline {4.1}{Xend}\xspace \ }{21}
\contentsline {subsection}{\numberline {4.1.1}Logging}{22}
\contentsline {subsection}{\numberline {4.1.2}Configuring {Xend}\xspace \ }{22}
\contentsline {section}{\numberline {4.2}Xm}{23}
\contentsline {subsection}{\numberline {4.2.1}Basic Management Commands}{23}
\contentsline {subsection}{\numberline {4.2.2}Domain Scheduling Management Commands}{24}
\contentsline {chapter}{\numberline {5}Domain Configuration}{25}
\contentsline {section}{\numberline {5.1}Configuration Files}{25}
\contentsline {section}{\numberline {5.2}Network Configuration}{26}
\contentsline {subsection}{\numberline {5.2.1}Xen virtual network topology}{26}
\contentsline {subsection}{\numberline {5.2.2}Xen networking scripts}{27}
\contentsline {section}{\numberline {5.3}Driver Domain Configuration}{27}
\contentsline {subsection}{\numberline {5.3.1}PCI}{27}
\contentsline {subsubsection}{Compile-Time Setup}{27}
\contentsline {subsubsection}{PCI Backend Configuration - Binding at Boot}{28}
\contentsline {subsubsection}{PCI Backend Configuration - Late Binding}{28}
\contentsline {subsubsection}{PCI Backend Configuration - User-space Quirks}{29}
\contentsline {subsubsection}{PCI Backend Configuration - Permissive Flag}{29}
\contentsline {subsubsection}{PCI Backend - Checking Status}{29}
\contentsline {subsubsection}{PCI Frontend Configuration}{30}
\contentsline {section}{\numberline {5.4}Support for virtual Trusted Platform Module (vTPM)}{30}
\contentsline {subsubsection}{Compile-Time Setup}{31}
\contentsline {subsubsection}{Development and Testing TPM Emulator}{31}
\contentsline {subsubsection}{vTPM Frontend Configuration}{32}
\contentsline {subsubsection}{Using the virtual TPM}{32}
\contentsline {chapter}{\numberline {6}Storage and File System Management}{33}
\contentsline {section}{\numberline {6.1}Exporting Physical Devices as VBDs}{33}
\contentsline {section}{\numberline {6.2}Using File-backed VBDs}{34}
\contentsline {subsection}{\numberline {6.2.1}Loopback-mounted file-backed VBDs (deprecated)}{35}
\contentsline {section}{\numberline {6.3}Using LVM-backed VBDs}{36}
\contentsline {section}{\numberline {6.4}Using NFS Root}{37}
\contentsline {chapter}{\numberline {7}CPU Management}{39}
\contentsline {chapter}{\numberline {8}Migrating Domains}{41}
\contentsline {section}{\numberline {8.1}Domain Save and Restore}{41}
\contentsline {section}{\numberline {8.2}Migration and Live Migration}{41}
\contentsline {chapter}{\numberline {9}Securing Xen}{43}
\contentsline {section}{\numberline {9.1}Xen Security Considerations}{43}
\contentsline {section}{\numberline {9.2}Driver Domain Security Considerations}{43}
\contentsline {section}{\numberline {9.3}Security Scenarios}{45}
\contentsline {subsection}{\numberline {9.3.1}The Isolated Management Network}{45}
\contentsline {subsection}{\numberline {9.3.2}A Subnet Behind a Firewall}{45}
\contentsline {subsection}{\numberline {9.3.3}Nodes on an Untrusted Subnet}{45}
\contentsline {chapter}{\numberline {10}sHype/Xen Access Control}{47}
\contentsline {section}{\numberline {10.1}Overview}{48}
\contentsline {section}{\numberline {10.2}Xen Workload Protection Step-by-Step}{49}
\contentsline {subsection}{\numberline {10.2.1}Configuring/Building sHype Support into Xen}{49}
\contentsline {subsection}{\numberline {10.2.2}Creating A WLP Policy in 3 Simple Steps with ezPolicy}{50}
\contentsline {paragraph}{Defining workloads.}{50}
\contentsline {paragraph}{Defining run-time conflicts.}{51}
\contentsline {paragraph}{Translating the workload definition into an sHype/Xen access control policy.}{52}
\contentsline {subsection}{\numberline {10.2.3}Deploying a WLP Policy}{52}
\contentsline {subsection}{\numberline {10.2.4}Labeling Unmanaged User Domains}{53}
\contentsline {subsection}{\numberline {10.2.5}Labeling Resources}{55}
\contentsline {subsection}{\numberline {10.2.6}Testing The Xen Workload Protection}{55}
\contentsline {paragraph}{Test 1: Run-time exclusion rules.}{56}
\contentsline {paragraph}{Test2: Resource access.}{57}
\contentsline {paragraph}{Test 3: Communication.}{57}
\contentsline {subsection}{\numberline {10.2.7}Labeling Domain-0 --or-- Restricting System Authorization}{57}
\contentsline {subsection}{\numberline {10.2.8}Labeling Managed User Domains}{59}
\contentsline {section}{\numberline {10.3}Xen Access Control Policy}{60}
\contentsline {subsection}{\numberline {10.3.1}Policy Header and Policy Name}{61}
\contentsline {subsection}{\numberline {10.3.2}Simple Type Enforcement Policy Component}{62}
\contentsline {subsection}{\numberline {10.3.3}Chinese Wall Policy Component}{63}
\contentsline {subsection}{\numberline {10.3.4}Security Labels}{64}
\contentsline {subsection}{\numberline {10.3.5}Managing sHype/Xen Security Policies at Run-time}{67}
\contentsline {subsubsection}{Removing the sHype/Xen Security Policy}{67}
\contentsline {subsubsection}{Changing to a Different sHype/Xen Security Policy}{67}
\contentsline {subsubsection}{Update an sHype/Xen Security Policy at Run-time}{69}
\contentsline {paragraph}{Types and Conflic Sets}{70}
\contentsline {paragraph}{Labels}{70}
\contentsline {subsection}{\numberline {10.3.6}Tools For Creating sHype/Xen Security Policies}{74}
\contentsline {section}{\numberline {10.4}Current Limitations}{74}
\contentsline {subsection}{\numberline {10.4.1}Network Traffic}{74}
\contentsline {subsection}{\numberline {10.4.2}Resource Access and Usage Control}{74}
\contentsline {subsection}{\numberline {10.4.3}Domain Migration}{75}
\contentsline {subsection}{\numberline {10.4.4}Covert Channels}{75}
\contentsline {part}{III\hspace {1em}Reference}{77}
\contentsline {chapter}{\numberline {11}Build and Boot Options}{79}
\contentsline {section}{\numberline {11.1}Top-level Configuration Options}{79}
\contentsline {section}{\numberline {11.2}Xen Build Options}{79}
\contentsline {section}{\numberline {11.3}Xen Boot Options}{80}
\contentsline {section}{\numberline {11.4}XenLinux Boot Options}{83}
\contentsline {chapter}{\numberline {12}Further Support}{85}
\contentsline {section}{\numberline {12.1}Other Documentation}{85}
\contentsline {section}{\numberline {12.2}Online References}{85}
\contentsline {section}{\numberline {12.3}Mailing Lists}{86}
\contentsline {chapter}{\numberline {A}Unmodified (HVM) guest domains in Xen with Hardware support for Virtualization}{87}
\contentsline {section}{\numberline {A.1}Building Xen with HVM support}{87}
\contentsline {section}{\numberline {A.2}Configuration file for unmodified HVM guests}{88}
\contentsline {section}{\numberline {A.3}Creating virtual disks from scratch}{90}
\contentsline {subsection}{\numberline {A.3.1}Using physical disks}{90}
\contentsline {subsection}{\numberline {A.3.2}Using disk image files}{90}
\contentsline {section}{\numberline {A.4}HVM Guests}{93}
\contentsline {subsection}{\numberline {A.4.1}Editing the Xen HVM config file}{93}
\contentsline {subsection}{\numberline {A.4.2}Creating HVM guests}{93}
\contentsline {subsection}{\numberline {A.4.3}Mouse issues, especially under VNC}{93}
\contentsline {subsection}{\numberline {A.4.4}USB Support}{96}
\contentsline {subsection}{\numberline {A.4.5}Destroy HVM guests}{98}
\contentsline {subsection}{\numberline {A.4.6}HVM window (X or VNC) Hot Key}{98}
\contentsline {chapter}{\numberline {B}Vnets - Domain Virtual Networking}{99}
\contentsline {section}{\numberline {B.1}Example}{100}
\contentsline {section}{\numberline {B.2}Installing vnet support}{101}
\contentsline {chapter}{\numberline {C}Glossary of Terms}{103}

[Stefan Kottwitz]

Is this file called user.toc? Because I've read in the logfile:

Code: Select all

No file user.toc.

Stefan

[xen_latex]

I had to do a cut and paste since this tool would not let me upload a .toc file.

[Stefan Kottwitz]

Yes, but the problems seems to be that the compiler cannot find a file user.toc, that's why I've asked if this is exactly user.toc or if the name is different. But now I'm noticing at the beginning of the log file

Code: Select all

This is TeX, Version 3.14159 (Web2C 7.4.5) (format=latex 2004.9.30)  31 OCT 2008 14:02
**src/user.tex
(./src/user.tex

that you're compiling a file in a subdirectory, perhaps that's a problem.
Try compiling by latex user inside the src directory instead of latex src/user.

Stefan

[xen_latex]

Thanks. I see what you are saying. Will give it a try and update later today after my lunch meetings. Appreciate your great help.