Re: [qubes-users] bind-dirs configuration not persisting to dvm
On 8/20/20 9:06 AM, 'awokd' via qubes-users wrote: Qubes: I have an appVM that I changed into a dvm template, but I need to increase the size of tmpfs /run/user/1000 from the default 10% of memory size to e.g. 40% when an application in the dvm is opened (and the disp gets created). To do this I edited /etc/systemd/logind.conf in the appVM and changed RuntimeDirectorySize=40%. To make this stick between reboots, I used bind-dirs. If I reboot the appVM and look at 'df -h' and 'cat /etc/systemd/logind.conf' I can see that my changes have persisted. The problem is after I change my appVM into a dvm template, 'qvm-prefs template_for_dispvms True' in my dvm 'tmpfs /run/user/1000' is at default 10%, 'df -h' confirms. And my customization to '/etc/systemd/logind.conf' is not there. However, 'cat /rw/bind-dirs/etc/systemd/logind.conf' still shows user@disp9640:~$ cat /rw/bind-dirs/etc/systemd/logind.conf RuntimeDirectorySize=40% Is that a bug or does that have something to do with how and when '/rw/config/qubes-bind-dirs.d/50_user.conf' is parsed? because this is where '/etc/systemd/logind.conf' is binded. To simplify the problem a bit, maybe use a different template for your dvm template and edit /etc/systemd/logind.conf directly in the base template? That works. It also works in the appVM before I set it to be a dvm, but it does not address the root cause. The issue described is only applicable to dvm's, but I have not found any documentation or anywhere else online for that matter indicating that bind-dirs are not compatible with dvm's. AFAIK it should work in the dvm exactly as it does in the appVM. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/81277a33-c964-f990-b7b1-642de334af97%40ak47.co.za.
Re: [qubes-users] bind-dirs configuration not persisting to dvm
Qubes: > I have an appVM that I changed into a dvm template, but I need to > increase the size of tmpfs /run/user/1000 from the default 10% of memory > size to e.g. 40% when an application in the dvm is opened (and the > disp gets created). > > To do this I edited /etc/systemd/logind.conf in the appVM and changed > RuntimeDirectorySize=40%. > > To make this stick between reboots, I used bind-dirs. > > If I reboot the appVM and look at 'df -h' and 'cat > /etc/systemd/logind.conf' I can see that my changes have persisted. > > The problem is after I change my appVM into a dvm template, 'qvm-prefs > template_for_dispvms True' in my dvm 'tmpfs /run/user/1000' is > at default 10%, 'df -h' confirms. And my customization to > '/etc/systemd/logind.conf' is not there. > > However, 'cat /rw/bind-dirs/etc/systemd/logind.conf' still shows > > user@disp9640:~$ cat /rw/bind-dirs/etc/systemd/logind.conf > RuntimeDirectorySize=40% > > Is that a bug or does that have something to do with how and when > '/rw/config/qubes-bind-dirs.d/50_user.conf' is parsed? because this is > where '/etc/systemd/logind.conf' is binded. > To simplify the problem a bit, maybe use a different template for your dvm template and edit /etc/systemd/logind.conf directly in the base template? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc1d1326-a3f2-3cda-225a-4b4b688dcd74%40danwin1210.me.
[qubes-users] bind-dirs configuration not persisting to dvm
I have an appVM that I changed into a dvm template, but I need to increase the size of tmpfs /run/user/1000 from the default 10% of memory size to e.g. 40% when an application in the dvm is opened (and the disp gets created). To do this I edited /etc/systemd/logind.conf in the appVM and changed RuntimeDirectorySize=40%. To make this stick between reboots, I used bind-dirs. If I reboot the appVM and look at 'df -h' and 'cat /etc/systemd/logind.conf' I can see that my changes have persisted. The problem is after I change my appVM into a dvm template, 'qvm-prefs template_for_dispvms True' in my dvm 'tmpfs /run/user/1000' is at default 10%, 'df -h' confirms. And my customization to '/etc/systemd/logind.conf' is not there. However, 'cat /rw/bind-dirs/etc/systemd/logind.conf' still shows user@disp9640:~$ cat /rw/bind-dirs/etc/systemd/logind.conf RuntimeDirectorySize=40% Is that a bug or does that have something to do with how and when '/rw/config/qubes-bind-dirs.d/50_user.conf' is parsed? because this is where '/etc/systemd/logind.conf' is binded. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d651ef98-0003-72b1-3440-0bda5114c202%40ak47.co.za.
