Download Vmware Workstation 6.5 Serial Key

Download Vmware Workstation 6.5 Serial Key
Download Vmware Workstation 6.5 Serial Key 64-bit
Download Vmware Workstation 6.5 Serial Keyboard
Download Vmware Workstation 6.5 Serial Keys
Download Vmware Workstation 6.5 Serial Key Generator

This VMware Packer builder is able to create VMware virtual machines from an ISO file as a source. It currently supports building virtual machines on hosts running VMware Fusion for OS X, VMware Workstation for Linux and Windows, and VMware Player on Linux. It can also build machines directly on VMware vSphere Hypervisor using SSH as opposed to the vSphere API. If you are using a supported version of VMware vSphere earlier than 6.5, or are configuring a VM to use vSGA, omit this task. Change the default graphics type before configuring vGPU. Output from the VM console in the VMware vSphere Web Client is not available for VMs that are running vGPU.

The FreeNAS^® operating system has to be installed on aseparate device from the drives which hold the storage data. With onlyone disk drive, the FreeNAS^® web interface isavailable, but there is no place to store any data. And storing datais, after all, the whole point of a NAS system. Home usersexperimenting with FreeNAS^® can install FreeNAS^® on an inexpensive USBthumb drive and use the computer disks for storage.

This section describes:

2.1. Getting FreeNAS^®¶

The latest STABLE version of FreeNAS^® 11.2 is available for downloadfrom https://download.freenas.org/11.2/STABLE/latest/.

The download page contains an .iso file. This is a bootableinstaller that can be written to either a CD or USB flash as describedin Preparing the Media.

The .iso file has an associated sha256.txt file which isused to verify the integrity of the downloaded file. The command toverify the checksum varies by operating system:

on a BSD system use the commandsha256name_of_file
on a Linux system use the commandsha256sumname_of_file
on a Mac system use the commandshasum-a256name_of_file
Windows or Mac users can install additional utilities likeHashCalcorHashTab.

The value produced by running the command must match the value shownin the sha256.txt file. Checksum values that do not matchindicate a corrupted installer file that should not be used.

2.2. Preparing the Media¶

The FreeNAS^® installer can run from either a CD or a USB memorystick.

A CD burning utility is needed to write the .iso file to aCD.

The .iso file can also be written to a USB memory stick. Themethod used to write the file depends on the operating system.Examples for several common operating systems are shown below.

Note

To install from a USB stick to another USB stick, twoUSB ports are needed, each with an inserted USB device. One USBstick contains the installer. The other USB stick is thedestination for the FreeNAS^® installation. Take care to select thecorrect USB device for the FreeNAS^® installation. It is notpossible to install FreeNAS^® onto the same USB stick containing theinstaller. After installation, remove the installer USB stick. Itmight also be necessary to adjust the BIOS configuration to bootfrom the new FreeNAS^® USB stick.

Ensure the boot device order in the BIOS is set to boot fromthe device containing the FreeNAS^® installer media, then boot thesystem to start the installation.

2.2.1. On FreeBSD or Linux¶

On a FreeBSD or Linux system, the dd command is used towrite the .iso file to an inserted USB thumb drive.

Warning

The dd command is very powerful and candestroy any existing data on the specified device. Makeabsolutely sure of the device name to write to and do notmistype the device name when using dd! This command canbe avoided by writing the .iso file to a CD instead.

This example demonstrates writing the image to the first USB deviceconnected to a FreeBSD system. This first device usually reports as/dev/da0. Replace FreeNAS-RELEASE.iso with the filenameof the downloaded FreeNAS^® ISO file. Replace /dev/da0 withthe device name of the device to write.

When using the dd command:

if= refers to the input file, or the name of the file to writeto the device.
of= refers to the output file; in this case, the device name ofthe flash card or removable USB drive. Note that USB device numbersare dynamic, and the target device might be da1 or da2 oranother name depending on which devices are attached. Beforeattaching the target USB drive, use ls /dev/da*. Thenattach the target USB drive, wait ten seconds, and run ls/dev/da* again to see the new device name and number of the targetUSB drive. On Linux, use /dev/sdX, where X refers to theletter of the USB device.
bs= refers to the block size, the amount of data to write at atime. The larger 64K block size shown here helps speed up writes tothe USB drive.

