search for: larabi

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,

> > 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

On Mon, Feb 10, 2014 at 15:13:05 +0100, Mohamed Amine Larabi wrote: > 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 everyt...

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

Hi there, I am using libvirt with lxc to create fedora 16 & 18 containers on fedora 18 host. first I did the setup with libvirt 1.0.3 and everything worked fine, then after upgrading to libvirt 1.0.4, I could not create character device on the guests : Test on the guest1 : # ls -l /dev total 0 lrwxrwxrwx. 1 root root 10 Apr 17 21:18 console -> /dev/pts/0 lrwxrwxrwx. 1 root root 11