From 1bcff32dfb0e99c9adf99bafb9ead12d4b83191d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?=
 <marmarek@invisiblethingslab.com>
Date: Thu, 15 Sep 2011 20:53:34 +0000
Subject: [PATCH] TemplateImplementation changed

StandaloneVM
---
 TemplateImplementation.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/TemplateImplementation.md b/TemplateImplementation.md
index d67a1dea..5c40ed64 100644
--- a/TemplateImplementation.md
+++ b/TemplateImplementation.md
@@ -98,3 +98,10 @@ volatile.img is divided into two partitions:
 2.  swap partition
 
 Inside of an AppVM, the root device is wrapped by the snapshot in the first partition of volatile.img. Therefore, the AppVM can write anything to its filesystem - however, such changes will be discarded after a restart.
+
+StandaloneVM
+------------
+
+Standalone VM enables user to modify root filesystem persistently. It can be created using *--standalone* switch to *qvm-create*.
+
+It is implemented just like TemplateVM (has own root.img connected as R/W device), but no other VMs can be based on it.