2.2.2. On Windows¶

Image WriterandRufuscan be used for writing images to USB sticks on Windows.

2.2.3. On macOS¶

Download Vmware Workstation 6.5 Serial Key

Insert the USB thumb drive. In Finder, go toApplications ‣ Utilities ‣ Disk Utility.Unmount any mounted partitions on the USB thumb drive. Check that theUSB thumb drive has only one partition, or partition table errors willbe shown on boot. If needed, use Disk Utility to set up one partitionon the USB drive. Selecting Free space when creating thepartition works fine.

Determine the device name of the inserted USB thumb drive. FromTERMINAL, navigate to the Desktop, then type this command:

This shows which devices are available to the system. Locate thetarget USB stick and record the path. To determine the correct pathfor the USB stick, remove the device, run thecommand again, and compare the difference. Once sure of the devicename, navigate to the Desktop from TERMINAL, unmount the USB stick,and use the dd command to write the image to the USB stick.In this example, the USB thumb drive is /dev/disk1. It isfirst unmounted. The dd command is used to write theimage to the faster “raw” version of the device (note the extrar in /dev/rdisk1).

When running these commands, replace FreeNAS-RELEASE.isowith the name of the FreeNAS^® ISO and /dev/rdisk1 with thecorrect path to the USB thumb drive:

Note

If the error “Resource busy” is shown when thedd command is run, go toApplications ‣ Utilities ‣ Disk Utility,find the USB thumb drive, and click on its partitions to make sureall of them are unmounted. If a “Permission denied” error is shown,use sudo for elevated rights:sudoddif=FreeNAS-11.0-RELEASE.isoof=/dev/rdisk1bs=64k.This will prompt for the password.

The dd command can take some minutes to complete. Waituntil the prompt returns and a message is displayed with informationabout how long it took to write the image to the USB drive.

2.3. Performing the Installation¶

With the installation media inserted, boot the system from that media.

The FreeNAS^® installer boot menu is displayed as is shown inFigure 2.3.1.

The FreeNAS^® installer automatically boots into the default option afterten seconds. If needed, choose another boot option by pressing theSpacebar to stop the timer and then enter the number of thedesired option.

Tip

The Serial Console option is useful on systemswhich do not have a keyboard or monitor, but are accessed through aserial port, Serial over LAN, or IPMI.

Note

If the installer does not boot, verify that the installationdevice is listed first in the boot order in the BIOS. When bootingfrom a CD, some motherboards may require connecting the CD deviceto SATA0 (the first connector) to boot from CD. If the installerstalls during bootup, double-check the SHA256 hash of the.iso file. If the hash does not match, re-download thefile. If the hash is correct, burn the CD again at a lower speed orwrite the file to a different USB stick.

Once the installer has finished booting, the installer menu is displayedas shown in Figure 2.3.2.

Press Enter to select the default option,1 Install/Upgrade. The next menu, shown inFigure 2.3.3,lists all available drives. This includes any inserted USB thumbdrives, which have names beginning with da.

Note

A minimum of 8 GiB of RAM is required and the installer willpresent a warning message if less than 8 GiB is detected.

In this example, the user is performing a test installation usingVirtualBox and has created a 16 GiB virtual disk to hold the operatingsystem.

Use the arrow keys to highlight the destination USB drive, SSD, DOM(Disk on Module), or virtual disk. Press the spacebar to selectit. To mirror the boot device, move to the second device and pressspacebar to select it also. After making these selections,press Enter. The warning shown inFigure 2.3.4is displayed, a reminder not to install the operating system on adrive that is meant for storage. Press Enter to continue on tothe screen shown inFigure 2.3.6.

Fig. 2.3.4 Installation Warning

Note

A minimum of 8 GiB of space on the boot device is required.However, 32 GiB is recommended to provide room for future additionsand boot environments. When using mirrored boot devices, it is bestto use devices of the same size. If the device sizes are different,the mirror is limited to the size of the smaller device.

