smileyworld Posted March 27, 2021 Share #1 Posted March 27, 2021 Does anyone know a workaround for this? The same spk runs fine in 6.2.3 Quote Link to comment Share on other sites More sharing options...
1 IG-88 Posted March 27, 2021 Share #2 Posted March 27, 2021 (edited) if you want to try it yourself DSM_Developer_Guide_7_0_Beta.pdf page 64 Privilege DSM 7.0, packages are forced to lower the privilege by applying privilege mechanism explicitly. To reduce security risks, package should run as an user rather than root . Package can apply such mechanism by providing a configuration file named pivilege : With the configuration, package developer is capable to Control default user / group name of process in scripts Control permission of files in package.tgz Control file capabilities in package.tgz Control if special system resources are accessible Control group relationship between packages To overcome the limitation that normal user cannot be used to do privileged operations, we provide a way for package to request system resources. Please refer to Resource for more information. Setup privilege configuration Just create a file at conf/privilege with prefered configuration. { "defaults": { "run-as": "package" } } DSM_Developer_Guide_6_0.pdf page 104 to compare with Edited March 27, 2021 by IG-88 1 Quote Link to comment Share on other sites More sharing options...
0 smileyworld Posted March 29, 2021 Author Share #3 Posted March 29, 2021 (edited) Unfortunately my problem starts one hop earlier. I asked this question because I want to have a VM which is connected via VPN and is able to run another (Virtualbox) VM in it. So basically what I need is nested virtualization. Has anyone got this working in DSM? I tried it with VMM from Synology and Virtualbox but no matter which operating system I use as soon as I try to add a VM in virtualbox in the nested VM I get this message: "Invalid Settings Detected" System : Acceleration page On the host (DSM 6.2) cat /sys/module/kvm_intel/parameters/nested is giving me "N" as answer, which means nested VMs are not activated but unloading the module modprobe -r kvm_intel and editing/activating the nested feature didn't work # modprobe kvm_intel nested=Y Any ideas? Edited March 29, 2021 by smileyworld Quote Link to comment Share on other sites More sharing options...
0 smileyworld Posted July 24, 2022 Author Share #4 Posted July 24, 2022 Found the answer on synology's website for my original problem. You need the pro version for nested VMs. If anyone needs it, here is the documentation. Quote Link to comment Share on other sites More sharing options...
Question
smileyworld
Does anyone know a workaround for this? The same spk runs fine in 6.2.3
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.