You are here: everRun User's Guide > Managing Virtual Machines > Creating and Migrating Virtual Machines > Creating a New Virtual Machine

Creating a New Virtual Machine

Create a new virtual machine (VM) to install a guest operating system on your everRun system. (You can also migrate an existing VM or physical machine (PM), as summarized in Creating and Migrating Virtual Machines.)

Launch the VM Creation Wizard by clicking Create on the Virtual Machines page. The wizard steps you through the process of allocating resources to the VM.

Note:
If you need to create a Windows Server 2003 VM, see Creating a New Windows Server 2003 Virtual Machine. You must perform a different procedure to create a Windows Server 2003 VM.
Prerequisites:  

To create a new VM

  1. On the Physical Machines page (see The Physical Machines Page), verify that both PMs are in the running state and that neither PM is in maintenance mode or in the process of synchronizing.
  2. On the Virtual Machines page (see The Virtual Machines Page), click Create to open the VM Creation Wizard.
  3. On the Name, Description, Protection and OS page:
    1. Type the Name and an optional Description for the VM as they will appear in the everRun Availability Console.
    2. Select the level of protection to use for the VM:
      • Fault Tolerant (FT)—Transparently protects an application by creating a redundant environment for a VM running across two physical machines. Use FT for applications that need greater downtime protection than HA provides.
      • High Availability (HA)—Provides basic failover and recovery, with some faults requiring an (automatic) VM reboot for recovery. Use HA for applications that can tolerate some downtime and that do not need the downtime protection that FT provides.

      For more information about these levels of protection, see Modes of Operation.

    3. For Boot From, select one of the following as the boot source:
      • VCD—The boot source is a VCD. Select a source from the pull-down menu.
      • Remote ISO via Windows Share (CIFS/SMB)—The boot source is a remote ISO file on a shared network drive. You must enter values for User Name and Password. For Repository, enter a value in the format //iso_url/path_to_ISO_folder.
      • Remote ISO via NFS—The boot source is a remote ISO file, accessed through NFS. For Repository, enter a value in the format //iso_url/path_to_ISO_folder.

      For a list of available ISO repositories, click List ISOs, and select an ISO file. The full path name of the selected ISO file appears under Repository. You cannot edit the ISO URL that is displayed.

    4. Click Next.
  4. On the vCPUs and Memory page:
    1. Specify the number of vCPUs and the amount of Memory to assign to the VM. For more information, see Planning Virtual Machine vCPUs and Planning Virtual Machine Memory.
    2. If applicable, select the Keyboard Layout in Console to set the keyboard type for your country.
    3. Click Next.
  5. On the Volumes page:
    1. Type the Name of the boot volume as it will appear in the everRun Availability Console.
    2. Type the Container Size and Volume Size of the volume to create in gigabytes (GB). The container size is the total size for the volume including extra space to store snapshots. The volume size is the portion of the container that is available to the guest operating system. For more information about allocating storage, see Sizing Volume Containers and Planning Virtual Machine Storage.

    3. Select the Disk Image format:
      • RAW—raw disk format
      • QCOW2—QEMU Copy On Write (QCOW2) format, which supports snapshots
    4. Select the Storage Group in which to create the volume, and, if applicable, select the Sector Size.

      Ensure that you select a storage group that supports the sector size of the volume that you want to create (see Planning Virtual Machine Storage). Note that the boot volume must have a sector size of 512 B. You can select the sector size, either 4K or 512B, only for data disks.

    5. If applicable, create additional data volumes by clicking Add New Volume and specifying the parameters for each volume. (You can also add volumes after you create the VM by using the Reprovision Virtual Machine wizard, as described in Creating a Volume in a Virtual Machine.)
    6. Click Next.
  6. On the Networks page, select the shared networks to attach to the VM (fr more information, see Planning Virtual Machine Networks). To continue, click Next.
  7. On the Creation Summary page:

    1. Review the creation summary. If you need to make changes, click Back.
    2. If you want to prevent a console session from automatically starting to observe the software installation, deselect Launch Console.
    3. To accept the VM as provisioned and begin the software installation, click Finish.
  8. If applicable, observe the progress of the installation of the operating system (allow pop-ups in your browser, if necessary) and respond to any prompts in the VM console session.
  9. After you install the operating system, configure the additional resources and software necessary for production use, as described in:
Caution: If the primary PM fails or the VM crashes before the final reboot after the installation process is completed, the installation of the VM may need to be restarted.

The VM may not reboot if installations of any of the following are aborted:

Related Topics

Copying a Virtual Machine

Renaming a Virtual Machine

Removing a Virtual Machine

Creating and Migrating Virtual Machines

Managing Virtual Machine Resources

Managing the Operation of a Virtual Machine

of