i tried just for the fun to se how well a kvm/vm would perform on a directory mounted on tmpfs, ohh my it is fast.
i am seeing - almost 7gb write and read speeds.
to overcome the non persistent nature of ram i i have configured proxmox to make a backup on a persistent disk every night. When a reboot occurs, it is just a matter of restoring the most current backup to tmpfs, in this setup i is possible to lose a day in the vm but for this setup i this is not a concern. the benefit of having a vm that fast and not be prone to disk overload is a massive win from my point of view.
This made me think about a lxc container that runs in tmpfs. is that even possible with the nature of lxc ?
i tried in the same directory but i get a error message when creating the container, but in containers there is no way to set writeback or similar that is key for making it work with kvm.?
Creating journal (16384 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/16
Warning, had trouble writing out superblocks.TASK ERROR: command 'mkfs.ext4 -O mmp -E 'root_owner=0:0' /mnt/ramdrive//images/100/vm-100-disk-1.raw' failed: exit code 144
i am seeing - almost 7gb write and read speeds.
to overcome the non persistent nature of ram i i have configured proxmox to make a backup on a persistent disk every night. When a reboot occurs, it is just a matter of restoring the most current backup to tmpfs, in this setup i is possible to lose a day in the vm but for this setup i this is not a concern. the benefit of having a vm that fast and not be prone to disk overload is a massive win from my point of view.
This made me think about a lxc container that runs in tmpfs. is that even possible with the nature of lxc ?
i tried in the same directory but i get a error message when creating the container, but in containers there is no way to set writeback or similar that is key for making it work with kvm.?
Creating journal (16384 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/16
Warning, had trouble writing out superblocks.TASK ERROR: command 'mkfs.ext4 -O mmp -E 'root_owner=0:0' /mnt/ramdrive//images/100/vm-100-disk-1.raw' failed: exit code 144
Last edited: