When you need something fast and reliable, but don't want the hassle of building a cloud environment.
Usually, VMs are provisioned within a minute or two. Windows images can take a bit longer since they are larger than Linux images. In addition, Windows performs the sysprep process upon first boot, so that can take a couple minutes. An email is sent when the order is placed. Another email is sent when the VM has been provisioned. For Windows VMs, wait a couple more minutes for the sysprep process to finish.
Our Intel servers (AMD EPYC will be available mid-2020) have hyperthreading disabled to mitigate MDS and other vulnerabilities.
We have all current mitigations in place, including disabling hyperthreading and the latest microcode, deployed by the latest BIOSes for our servers. All mitigations checked by https://github.com/speed47/spectre-meltdown-checker are reported as mitigated.
Yes, as long as you have configured the appropriate firewall rules. We suggest you restrict traffic so you only accept traffic from your own VMs' private IPs to reduce the chance that another client's VMs can talk to your VMs.
We charge for all outbound data transfers originating from your VM, regardless of where that traffic is headed. We have a very low data transfer price, so typically data transfer charges are minimal, including those for Internet-bound traffic.
All VMs are created on the same network, which is behind 1:1 NAT to your public IP. So, every VM is assigned a private IP which is translated to a public IP when traffic is sent outbound to the Internet, and vice-versa when traffic is sent inbound from the Internet. VMs can talk to each other on the private network as long as you have appropriate firewall rules configured. IP and MAC addresses are filtered, so spoofing either is impossible.
We do enable this capability in the hypervisor, but we can not support this since there are too many factors that can go wrong. So, we suggest you use this only for testing for DR environments where nested hypervisors is an absolutely necessity.
No - boot disks are volumes on our replicated NVMe storage, so if a physical server dies at Genesis, your data is not lost.
Yes! If you don't like your purchase for any reason, within 24 hours of the purchase, we will refund your purchase. Terms and conditions apply, however. If we find that the machine was used for any form of abuse, you will waive your right to a refund.
Not with Genesis VMs, unfortunately. We do support reverse DNS with our Genesis Public Cloud service.
Not with Genesis VMs, unfortunately. We do support Jumbo Frames with our Genesis Public Cloud service.
When ordering, you specify a backup count limit. After provisioning, you can enable and specify a schedule for the backups, such as every 2 hours. When the backup count is reached, the oldest backup is deleted before a new backup is performed. We charge a flat fee for each backup, which is metered every hour, so if you decide to change the backup limit, or disable and delete backups, you will only be charged for what you use. For file-level backups, please see Genesis Backup.
VMs can only be upgraded such that the storage is the same size or large due to the fact that block storage devices can't be resized smaller. Upgrades must be performed by submitting a ticket. We will simply charge the difference in cost pro-rated.
Genesis VMs are provisioned as VMs on our OpenStack Public Cloud platform, which is connected via redundant 100Gbps links to each compute node. Network bandwidth is restricted based on the Flavor of VM selected and ranges anywhere from 25Mbps up to 40Gbps. See our specifications page for flavor definitions.
Genesis VMs is paid in advance every month, due on the 1st of each month. Backups and egress data transfer charges are paid in-arrears and appear on the invoice following the service period.
Yes, but we would need to evaluate the scope of work required for the migration and provide a proposal. Free free to contact us if you have any questions or would like to discuss options.