No. We provide the bare metal hardware and the installation capability. VMware ESXi is a proprietary software. You can install the Free Hypervisor version (which has some limitations) or Bring Your Own License (BYOL) if you have a commercial vSphere entitlement. This gives you maximum flexibility and avoids "renting" a license at a markup.
Once installed, you can access the VMware Host Client via any web browser (Chrome/Firefox) using your server's public IP address. From this graphical interface, you can create VMs, assign networking, and monitor performance.
Yes! This is one of our key strengths. During checkout or via a support ticket, you can order additional IP blocks (e.g., a /29, /28, or even a /24). You can then assign these static public IPs directly to your virtual machines inside the vSwitch configuration.
Yes. Our hardware supports IOMMU (PCI Passthrough). If you order a server with a GPU, you can configure ESXi to pass that GPU directly to a specific VM, which is ideal for VDI (Virtual Desktop Infrastructure) or AI workloads inside a virtualized environment.
No. We manage the hardware, network, and power (keeping the lights on). You are responsible for the hypervisor configuration and the Operating Systems (Windows/Linux) running inside your VMs. This is an unmanaged service designed for IT professionals.
The free version (vSphere Hypervisor) is powerful but has restrictions designed for labs, not enterprise clusters.
- No vCenter Server: You cannot manage multiple servers from a single pane of glass.
- No vMotion: You cannot live-migrate VMs between servers.
- API Read-Only: Many backup tools (like Veeam) require a paid license to access the storage API for automated backups.
For standalone production servers, the free version is often sufficient. For clusters and automated backups, we recommend applying a paid Essentials or Standard license.
This is a common configuration for hosting providers. When you order a dedicated IP block (e.g., /29) from ServerMO:
- Log in to your vSphere Host Client.
- Go to Networking > Virtual Switches
- Ensure your VMs are connected to the main "VM Network" port group.
- Inside the VM's OS (Windows/Linux), manually configure the static network adapter settings using the IP, Gateway, and Subnet Mask we provide. You do not need to create separate vSwitches for each IP; they can exist on the same physical uplink.
Yes. Our motherboards and CPUs support Intel VT-d / AMD-Vi (IOMMU). This allows you to bypass the hypervisor and give a VM direct access to a physical hardware component.
- GPU Passthrough: Essential for VDI, AI/ML models, or transcoding inside a VM.
- NIC Passthrough: Useful for virtualized firewalls (pfSense/OPNsense) to get line-rate network performance.
Since this is an unmanaged bare metal server, you are responsible for backups. Common strategies include:
- Veeam Backup & Replication: The industry standard (requires a paid ESXi license).
- GhettoVCB: A popular free script for automated snapshot backups on free ESXi hosts.
- OVF Export: Manually exporting VMs to your local machine for cold storage.
We highly recommend ordering a secondary large HDD (e.g., 4TB) specifically to store local backups.
Yes. All our CPUs have hardware virtualization extensions (VT-x/EPT or AMD-V/RVI) enabled in the BIOS. This allows you to run a hypervisor inside a VM. This is extremely popular for Home Labs and Training Environments where you want to simulate a multi-host cluster or test vMotion configurations without buying multiple physical servers.