The installer recognizes existing installations of previous versionsof FreeNAS^®. When an existing installation is present, the menu shown inFigure 2.3.5is displayed. To overwrite an existing installation, use the arrowsto move to Fresh Install and press Enter twice tocontinue to the screen shown inFigure 2.3.6.

The screen shown inFigure 2.3.6prompts for the root passwordwhich is used to log in to the web interface.

Fig. 2.3.6 Set the Root Password

Setting a password is mandatory and the password cannot be blank.Since this password provides access to the web interface, itneeds to be hard to guess. Enter the password, press the down arrow key,and confirm the password. Then press Enter to continue with theinstallation. Choosing Cancel skips setting a root passwordduring the installation, but the web interface will require setting aroot password when logging in for the first time.

Note

For security reasons, the SSH service and root SSH loginsare disabled by default. Unless these are set, the only way toaccess a shell as root is to gain physical access to the consolemenu or to access the web shell within the web interface. Thismeans that the FreeNAS^® system needs to be kept physically secure andthat the web interface needs to be behind a properly configuredfirewall and protected by a secure password.

FreeNAS^® can be configured to boot with the standard BIOS bootmechanism or UEFI booting as shownFigure 2.3.7.BIOS booting is recommended for legacy and enterprise hardware. UEFIis used on newer consumer motherboards.

Note

Most UEFI systems can also boot in BIOS mode if CSM(Compatibility Support Module) is enabled in the UEFI setupscreens.

The message inFigure 2.3.8is shown after the installation is complete.

Press Enter to return to Installer Menu.Highlight 3 Reboot System and press Enter. Ifbooting from CD, remove the CDROM. As the system reboots, make surethat the device where FreeNAS^® was installed is listed as the firstboot entry in the BIOS so the system will boot from it.

FreeNAS^® boots into the Console Setup menu described inBooting after waiting five seconds in theboot menu. Press the Spacebar to stop thetimer and use the boot menu.

2.4. Installation Troubleshooting¶

If the system does not boot into FreeNAS^®, there are several thingsthat can be checked to resolve the situation.

Check the system BIOS and see if there is an option to change the USBemulation from CD/DVD/floppy to hard drive. If it still will not boot,check to see if the card/drive is UDMA compliant.

If the system BIOS does not support EFI with BIOS emulation, see if ithas an option to boot using legacy BIOS mode.

When the system starts to boot but hangs with this repeated errormessage:

go into the system BIOS and look for an onboard device configurationfor a 1394 Controller. If present, disable that device and try bootingagain.

If the system starts to boot but hangs at a mountroot> prompt,follow the instructions inWorkaround/Semi-Fix for Mountroot Issues with 9.3.

If the burned image fails to boot and the image was burned using aWindows system, wipe the USB stick before trying a second burn using autility such asActive@ KillDisk.Otherwise, the second burn attempt will fail as Windows does notunderstand the partition which was written from the image file. Bevery careful to specify the correct USB stick when using a wipeutility!

2.5. Upgrading¶

FreeNAS^® provides flexibility for keeping the operating systemup-to-date:

Upgrades to major releases, for example from version 9.3 to 9.10,can still be performed using either an ISO or theweb interface. Unless the Release Notes for the newmajor release indicate that the current version requires an ISOupgrade, either upgrade method can be used.
Minor releases have been replaced with signed updates. This meansthat it is not necessary to wait for a minor release to update thesystem with a system update or newer versions of drivers andfeatures. It is also no longer necessary to manually download anupgrade file and its associated checksum to update the system.
The updater automatically creates a boot environment, makingupdates a low-risk operation. Boot environments provide theoption to return to the previous version of the operating system byrebooting the system and selecting the previous boot environmentfrom the boot menu.

This section describes how to perform an upgrade from an earlierversion of FreeNAS^® to 11.2. After 11.2 has been installed,use the instructions in Update to keep the system updated.

2.5.1. Caveats¶

