[Pkg-libvirt-maintainers] Bug#783106: lxc container does not start automatically

[Nikolay Shaplov]

В письме от 30 апреля 2015 08:50:04 пользователь Guido Günther написал:
> On Wed, Apr 29, 2015 at 06:53:59PM +0300, Nikolay Shaplov wrote:
> > В письме от 29 апреля 2015 08:01:24 пользователь Daniel Baumann написал:
> > > Hi,
> > > 
> > > could you reproduce it without libvirt?
> > 
> > I've commented out all lxc.network.* options, and container started
> > successfully on reboot.
> > 
> > But I still think this is a bug. Because 1. It does not give any
> > reasonable
> > description in error log 2. It should work. I far as I can get libvrt is a
> > valid tool for this task, it is described in debian's wiki, and I see no
> > reason why it should not be used in start on boot case. Boot script should
> > be fixed.
> 
> I don't see what libvirt could do here. From the report it seems
> 
> * lxc is lacking error reporting
> * doesn't wait for libvirt to come up - it's debatable wether this would
>   be a good thing
Yeah, that's exactly what I am trying to say ;-)

> 
> I would totally agree that libvirt has a bug if the lxc container would
> be libvirt managed (via lxc://) but this isn't the case.
> Cheers,
>   -- Guido
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20150430/c4c56c38/attachment.sig>