TemplateImplementation changed

StandaloneVM
This commit is contained in:
Marek Marczykowski-Górecki 2011-09-15 20:53:34 +00:00
parent 0e6672f706
commit 1bcff32dfb

View File

@ -98,3 +98,10 @@ volatile.img is divided into two partitions:
2. swap partition 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. 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.