search for: d8c16482496875afc0d37b181487ae46r1

...ke this a single action? Here is how we handled this: * The code for register: https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 * The configuration file that we adopted as a default: https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-d8c16482496875afc0d37b181487ae46R1 3) When using libvirt it changes the owner of our image If we try to use libvirt, it changes the ownership of our QEMU images (root). We fixed it by changing the file “/etc/libvirt/qemu.conf”, and switch the option dynamic_ownership to “0”. What is the impact of that change? Is it dangerous? Ther...

...handled this: > > * The code for register: > > https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 > > * The configuration file that we adopted as a default: > > https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-d8c16482496875afc0d37b181487ae46R1 > > > > 3) When using libvirt it changes the owner of our image > > > > If we try to use libvirt, it changes the ownership of our QEMU images > > (root). We fixed it by changing the file “/etc/libvirt/qemu.conf”, and > > switch the option dynamic_ownership to “...

...eds. >Here is how we handled this: >* The code for register: >https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 >* The configuration file that we adopted as a default: >https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-d8c16482496875afc0d37b181487ae46R1 > >3) When using libvirt it changes the owner of our image > >If we try to use libvirt, it changes the ownership of our QEMU images >(root). We fixed it by changing the file “/etc/libvirt/qemu.conf”, and >switch the option dynamic_ownership to “0”. What is the impact of that >c...