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

[Guido Günther]

tag 598149 +unreproducible
thanks

On Mon, Sep 27, 2010 at 01:28:37PM +0200, Jean-Louis Dupond wrote:
> 
> On Mon, 27 Sep 2010 13:20:34 +0200, Guido Günther <agx at sigxcpu.org> wrote:
> > Thanks a lot for your testing!
> > 
> > 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
> 
> 
> Ok I removed the changes again in the init.d.
> 
> Permission @ boot:
> crw-rw---- 1 root uml-net 10, 200 Sep 27 13:24 /dev/net/tun
> 
> 
> The tap devices again created without issues.
> But again:
> 
> Sep 27 13:25:03 cloud libvirtd: 13:25:03.027: error :
> qemudReadLogOutput:2118 : internal error Process exited while reading
> console log output: char device redirected to /dev/pts/1#012could not open
> /dev/net/tun: Permission denied#012
> Sep 27 13:25:03 cloud libvirtd: 13:25:03.027: error :
> qemuAutostartDomain:827 : Failed to autostart VM 'dupondje': internal error
> Process exited while reading console log output: char device redirected to
> /dev/pts/1#012could not open /dev/net/tun: Permission denied#012
> 
> 
> Without any change I do:
> cloud:~# /etc/init.d/libvirt-bin restart
> Restarting libvirt management daemon: /usr/sbin/libvirtd.
> 
> And the guest devices are started without any permission error...

So your vm autostarts either when

- fixing the /dev/net/tun permissions to 0666 - everything fine here - I
  understand that.

or

- when restarting libvirtd after the boot - I don't understand that one.

* Are you using cgroups (though this shouldn't change anything about the
  device permissions)?
* Any chance there's another self compiled libvirtd around that could get
  picked up?

When I try to reproduce your problem here it's 100% consistent: the
device comes up with 0640 and the vm won't start. After restarting
libvirtd the device is still 0640 and the vm still won't start (as
expected). When I change the permissions of /dev/net/tun to 0666
everything works fine and the vm gets autostarted on daemon restart.

Could you doublecheck the permissions of /dev/net/tun when the vm runs?
Cheers,
 -- Guido