[Pkg-libvirt-maintainers] Bug#598149: Bug#598149: libvirt-bin: autostart fails on reboot

Guido Günther agx at sigxcpu.org
Mon Sep 27 11:20:34 UTC 2010


On Mon, Sep 27, 2010 at 12:55:18PM +0200, Jean-Louis Dupond wrote:
> 
> On Mon, 27 Sep 2010 11:56:15 +0200, Guido Günther <agx at sigxcpu.org> wrote:
> > So the permissions stay the same when checked from within the init
> > script and after the boot completed?
> > 
> > Does setting /dev/net/tun to 0666 in the init script before libvirt
> > starts change anything?
> > 
> > Cheers,
> >  -- Guido
> 
> Did some more testing now:
>                 /bin/ls -la /dev/net/tun > /root/boot
>                 /sbin/ifconfig >> /root/boot
>                 /bin/chmod 0666 /dev/net/tun
>                 /bin/ls -la /dev/net/tun >> /root/boot
>                 start-stop-daemon --start --quiet --pidfile $PIDFILE \
>                         --exec $DAEMON -- $libvirtd_opts
Thanks a lot for your testing!

> 
> 
> On reboot, the permissions:
> crw-rw---- 1 root uml-net 10, 200 Sep 27 12:48 /dev/net/tun
> 
> Afterwards it lists all the tap devices correctly.
> They are up.
> 
> Then I chmod /dev/net/tun:
> crw-rw-rw- 1 root uml-net 10, 200 Sep 27 12:48 /dev/net/tun
> 
> 
> And what do I see, the guests started without problems :)
So the issue isn't in libvirtd-bin - it's a permission problem when
using uml-utilties. There's one open question though (as stated in my
previous mail):

How do the permissions on your system look like when the system is fully
booted (and you revert your changes in /etc/init.d/libvirt-bin)?

(since you said you can then start your guests without problems too).
Cheers,
 -- Guido





More information about the Pkg-libvirt-maintainers mailing list