• Buy Now
    • Rackspace Cloud
    • Email & Apps
    • Fanatical Support for AWS
    • Managed Google Cloud Platform
    • Office 365
  • Log In
    • MyRackspace Portal
    • Cloud Control Panel
    • Rackspace Webmail Login
    • Cloud Office Control Panel
  • Rackspace Logo
  • Developer Home
  • Developer Documentation
  • Blogs ▼
    • Technical Blog
    • Rackspace Blog
  • Support Documentation

Developer Docs


Let’s Build Something Powerful Together!

Submit an issue
  • Microsoft Private Cloud Hyper-V Customer Handbook
  • About Microsoft Hyper-V
    • Roles and responsibilities
      • Managed virtual machines
      • Unmanaged virtual machines
    • Licensing
      • Virtual machine licensing
  • Getting started with Microsoft Hyper-V
    • Microsoft Hyper-V architecture
    • Microsoft Hyper-V features
      • Rackspace Hyper-V managed services
    • Microsoft Server 2016
    • Add-on services
      • Hyper-V Replica
        • Hyper-V Extended Replication
        • Requesting a failover
      • Cloud Replication for Hyper-V
        • Requesting a failover
  • Microsoft Hyper-V user manual
    • Manage permissions
      • Assigning permissions by user
      • Assigning permissions by product
      • Managing groups
      • Changing global permissions
    • Credentials management
      • Windows Server 2016 (v2)
        • Rackspace
        • Customer
      • Windows Server 2012 (v1)
        • Rackspace
        • Customer
    • Datastore overhead
      • Why does Rackspace require this?
      • What else can consume space on my datastores?
    • Ordering virtual machines
      • Virtual machine OS images
      • Create a new managed virtual machine
      • Create a new unmanaged virtual machine
      • Converting unmanaged VM to managed
    • Managing virtual machines
      • Start or resume a virtual machine
      • Shut down a virtual machine
      • Checkpoint a virtual machine
        • Reverting a checkpoint
        • Delete a checkpoint
      • Export virtual machines
      • Resize virtual hard disks
      • Making a virtual machine highly available
      • Remove and delete virtual machines
    • Decommissioning virtual machines and hypervisors
    • Virtual Fibre Channel SAN
      • Deploying virtual SAN
    • Migrating from Server 2012 to 2016
  • Frequently asked questions
  • Additional resources
    • SLA information
    • Additional links
  • Disclaimer

Ordering virtual machines#

This section provides information about ordering virtual machines.

Virtual machine OS images#

Rackspace provides you with all the base images for all your VMs. The following is a list of supported virtual machine operating systems for Hyper-V:

  • Windows Server 2012 Datacenter
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2016 Datacenter
  • CentOS 6.7
  • CentOS 7
  • Ubuntu® 14.04 LTS
  • Ubuntu 16.04 LTS
  • RHEL 6.7
  • RHEL 7

Create a new managed virtual machine#

Create a support ticket to request a new managed virtual machine. Rackspace requests the following configuration details to ensure the VM is deployed to your specification:

  • Name
  • OS type
  • vCPU count
  • RAM size
  • Disks
  • VLAN/Segment
  • Requested IP
  • File level backups (Yes/No)
  • Customer domain

See the Additional Resources section for a video on how the Rackspace Microsoft Hyper-V support team creates virtual machines.

Create a new unmanaged virtual machine#

  • The New-VM cmdlet creates a virtual machine. Use the following commands to create a virtual machine by using PowerShell:

    1. New-VM -Name "<name>" -MemoryStartupBytes <size> -NewVHDPath <path>
      

    Note

    -NewVHDPath, -NewVHDSizeBytes and -VHDPath are required parameters when running this command. For more information, see the PowerShell documentation for New-VM.

  • Use the following instructions to create a virtual machine by using the Management Virtual Machine (VM):

  1. In the Management VM, click Action > New > Virtual Machine to open the New Virtual Machine Wizard.

  2. Review the Before You Begin page and click Next.

  3. Assign an appropriate name to the virtual machine.

    Ensure that the name you assign is under 15 characters.

  4. Choose a location where you want to store the virtual machine files or choose the default location, and then click Next.

  5. Select either Windows Server 2012 R2(v1) or Windows Server 2016(v2) as the generation, and then click Next.

  6. Select 2048 MB for the Startup Memory value and leave Use Dynamic Memory selected, and then click Next.

  7. On the Configure Networking wizard, select a virtual switch for the virtual machine and then click Next.

  8. Give the virtual hard drive a name, select a location or keep the default, and specify a size. Then click Next.

  9. On the Installation Options wizard, select Install an operating system from a bootable image file and then select an operating system .iso file. Click Next.

  10. Review the virtual machine details and then click Finish.

Converting unmanaged VM to managed#

To convert an unmanaged VM to managed, create a support ticket with your Microsoft Hyper-V Support team to request a conversion.

Note

At this time, Rackspace can only convert Windows unmanaged machines. Linux machines are currently unable to be converted.

Previous Datastore overhead
Next Managing virtual machines
Docs
  • Style Guide for Technical Content
  • Cloud Backup
  • Cloud Block Storage
  • Cloud Databases
  • Cloud DNS
  • Cloud Files
  • Identity
  • Cloud Images
  • Cloud Load Balancers
  • Cloud Monitoring
  • Cloud Orchestration
  • Cloud Networks
  • Cloud Queues
  • Cloud Servers
  • Rackspace Auto Scale
  • Rackspace CDN
Sdks
  • Go
  • Java
  • .Net
  • Node
  • PHP
  • Python
  • Ruby
Partner Tools
  • Airbrake
  • Mailgun
  • ObjectRocket
  • RedisToGo
Blog
  • Technical Blog
  • Rackspace Blog
©2019 Rackspace US, Inc.
  • ©2019 Rackspace US, Inc.
  • About Rackspace
  • Investors
  • Careers
  • Privacy Statement
  • Website Terms
  • Trademarks