On Tue, Sep 16, 2014 at 02:43:08PM -0000, Serge Hallyn wrote:
> Seems like the best thing would be to move qemu-system-x86.qemu-
> kvm.upstart to qemu-system-common.qemu-kvm.upstart (and same with
> .default and .init) and have the jobs check for the right architectures.
Note that currently qemu-system-x86 ships an init script named
qemu-system-x86 and an upstart job named qemu-kvm. These need to be made
consistent. On Ubuntu, we're currently running *both* of them at boot time.
I'm not convinced that it's better to name it qemu-kvm and put it in a
common package, than to have each native arch-specific package to ship its
own. These startup scripts are dead weight on other architectures, better
to optimize them out at package build time.
On Tue, Sep 16, 2014 at 02:43:08PM -0000, Serge Hallyn wrote: x86.qemu- common. qemu-kvm. upstart (and same with
> Seems like the best thing would be to move qemu-system-
> kvm.upstart to qemu-system-
> .default and .init) and have the jobs check for the right architectures.
Note that currently qemu-system-x86 ships an init script named
qemu-system-x86 and an upstart job named qemu-kvm. These need to be made
consistent. On Ubuntu, we're currently running *both* of them at boot time.
I'm not convinced that it's better to name it qemu-kvm and put it in a
common package, than to have each native arch-specific package to ship its
own. These startup scripts are dead weight on other architectures, better
to optimize them out at package build time.