Be aware of these caveats before attempting an upgrade to11.2:

Warning: upgrading the ZFS pool can make it impossible to go backto a previous version. For this reason, the update process doesnot automatically upgrade the ZFS pool, though the Alertsystem shows when newer ZFS Feature Flags are available for apool. Unless a new feature flag is needed, it is safe to leave thepool at the current version and uncheck the alert. If the pool isupgraded, it will not be possible to boot into a previous version thatdoes not support the newer feature flags.
Upgrading the firmware of Broadcom SAS HBAs to the latest version isrecommended.
If upgrading from 9.3.x, read theFAQ: Updating from 9.3 to 9.10first.
Upgrades from FreeNAS^®0.7x are not supported. The systemhas no way to import configuration settings from 0.7x versions ofFreeNAS^®. The configuration must be manually recreated. Ifsupported, the FreeNAS^® 0.7x pools or disks must be manuallyimported.
Upgrades on 32-bit hardware are not supported. However, if thesystem is currently running a 32-bit version of FreeNAS^®and thehardware supports 64-bit, the system can be upgraded. Anyarchived reporting graphs will be lost during the upgrade.
UFS is not supported. If the data currently resides on oneUFS-formatted disk, create a ZFS pool using other disks after theupgrade, then use the instructions in Importing a Disk to mount the UFS-formatted disk and copy the data to the ZFS pool. With onlyone disk, back up its data to another system or media before theupgrade, format the disk as ZFS after the upgrade, then restore thebackup. If the data currently resides on a UFS RAID of disks, it isnot possible to directly import that data to the ZFS pool. Instead,back up the data before the upgrade, create a ZFS pool after theupgrade, then restore the data from the backup.
The VMware Tools VMXNET3 drivers are not supported. Configure anduse the vmx(4)driver instead.

2.5.2. Initial Preparation¶

Before upgrading the operating system, perform the following steps:

Back up the FreeNAS^®configuration inSystem ‣ General ‣ Save Config.
If any pools are encrypted, remember to set a passphraseand download a copy of the encryption key and the latestrecovery key.After the upgrade is complete, use the instructions inImporting a Pool to import the encrypted pools.
Warn users that the FreeNAS^® shares will be unavailable during theupgrade; it is recommended to schedule the upgrade for a timethat will least impact users.
Stop all services inServices.

2.5.3. Upgrading Using the ISO¶

To perform an upgrade using this method,downloadthe .iso to the computer that will be used to prepare theinstallation media. Burn the downloaded .iso file to a CD orUSB thumb drive using the instructions inPreparing the Media.

Insert the prepared media into the system and boot from it. Theinstaller waits ten seconds in theinstaller boot menu before booting thedefault option. If needed, press the Spacebar to stop the timerand choose another boot option. After the media finishes booting intothe installation menu, press Enter to select the default optionof 1 Install/Upgrade. The installer presents a screenshowing all available drives.

Warning

All drives are shown, including boot drives and storagedrives. Only choose boot drives when upgrading. Choosing the wrongdrives to upgrade or install will cause loss of data. If unsureabout which drives contain the FreeNAS^® operating system, reboot andremove the install media. In the FreeNAS^® web interface, useSystem ‣ Bootto identify the boot drives. More than one drive is shown when amirror has been used.

Move to the drive where FreeNAS^® is installed and press theSpacebar to mark it with a star. If a mirror has been used forthe operating system, mark all of the drives where the FreeNAS^®operating system is installed. Press Enter when done.

The installer recognizes earlier versions of FreeNAS^® installed on theboot drive or drives and presents the message shown inFigure 2.5.1.

Note

A FreeNAS^® system can be upgraded by backing up the existingconfiguration data, performing a fresh install, then restoring theconfiguration. Back up the configuration withSystem ‣ General ‣ Save Config.Choose Fresh Install during the installation. Afterbooting into the new install, restore the previous configurationdata withSystem ‣ General ‣ Upload Config.

To perform an upgrade, press Enter to accept the default ofUpgrade Install. Again, the installer will display areminder that the operating system should be installed on a diskthat is not used for storage.

