On Wed, Dec 06, 2017 at 01:56:23PM +0100, Cedric Bosdonnat wrote:
> On Tue, 2017-12-05 at 16:52 +, Daniel P. Berrange wrote:
> > On Tue, Dec 05, 2017 at 10:53:17AM +0100, Cédric Bosdonnat wrote:
> > > libvirt-sandbox-init-common is expecting -d and -v parameters to
> > > set it in debug or
On Tue, 2017-12-05 at 16:52 +, Daniel P. Berrange wrote:
> On Tue, Dec 05, 2017 at 10:53:17AM +0100, Cédric Bosdonnat wrote:
> > libvirt-sandbox-init-common is expecting -d and -v parameters to
> > set it in debug or verbose mode... but those will never be passed
> > by the launcher program.
>
On Tue, Dec 05, 2017 at 10:53:17AM +0100, Cédric Bosdonnat wrote:
> libvirt-sandbox-init-common is expecting -d and -v parameters to
> set it in debug or verbose mode... but those will never be passed
> by the launcher program.
Hmm, libvirt-sandbox-init-{qemu,lxc} both know how to pass -d
to
libvirt-sandbox-init-common is expecting -d and -v parameters to
set it in debug or verbose mode... but those will never be passed
by the launcher program.
Writing the core.debug and core.verbose parameters in the sandbox
configuration makes those values actually usable from the init.
---
