English UK Deutsch Español

high availability, redundant kvm vserver (linux KVM) linux and windows

KVM VServer Video
Linux KVM

kvm vserver configurator

suggested configs

1 - 4

512MB - 4GB

10GB - 500GB

1 IP address*

0.90 €

additional ip space available according to ripe policies

you can select other CD-images via our webinterface such as OpenSuSE, Red Hat Fedora, Gentoo, Ubuntu and even *BSD or Windows 2008 Server R2

bandwidth

1GBit/s

1000 GB / Traffic

setup: no setup fee! 0,00 €
total per month:

Start KVM VServer trial NOW - 12 hours for FREE - with INSTANT ACCESS!

smart-kvm benefits

  • SSD cached Storage
  • Intel Xeon >=2.5 GHz CPUs
  • faulttolerant ECC RAM
  • Windows and Linux support
  • nested KVM (KVM inside KVM) support
  • redundant HA storage pool
  • redundant host servers
  • adaptive load balancing in the cluster
  • rescuesystem via webinterface
  • boot CD image via webinterface
  • reinstall via webinterface
  • install other operating systems
  • remote console via webinterface
  • reset, start and stop via webinterface

test us now!

Try out our KVM vserver now! You can test our vserver for 12 hours for free. You only have to register an account. You will receive your account and login data appr. 3 mins after registration. After 12 hours of usage we will stop the vserver. This vserver is then preserved for you for the next 12 hours. If you decide to rent this vserver, it will be immediatelly put back on for you after the payment has been received.

How we provide virtual servers

1. This is our running setup. Our servers use the network-raid like ceph storage system to provide disk-storage to the virtual servers. Your virtual server can be started on any node of our cluster, and even can live migrate to another node.
2. If we have to do maintainance work on a node, the node is going standby. Your virtual server is then being migrated to another node. Now we start our maintaince.
3. As soon as we finished maintainance, the node will become online again and the load in the cluster is distributed.
4. In case of hardware failure a node can go offline without migrating your virtual server.
5. Our system detects this and starts your virtual server on a different node immediatelly.
6. When the bad node has been replaced, load will be balanced again.
7. It may be that many users create or modifiy virtual servers in the cluster on some nodes.
8. Our systems detects the load increase and balances the load again. When the load is getting to high, we add more nodes to the cluster.