| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
To boot a nested guest in juno, we need to relocate the virtualization
type config setting into the [libvirt] section.
With this, we can sucessfully launch a guest.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
| |
We expose the libvirt_type config setting with a default value of 'kvm', but
for nested virtualization configurations, we also provide a bbappend that
will modify the value to 'qemu' automatically.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
| |
Without renaming the bbappend, our configuration will fail to launch in a
virtualized environment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Since we can't count on package postinst order, many components check for
a configured postgresql daemon, and if not found, initialize it.
Rather than sprinkling the knowledge of how to initialize the database
through all these packages, we create a more robust, central postgresql-init
script, and call it when any component needs the database configured.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
When included in a build, this layer modifies settings to allow a controller
and compute node boot and runtime under qemu system emulation.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
