libvirt users - Feb 2014 - libvirt 1.2.1 / lxc : default virtual network not defined after installing/starting Libvirt

>
> Lets say you want a 2 level hierarchy for the guest from your example
> above. In the libvirt XML you would set the partition name to:
>
>    /machine/dahlia
>
> this corresponds to a systemd slice call  machine-dahlia.slice
>
> If you wanted a third level you'd need to create machine-dahlia.slice
> and also create machine-dahlia-foo.slice, making sure the latter had
> After=machine-dahlia.slice. Then the libvirt name would be listed as
> /machine/dahlia/foo

Got it. Thanks a lot.
> Daniel
> --
> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/
:|
> |: http://libvirt.org              -o-             http://virt-manager.org
:|
> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/
:|
> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc
:|


-- 

google.com/+arnaudgabourygabx

Hi There,

I am using Libvirt 1.2.1  on Fedora 20.

So, Libvirt is well installed and started but the weird thing is that the
'default' virtual network is not automatically defined and started,
knowing that I can define/start it manually and everything goes fine.

previously I was using libvirt 1.0.4 and the 'default' virtual network
was defined/started at Libvirt startup.

so, I am wondering if this new behavior was introduced intentionally in the
latest versions of Libvirt or it's a known issue.

Thank you in advance for your help.

Regards
Mohamed.

Hi again,

I just wanted to let you know that this is our own packaging of libvirt 1.2.1, 
and that we are using a slightly different spec file from the one available in
the sources.

regards
Mohamed 

----- Mail original -----
> De: "Mohamed Amine Larabi" <mohamed.larabi@inria.fr>
> À: libvirt-users@redhat.com
> Envoyé: Lundi 10 Février 2014 14:50:33
> Objet: [libvirt-users] libvirt 1.2.1 / lxc : default virtual network not
defined after installing/starting Libvirt
> 
> Hi There,
> 
> I am using Libvirt 1.2.1  on Fedora 20.
> 
> So, Libvirt is well installed and started but the weird thing is that
> the 'default' virtual network is not automatically defined and
> started, knowing that I can define/start it manually and everything
> goes fine.
> 
> previously I was using libvirt 1.0.4 and the 'default' virtual
> network was defined/started at Libvirt startup.
> 
> so, I am wondering if this new behavior was introduced intentionally
> in the latest versions of Libvirt or it's a known issue.
> 
> Thank you in advance for your help.
> 
> Regards
> Mohamed.
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
>