VM2Cloud VE
VM2Cloud Virtual Environment (VE) runs virtual machines on your own hardware, managed through a web interface. There is nothing to install on the machine you administer it from — a browser is enough.
These guides take a new server from bare metal to a running virtual machine, then cover everything the interface can do.
Start here
Section titled “Start here”| Guide | What it covers |
|---|---|
| Installing VM2Cloud VE | Install onto a new server: disks and storage layout, the management network, bonding and VLANs, first sign-in. |
| Getting around the web interface | The tree, the four views, the menus for each kind of object, and the task panel. |
| Uploading an ISO image | Add operating-system installation media so it can be selected when you build a virtual machine. |
| Creating a virtual machine | Size and create a virtual machine, then install an operating system into it. |
| Containers | Run lightweight Linux services alongside virtual machines. |
Menu reference
Section titled “Menu reference”Every entry in every menu, and what each is for.
| Reference | Covers |
|---|---|
| Datacenter menu | The 20 entries that apply to the whole system. |
| Node menu | The settings for one server. |
| Virtual machine and container menu | Everything about a single guest. |
| Datacenter options | Every cluster-wide default, and the two worth changing on day one. |
Storage and networking
Section titled “Storage and networking”| Guide | What it covers |
|---|---|
| Storage management | Define storages, choose between the types, set content types and retention. |
| Disks and local storage | Disk health, and turning physical disks into pools, volume groups and filesystems. |
| Node network configuration | Bridges, bonds and VLANs — and the staged-changes trap. |
| Software-defined networking | Virtual networks that machines attach to instead of a bridge. |
| Firewall | Rules at datacenter, node and guest level — and how not to lock yourself out. |
Running it in production
Section titled “Running it in production”| Guide | What it covers |
|---|---|
| Backups and restore | Scheduled backup jobs, backup modes, restoring a guest, and how snapshots differ from backups. |
| Clustering and high availability | Join nodes into a cluster and understand quorum. |
| High availability | Protect a machine, control where it runs, and pause HA for maintenance. |
| Replication | Keep a recent copy of a machine on another node. |
| Users, roles and permissions | Give people their own sign-in, scope their access, add two-factor authentication, and issue API tokens. |
| Notifications and monitoring | Make the system tell you when something fails, and keep long-term metrics. |
| Certificates | Replace the browser security warning with a certificate your browser trusts. |
Troubleshooting
Section titled “Troubleshooting”| Guide | What it covers |
|---|---|
| Fixing “Authentication failed! (401)” | One node signs in but another rejects you — almost always node clocks drifting apart. |
Reaching the web interface
Section titled “Reaching the web interface”Every node serves its own web interface on port 8006:
https://<server IP address>:8006On a newly installed server the browser warns that the connection is not private. That is expected — the server starts with a self-signed certificate. See Certificates to replace it.
Sign in with user name root, the administrator password you set during installation, and the
Linux PAM standard authentication realm.
Getting help
Section titled “Getting help”Support is available through the VM2Cloud support portal.