Kernel-based Virtual Machine (KVM) is a virtual machine implementation using the operating system's kernel. This often allows for greater performance than when using virtual machine solutions which rely on user-space drivers.
Upon provisioning you'll have the option of either installing from a template or doing a manual install by ISO.
We recommend the templates whenever possible as they will include the latest updates and are slimmed down quite a bit.
- Log in to the Stallion Control Panel
- Click on the VPS you wish to set up
- Click “Reinstall” at the top
- Pick the template of choice and click the “Reinstall” button
Linux-based templates will prompt you for a password.
Windows-based templates will be syspreped and will ask you to setup an adminstrator user.
You must load the console and finish setup. You will also have to enable remote desktop from the Computer Properties page.
Some operating systems are walled off depending on how much memory you have.
Templates can help get around some of these limits since, for instance, CentOS will request 256MB+ RAM during installation but will only use < 20MB when bootup. For CentOS you will need to use a template.
To run Windows Server 2012 or higher you need at least a 1GB Slice or higher.
DHCP is hit or miss with KVM, if your networking fails to setup automatically please use the following information to configure it manually:
- Netmask: 255.255.255.0
- Gateway: x.x.x.1 (x.x.x being the first 3 parts of your main IP.)
- Las Vegas Resolver #1: 184.108.40.206
- Las Vegas Resolver #2: 220.127.116.11
- New York Resolver #1: 18.104.22.168
- New York Resolver #2: 22.214.171.124
- Luxembourg Resolver #1: 126.96.36.199
- Luxembourg Resolver #2: 188.8.131.52
Here is a Debian example using ifupdown2:
auto eth0 iface eth0 inet static address 184.108.40.206 netmask 255.255.255.0 gateway 220.127.116.11
- Gateway: 2605:6400:20::1
- Netmask: /48
Example configuration for Debian using ifupdown2 in Las Vegas
iface eth0 inet6 static address YOUR_IPV6_ADDRESS_HERE netmask 48 gateway 2605:6400:20::1
- Gateway: 2605:6400:10::1
- Netmask: /48
Example configuration for Debian using ifupdown2 in New York
iface eth0 inet6 static address YOUR_IPV6_ADDRESS_HERE netmask 48 gateway 2605:6400:10::1
- Gateway: 2605:6400:30::1
- Netmask: /48
Example configuration for Debian using ifupdown2 in Luxembourg
iface eth0 inet6 static address YOUR_IPV6_ADDRESS_HERE netmask 48 gateway 2605:6400:30::1
- Gateway: 2605:6400:40::1
- Netmask: /48
Example configuration for Debian using ifupdown2 in Miami
iface eth0 inet6 static address YOUR_IPV6_ADDRESS_HERE netmask 48 gateway 2605:6400:40::1
- Choose Intel PRO/1000 as the NIC in the VPS panel, and then once the OS is installed make sure to upgrade the intel ethernet driver to the latest Intel PRO/1000MT driver from intel.com
Intel E1000 NIC Drivers
- Drivers for the e1000 Virtual NIC can be downloaded via intel.com
- Drivers for the e1000 Virtual NIC are also available via the Intel E1000 Driver CD, please use these only if you are unable to download the latest drivers via the URL above as these are only meant to enable internet access if you are otherwise unable to.
Please set reasonable Pagefile/Swap sizes as excessive IO caused by abusing these will result in suspension, repeated abuse will result in termination without credit nor refund.
Poor Disk Performance
You may be unsatisfied or have noticed poor I/O performance due to the fact that all KVM based VPS are provisioned with IDE based disks by default, this is required as not all OS play well with the VIRTIO BUS, namely Windows.
The VIRTIO driver floppy is automatically mounted with your VPS during bootup time so be sure to select the drivers off this disk when installing Windows.
Poor Network Performance On Linux
If your virtual server has 512MB RAM you'll likely suffer poor network performance due to strict default buffer sizes.
To get around this please add the follow to your /etc/sysctl.conf
net.core.rmem_max=16777216 net.core.wmem_max=16777216 net.ipv4.tcp_rmem=4096 87380 16777216 net.ipv4.tcp_wmem=4096 65536 16777216
Once you're done this be sure to
sysctl -p to apply it.
These settings will automatically apply during restarts so you shouldn't need to cron/script anything else