Skip to main content

jumping on the virtualisation bandwagon

Is virtualisation the next wave of true computing or just the recent hype that technologist are throwing at system buyers? Why are we all jumping to believe that its the way things should be implemented now? Back to the earlier post, less than 2 years ago, open source and linux wasn't a viable option and now it is. Virtulisation isn't mature technology, if youre talking about pseudo virtualisation, then maybe, but definately not on the enterprise level.

So what makes virtualisation more popular than open source, or have we learnt from our mistakes and suddenly willing to take any risks? I think its commercialisation as in how much money can you make from it. Industry is still driven by vendors isn't it?

Mature commercial virtualisation has massive overheads. A couple of examples is that it does not handle resources effectively as what essentially happens is that you are running one operating system on top on another.

To get things into perspective of system performance, you might have heard of embedded system. These are scaled down no nonsense operating systems that do only what they are built to do only. these lean mean simple machines may have limited functionality, but do these functions really quick.

The proportional speed chart is as follows (not considering hardware speed)

Fast -> Usable -> Sloppy
Embedded OS -> tweaked operating system -> default operating system

So what happens when you run another OS on top of a default operating system? you get a really ineffective machine isn't it?

This is probably how most people will deploy virutalisation to production.

layer 4 - Production Application
layer 3 - Guest Operating System
layer 2 - Virtual Application Layer
layer 1 - Default Host Operating System

So far, we only mentioned performance and not even talked about other potential risks like resource contention, but of course, your vendor has already mentioned that unlike other products, ours is safe.

If you want to learn more about virtualisation, read "Xen and the art of virtualisation". Doesn't the title just grab you? Warning, its open source. It talks about the maturity of current solutions and highlights the risks involved

Now for my beloved home user readers. How can virtulisation benefit them? Here are some people I would suspect will enjoy running a virtual machine on their home computers

a. Hobbists and enthuisasts
b. People who do not have a whole lot of strange perliherals
c. People frustrated with windows
d. people who have some strange habit of destroying their operating system, start using virtual ones and make copies
e. do you have kids? refer to point d.
f. bored people, you reading this aren't you
g. wannabe geeks

Comments

Aaron Lee said…
I wanna virtual gameboy to run on PC!

btw, youz still getting spam.
Melven said…
You will need a game boy emulator that runs on PC.

Can't help with the spam these days other than deleting them

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…