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

[Guido Günther]

Hi Jean,
On Sun, Sep 26, 2010 at 11:25:48PM +0200, Jean-Louis Dupond wrote:
> Subject: libvirt-bin: autostart fails on reboot
> Package: libvirt-bin
> Version: 0.8.3-1
> Severity: normal
> 
> I have a routed setup of kvm (with libvirt).
> 
> My tun devices are created in /etc/network/interfaces.
> 
> auto tap0
> iface tap0 inet static
>   address xxx.xxx.xxx.xxx
>   netmask 255.255.255.255
>   tunctl_user libvirt-qemu
>   up route add xxx.xxx.xxx.xxx/32 dev tap0
> 
> But when I reboot my host server, and libvirt starts, it can't start
> the guests.
> I get the following error:
> Sep 21 21:28:51 cloud libvirtd: 21:28:51.046: 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 21 21:28:51 cloud libvirtd: 21:28:51.047: 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
> 
> 
> It seems to fail because the tap0 doesn't exist yet, and libvirt
> tries to make it.
> 
> If I restart libvirt-bin after like 30 seconds, the devices get
> started without any issue.
> So it seems like there is some race condition, that makes
> libvirt-bin start before the network is initialized.
Are you using dependency based booting? Please check if the network is
fully up when libvirt-bin starts (e.g. by dumping the output of
ifconfing in the init script). It should be since we have a dependency
on $network in the init script.
Cheers,
 -- Guido