MNX.io Docs
  • MNX.io Documentation
  • Getting started
    • SSH to an instance from Windows
    • Account password requirements
    • Improving security using two-factor authentication (2FA)
    • Generating an SSH key
      • Manually generating your SSH key in macOS
      • Manually generating your SSH key in Windows
    • API integrations and CLI usage
    • Provisioning limits
    • Cancelling your account
  • Data centers
  • Instances
    • Infrastructure containers
    • Virtual machines
    • Snapshots
      • Automating Snapshots
    • Tags and metadata
    • Connecting to containers and VMs
    • Instance Types
  • Triton CLI & Tools
    • Using the VNC console
    • Triton CLI tool
    • Hashicorp Packer and Terraform
      • Create and manage images with Packer
      • Manage infrastructure with Terraform
    • Container Monitor with Prometheus
  • Network
    • Networking and fabric user guide
    • Firewall
    • Firewall rules reference
    • Frequently Asked Questions
  • CloudAPI Documentation
    • Getting Started
    • RBAC: Users, Roles & Policies
    • API Introduction
    • API Details
      • Account
      • Keys
      • Users
      • Images
      • Instances
      • Packages
  • Contacting Support
  • Images
    • Linux
      • CentOS
      • Ubuntu
        • 20.04
      • Debian
    • FreeBSD
      • 12
Powered by GitBook
On this page
  • Virtual machines
  • Machine resizing

Was this helpful?

  1. Instances

Virtual machines

PreviousInfrastructure containersNextSnapshots

Last updated 5 years ago

Was this helpful?

Virtual machines

MNX virtual machines (VMs) are hardware virtual machines (HVMs) wrapped in highly secure zones, supporting a variety of images including Linux, FreeBSD, Windows, and Docker Engine. They offer a solution for a wide variety of applications that have certain operating system dependencies or applications that can't be run in a containerized environment. Triton offers support for these applications via hardware virtualization but there are some differences between infrastructure containers and virtual machines to be aware of.

Infrastructure containers run on top of a bare metal hypervisor. They do not run a separate guest OS, resulting in better performance, scalability, and stability than a hosted hypervisor. All VMs get the same high performance networking stack, regardless of the instance type or size.

Live resizing of HVM instances is not supported today. Infrastructure containers can be resized to add memory, CPU, and disk space without rebooting, but the nature of hardware virtualization does not allow that convenience today.

Machine resizing