Lines Matching full:on

6 For now, the focus is on VM memory aspects, and not about how to save and
17 VMs. The Copy-On-Write mechanism in the operating systems makes sure that
39 Supply VM RAM via memory-backend-file, with ``share=on`` (modifications go
49         -object memory-backend-file,id=pc.ram,mem-path=template,size=2g,share=on,... \\
58 In order to have a new VM be based on a template VM, we have to
59 configure VM RAM to be based on a template VM RAM file; however, the VM
63 stay private), ``readonly=on`` (open the file readonly) and ``rom=off``
67 In the following command-line example, a 2GB VM is created based on the
73         -object memory-backend-file,id=pc.ram,mem-path=template,size=2g,readonly=on,rom=off,... \\
80 template VM or when starting new VMs based on a template VM.
93 These technologies rely on shared memory, however, the template VMs
118 For VM migration, "x-release-ram" similarly relies on discarding of VM
119 RAM on the migration source to free up migrated RAM, and will
122 Postcopy live migration fails discarding VM RAM on the migration
124 that postcopy live migration usually only works on selected filesystems