<commit_before>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{\label{sec:Virtual-Machines}
Running HTCondor Jobs within a Virtual Machine}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\index{virtual machine!running HTCondor jobs under}

HTCondor jobs are formed from executables that are compiled to execute
on specific platforms.
This in turn restricts the machines within an HTCondor pool where
a job may be executed.
An HTCondor job may now be executed on a 
virtual machine system running VMware, Xen, or KVM.
This allows Windows executables to run on a Linux machine,
and Linux executables to run on a Windows machine.

In older versions of HTCondor, other parts of the system were also
referred to as \Term{virtual machines}, but in all cases, those are now
known as \Term{slots}.
A virtual machine here describes the environment in which
the outside operating system (called the host) emulates an inner operating
system (called the inner virtual machine),
such that an executable appears to run directly
on the inner virtual machine.
In other parts of HTCondor, a \Term{slot} (formerly known as
\Term{virtual machine}) refers to the multiple cores of a multi-core
machine.
Also, be careful not to confuse the virtual machines discussed here
with the Java Virtual Machine (JVM) referenced in other parts of this
manual.

HTCondor has the flexibility to run a job on either the host
or the inner virtual machine, 
hence two platforms appear to exist on a single machine.
Since two platforms are an illusion, HTCondor understands the illusion, 
allowing an HTCondor job to be execute on only
one at a time.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{\label{sec:Virtual-Machines-Configuration}
Installation and Configuration}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
<commit_msg>correct typo and add note about vm universe being different than running HTCondor on an existing/running virtual machine ===GT=== #2433<commit_after>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{\label{sec:Virtual-Machines}
Running HTCondor Jobs within a Virtual Machine}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\index{virtual machine!running HTCondor jobs under}

HTCondor jobs are formed from executables that are compiled to execute
on specific platforms.
This in turn restricts the machines within an HTCondor pool where
a job may be executed.
An HTCondor job may now be executed on a 
virtual machine running VMware, Xen, or KVM.
This allows Windows executables to run on a Linux machine,
and Linux executables to run on a Windows machine.

In older versions of HTCondor, other parts of the system were also
referred to as \Term{virtual machines}, but in all cases, those are now
known as \Term{slots}.
A virtual machine here describes the environment in which
the outside operating system (called the host) emulates an inner operating
system (called the inner virtual machine),
such that an executable appears to run directly
on the inner virtual machine.
In other parts of HTCondor, a \Term{slot} (formerly known as
\Term{virtual machine}) refers to the multiple cores of a multi-core
machine.
Also, be careful not to confuse the virtual machines discussed here
with the Java Virtual Machine (JVM) referenced in other parts of this
manual.
Targeting an HTCondor job to run on an inner virtual machine is
also different than using the \SubmitCmd{vm} universe. 
The \SubmitCmd{vm} universe lands and starts up a virtual machine
instance, which is the HTCondor job, on an execute machine.

HTCondor has the flexibility to run a job on either the host
or the inner virtual machine, 
hence two platforms appear to exist on a single machine.
Since two platforms are an illusion, HTCondor understands the illusion, 
allowing an HTCondor job to be executed on only
one at a time.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{\label{sec:Virtual-Machines-Configuration}
Installation and Configuration}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

{'fraction_non_alphanumeric': 0.16960457360647926, 'fraction_numerical': 0.0009528346831824678, 'mean_word_length': 5.77258064516129, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4534370', 'n_tokens_mistral': 1005, 'n_tokens_neox': 950, 'n_words': 547}