TinyKVM - part 2 - (almost) a month later
Follow-up from part 1.
- 0 downtime so far.
- 7GB promised = 7GiB (NB. GiB not GB)
- provider added support for netboot.xyz a few minutes after request.
- very nice to have console access via noVNC
- not so nice that OS reinstall really means it: the VM is destroyed and recreated. This means that I cannot use a recovery ISO of any kind on my own. Bummer. Would be nice to have an option to boot one of the recovery CDs without VM destruction. NB. There may be a way to do it that I could not see. If yes, looking forward to learning about it (and updating this review).
- to overcome point above I installed a second Debian copy exclusively for recovery. The bad news is that ate 2 GiB.
- I already wrote this in part 1 but it bears repeating because it is important to me: supplied IPv4 is clean.
- the VM comes with empty disk (not even partitioned), you boot into OS install disk. Much nicer than having a minimal install that you have no control on and that prevents you from partitioning the disk as you like. Saves time because you do not have to either trust supplier to provide a clean install (I do not as a general policy) or to manually check/validate it.
Part 3 will come after a few more months :-)
FYI, I run exim4, fail2ban, lighttpd and mariadb on a zfs root on this 256MB machine and backup it offsite daily using znapzend (and already recovered it once after a screw-up - just recreated the pool, dumped the backed-up filesystems on it, installed grub and booted). :-)