[Pkg-libvirt-maintainers] Bug#540018: Bug#540018: closed by Guido Günther <agx at sigxcpu.org> (Re: Bug#540018: libvirt-bin: net-autostart lies about marking network as auto-started)

[Guido Günther]

On Sat, Aug 08, 2009 at 10:17:14AM +0200, Tollef Fog Heen wrote:
> ]]  (Debian Bug Tracking System)
> 
> | > libvir: Network Config error : cannot create bridge 'virbr0': Operation not permitted
> | > 09:29:20.778: warning : remoteReadConfigFile:2569 : Cannot set group when not running as root
> | > Welcome to virsh, the virtualization interactive terminal.
> | > 
> | > Type:  'help' for help with commands
> | >        'quit' to quit
> | > 
> | > virsh # net-autostart default
> | > Network default marked as autostarted
> | 
> | This way you're accessing qemu://sesson not qemu:///system so autostart
> | networking can never work. But virsh should of course tell you so, it
> | does with 0.6.5:
> 
> So networks are shared between session and system buses?
No. qemu:///session only uses user mode networking since you don't have
the necessary privileges to create the tap/bridge devices.

> If so, why is it marked as inactive (but autostarted) on the session
> bus and active (and autostarted) on the system bus?
qemu:///session and qemu:///system are completely independent. You can
e.g. have vms with the same name on qemu:///session and qemu:///system
(autostarted or not). They don't share anything.
Cheers,
 -- Guido