Fig. 2.5.2 Install in New Boot Environment or Format

The updated system can be installed in a new boot environment,or the entire boot device can be formatted to start fresh. Installinginto a new boot environment preserves the old code, allowing aroll-back to previous versions if necessary. Formatting the bootdevice is usually not necessary but can reclaim space. User data andsettings are preserved when installing to a new boot environment andalso when formatting the boot device. Move the highlight to one of theoptions and press Enter to start the upgrade.

The installer unpacks the new image and displays the menu shown inFigure 2.5.3.The database file that is preserved and migrated contains your FreeNAS^®configuration settings.

Press Enter. FreeNAS^® indicates that the upgrade is complete anda reboot is required. Press OK, highlight3 Reboot System, then press Enter to reboot thesystem. If the upgrade installer was booted from CD, remove the CD.

During the reboot there can be a conversion of the previousconfiguration database to the new version of the database. Thishappens during the “Applying database schema changes” line in thereboot cycle. This conversion can take a long time to finish,sometimes fifteen minutes or more, and can cause the systemto reboot again. The system will startnormally afterwards. If database errors are shown but the web interfaceis accessible, go toSettings ‣ Generaland use the UPLOAD CONFIG button to upload theconfiguration that was saved before starting the upgrade.

2.5.4. Upgrading From the Web Interface¶

To perform an upgrade using this method, go toSystem ‣ Update.

The connection is lost temporarily when the update is complete. Itreturns after the FreeNAS^® system reboots into the new version of theoperating system. The FreeNAS^® system normally receives the sameIP address from the DHCP server. Refresh the browser after a momentto see if the system is accessible.

2.5.5. If Something Goes Wrong¶

If an update fails, an alert is issued and the details are written to/data/update.failed.

To return to a previous version of the operating system, physical or IPMIaccess to the FreeNAS^® console is needed. Reboot the system and watch forthe boot menu:

FreeNAS^® waits five seconds before booting into the default bootenvironment. Press the Spacebar to stop the automaticboot timer. Press 4 to display the available boot environmentsand press 3 as needed to scroll through multiple pages.

Fig. 2.5.5 Boot Environments

In the example shown in Figure 2.5.5, the firstentry in Boot Environments is11.2-MASTER-201807250900. This is the current version of theoperating system, after the update was applied. Since it is the firstentry, it is the default selection.

The next entry is Initial-Install. This is the original bootenvironment created when FreeNAS^® was first installed. Since there are noother entries between the initial installation and the first entry, onlyone update has been applied to this system since its initialinstallation.

To boot into another version of the operating system, enter the numberof the boot environment to set it as Active. PressBackspace to return to the Boot Menu andpress Enter to boot into the chosen Active bootenvironment.

If a boot device fails and the system no longer boots, do not panic.The data is still on the disks and there is still a copy of the savedconfiguration. The system can be recovered with a few steps:

Perform a fresh installation on a new boot device.
Import the pools inStorage ‣ Auto Import Pool.
Restore the configuration inSystem ‣ General ‣ Upload Config.

Note

It is not possible to restore a saved configuration that isnewer than the installed version. For example, if a rebootinto an older version of the operating system is performed,a configuration created in a later version cannot be restored.

2.5.6. Upgrading a ZFS Pool¶

In FreeNAS^®, ZFS pools can be upgraded from the graphicaladministrative interface.

Before upgrading an existing ZFS pool, be aware of these caveatsfirst:

the pool upgrade is a one-way street, meaning thatif you change your mind you cannot go back to an earlier ZFSversion or downgrade to an earlier version of the software thatdoes not support those ZFS features.
before performing any operation that may affect the data on astorage disk, always back up all data first and verify theintegrity of the backup.While it is unlikely that the pool upgrade will affect the data,it is always better to be safe than sorry.
upgrading a ZFS pool is optional. Do not upgrade the pool if thethe possibility of reverting to an earlier version of FreeNAS^® orrepurposing the disks in another operating system that supports ZFSis desired. It is not necessary to upgrade the pool unless the enduser has a specific need for the newer ZFS Feature Flags. If apool is upgraded to the latest feature flags, it will not be possibleto import that pool into another operating system that does not yetsupport those feature flags.

