Update drivers to support reading MAC Addresses
Merge pull request #966 from pmorton/read_mac_addresses

Add the ability to map mac addresses to interfaces
Revert "Update drivers to support reading MAC Addresses"

This reverts commit ddabacbeb3d06b189fa5095c226c97b38b287725.
ssh-config help text uses --host instead of -h
Use 127.0.0.1 instead of localhost for port use checking. [GH-1057]

Many systems actually don't have "localhost" setup as loopback in their
/etc/hosts file, so this would fail. This makes it pass.
Disable read timeout on Net::HTTP
Retry SSH on EHOSTUNREACH errors
Add missing translation for "saving" state [GH-1110]
Added driver for VirtualBox 4.2 to 1.0.x stable this is so far not very deep tested. but vagrant up and base commands to work.
Merge pull request #1120 from julianhille/1-0-stable

Added driver for VirtualBox 4.2 to 1.0.x stable this is so far not very...
Update CHANGELOG
v1.0.4
Update CHANGELOG
Update load_plugins to be more Windows friendly. Uses File::PATH_SEPARATOR instead of hard-coded colon (':').
Merge pull request #1128 from sbfaulkner/1-0-stable

backport Windows fix onto 1-0-stable
Add Fedora 17+ NFS support.
Also change Fedora 16 NFS handling.
Fix arch host class

1. Detect os by /etc/os-release
2. Bring nfs_cleanup from parent class
3. Use systemd if available
Remove #nfs? override

My system is now showing nfsd in /proc/filesystems. It must've been
some transient hiccup local to me.
Work around 4.2.0 bug on Windows

VirtualBox 4.2.0 on Windows has a critical bug where "showvminfo
--machinereadable" only outputs 5 lines of output no matter what.
Vagrant relies heavily on this output to read things such as network
interfaces, shared folders, etc. Therefore, prior to this commit,
Vagrant was broken on Windows. Note that this is 100% a VIRTUALBOX BUG.
But enough users will use VirtualBox 4.2.0 on Windows that Vagrant must
work around it.

We work around it by introducing "jank mode" for the 4.2 driver on
Windows. On 4.2.0 only on Windows, Vagrant will use the human-readable
version of "showvminfo" and use some pretty crazy regular expressions to
parse out the information it needs. This approach is far less tested but
it at least gets things working again on Windows with 4.2.0. I'm hoping
in the future that Oracle will quickly fix this issue for a 4.2.1, but
I'm not certain yet.

Even if Oracle fixes the issue, this workaround will be in Vagrant
forever to accomodate legacy 4.2.0 users on Windows.