To perform the ZFS pool upgrade, go toStorage ‣ Pools and click  (Settings)to upgrade. Click theUpgrade Pool button as shown inFigure 2.5.6.

Note

If the Upgrade Pool button does not appear, thepool is already at the latest feature flags and does not need to beupgraded.

The warning serves as a reminder that a pool upgrade is notreversible. Click OK to proceed with the upgrade.

The upgrade itself only takes a few seconds and is non-disruptive.It is not necessary to stop any sharing services to upgrade thepool. However, it is best to upgrade when the pool is not beingheavily used. The upgrade process will suspend I/O for a shortperiod, but is nearly instantaneous on a quiet pool.

2.6. Virtualization¶

FreeNAS^® can be run inside a virtual environment for development,experimentation, and educational purposes. Note that runningFreeNAS^® in production as a virtual machine is not recommended.When using FreeNAS^® within a virtual environment,read this post firstas it contains useful guidelines for minimizing the risk of losingdata.

To install or run FreeNAS^® within a virtual environment, create avirtual machine that meets these minimum requirements:

at least 8192 MiB (8 GiB) base memory size
a virtual disk at least 8 GiB in size to hold the operatingsystem and boot environments
at least one additional virtual disk at least 4 GiB in size to beused as data storage
a bridged network adapter

This section demonstrates how to create and access a virtual machinewithin VirtualBox and VMware ESXi environments.

2.6.1. VirtualBox¶

VirtualBoxis an open source virtualization program originally created by SunMicrosystems. VirtualBox runs on Windows, BSD, Linux, Macintosh, andOpenSolaris. It can be configured to use a downloaded FreeNAS^®.iso file, and makes a good testing environment for practicingconfigurations or learning how to use the features provided byFreeNAS^®.

To create the virtual machine, start VirtualBox and click theNew button, shown inFigure 2.6.1,to start the new virtual machine wizard.

Click the Next button to see the screen inFigure 2.6.2.Enter a name for the virtual machine, click theOperating System drop-down menu and select BSD, and selectFreeBSD (64-bit) from the Version dropdown.

Fig. 2.6.2 Enter Name and Operating System for the New Virtual Machine

Click Next to see the screen inFigure 2.6.3.The base memory size must be changed to at least 8192 MiB. Whenfinished, click Next to see the screen inFigure 2.6.4.

Fig. 2.6.3 Select the Amount of Memory Reserved for the Virtual Machine

Fig. 2.6.4 Select Existing or Create a New Virtual Hard Drive

Click Create to launch theCreate Virtual Hard Drive Wizard shown inFigure 2.6.5.

Select VDI and click the Next button to seethe screen inFigure 2.6.6.

Fig. 2.6.6 Select Storage Type for Virtual Disk

Choose either Dynamically allocated orFixed-size storage. The first option uses disk space asneeded until it reaches the maximum size that is set in the nextscreen. The second option creates a disk the full amount of diskspace, whether it is used or not. Choose the first option to conservedisk space; otherwise, choose the second option, as it allowsVirtualBox to run slightly faster. After selecting Next,the screen inFigure 2.6.7is shown.

Fig. 2.6.7 Select File Name and Size of Virtual Disk

This screen is used to set the size (or upper limit) of the virtualdisk. Set the default size to a minimum of 8 GiB. Use the foldericon to browse to a directory on disk with sufficient space to hold thevirtual disk files. Remember that there will be a system disk ofat least 8 GiB and at least one data storage disk of at least 4 GiB.

Use the Back button to return to a previous screen if anyvalues need to be modified. After making a selection and pressingCreate, the new VM is created. The new virtual machine islisted in the left frame, as shown in the example inFigure 2.6.8. Open the Machine Toolsdrop-down menu and select Details to see extra informationabout the VM.

Create the virtual disks to be used for storage. Highlight the VM andclick Settings to open the menu. Click theStorage option in the left frame to access the storagescreen seen inFigure 2.6.9.

Fig. 2.6.9 Storage Settings of the Virtual Machine

Click the Add Attachment button, selectAdd Hard Disk from the pop-up menu, then click theCreate new disk button. This launches theCreate Virtual Hard Disk wizard seen inFigure 2.6.5 and2.6.6.

Create a disk large enough to hold the desired data. The minimumsize is 4 GiB.To practice with RAID configurations, create as many virtual disks asneeded. Two disks can be created on each IDE controller. Foradditional disks, click the Add Controller button tocreate another controller for attaching additional disks.

Create a device for the installation media. Highlight the word“Empty”, then click the CD icon as shown inFigure 2.6.10.

Click Choose Virtual Optical Disk File… to browse tothe location of the .iso file. If the .iso was burnedto CD, select the detected Host Drive.

Depending on the extensions available in the host CPU, it might not bepossible to boot the VM from an .iso. If“your CPU does not support long mode” is shown when trying to bootthe .iso, the host CPU either does not have the requiredextension or AMD-V/VT-x is disabled in the system BIOS.

Note

If there is a kernel panic when booting into the ISO,stop the virtual machine. Then, go to System and checkthe box Enable IO APIC.

To configure the network adapter, go toSettings ‣ Network ‣ Adapter 1.In the Attached to drop-down menu selectBridged Adapter, then choose the name of the physicalinterface from the Name drop-down menu. In the exampleshown inFigure 2.6.11,the Intel Pro/1000 Ethernet card is attached to the network and has adevice name of em0.

Fig. 2.6.11 Configuring a Bridged Adapter in VirtualBox

After configuration is complete, click the Start arrow andinstall FreeNAS^® as described in Performing the Installation.After FreeNAS^® is installed, press F12 when the VM starts toboot to access the boot menu. Select the primary hard disk as the bootoption. You can permanently boot from disk by removing theOptical device in Storage or by uncheckingOptical in the Boot Order section ofSystem.

2.6.2. VMware ESXi¶

Before using ESXi, readthis postfor an explanation of why iSCSI will be faster than NFS.

ESXi is a bare-metal hypervisor architecture created by VMware Inc.Commercial and free versions of the VMware vSphere Hypervisoroperating system (ESXi) are available from theVMware website.After the operating system is installed on the supported hardware,use a web browser to connect to its IP address. The welcome screenprovides a link to download the VMware vSphere client which is usedto create and manage virtual machines.

Once the VMware vSphere client is installed, use it to connect to theESXi server. To create a new virtual machine, clickFile ‣ New ‣ Virtual Machine.The New Virtual Machine Wizard will launch as shown inFigure 2.6.12.

Click Next and enter a name for the virtual machine. ClickNext and highlight a datastore. An example is shown inFigure 2.6.13.Click Next. In the screen shown inFigure 2.6.14,click Other, then select a FreeBSD 64-bit architecture.

Fig. 2.6.13 Select Datastore

Click Next and create a virtual disk file of 8 GiB tohold the FreeNAS^® operating system, as shown inFigure 2.6.15.

Fig. 2.6.15 Create Disk for the Operating System

Click Next and Finish. The new virtual machineis listed in the left frame. Right-click the virtual machine andselect Edit Settings to access the screen shown inFigure 2.6.16.

Increase the Memory Configuration to at least 8192 MiB.

To create a storage disk,click Hard disk 1 ‣ Add.In the Device Type menu, highlight Hard Diskand click Next. SelectCreate a new virtual disk and click Next. Inthe screen shown inFigure 2.6.17,select the size of the disk. To dynamically allocate space as needed,check the boxAllocate and commit space on demand (Thin Provisioning).Click Next, then Next, then Finishto create the disk. Repeat to create the amount of storage disksneeded to meet your requirements.

Fig. 2.6.17 Creating a Storage Disk

For ESX 5.0, Workstation 8.0, or Fusion 4.0 or higher, additionalconfiguration is needed so that the virtual HPET setting does notprevent the virtual machine from booting.