Thanks, Daniel I verified I had libvirt-daemon rpm on my laptop and reloaded its units, but that didn't solve the issue. I then checked the vms- libvirt-daemon rpm was indeed missing on my vms. After I installed it & reloaded its unit files libvirtd.service was found, but as I started it, the error 'operation failed: pool 'default' already exists with uuid a42beb54-839e-437b-a48e-d06f6100205c' appeared again on my laptop. I'm not sure if I was supposed to install libvirt-daemon rpm on the vms? if it was needed - how do I resolve the error now? and any idea why it was missing? I never had to install it before if not - if you have any other thoughts/suggestions I'll be glad to hear :) Dana On Tue, May 12, 2020 at 1:16 PM Daniel P. Berrangé <berrange@redhat.com> wrote:> On Tue, May 12, 2020 at 01:00:06PM +0300, Dana Elfassy wrote: > > Hi all, > > Some background: > > I recently has some issues with libvirt on my laptop when I got the error > > 'operation failed: pool 'default' already exists with uuid > > dd48b6ad-9a00-46eb-a3a4-c122d8a294a5' when I connected virt-manager. I > was > > finally able to resolve it yesterday, when I removed libvirt and all its > > related content in /etc/libvirt, removed the pool by its UUID, deleted > > virbr0 & virbro-nic, removed the default network, reinstalled and created > > the network & default pool again > > > > Now I got libvirtd on my laptop up & running. > > > > However, when I install vms on my laptop, they don't have > libvirtd.service > > This is the network configuration XML: > > <interface type="network"> > > <mac address="52:54:00:d0:40:69"/> > > <source network="default" portid="171a745c-f96d-412a-baa7-ee1feeaed6ac" > > bridge="virbr0"/> > > <target dev="vnet1"/> > > <model type="virtio"/> > > <alias name="net0"/> > > <address type="pci" domain="0x0000" bus="0x00" slot="0x03" > > function="0x0"/> > > </interface> > > > > I installed the vms with virt-manager. The Network source is Virtual > > network 'default': NAT > > > > I'm using CentOS8.1 on both my laptop & vms. > > Is there anything else I need to reconfigure or any thoughts why > > libvirtd.service doesn't exist on my VMS? > > If the unit doesn't exist, then I suspect you are either missing the > libvirt-daemon RPM or systemd has not correctly reloaded its unit > files after install. (systemctl daemon-reload would fix the latter) > > > Regards, > Daniel > -- > |: https://berrange.com -o- > https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- > https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- > https://www.instagram.com/dberrange :| > >
Daniel P. Berrangé
2020-May-12 11:33 UTC
Re: Unit libvirtd.service could not be found. on VM
On Tue, May 12, 2020 at 02:25:29PM +0300, Dana Elfassy wrote:> Thanks, Daniel > I verified I had libvirt-daemon rpm on my laptop and reloaded its units, > but that didn't solve the issue. I then checked the vms- > libvirt-daemon rpm was indeed missing on my vms. After I installed it & > reloaded its unit files libvirtd.service was found, but as I started it, > the error 'operation failed: pool 'default' already exists with uuid > a42beb54-839e-437b-a48e-d06f6100205c' appeared again on my laptop. > I'm not sure if I was supposed to install libvirt-daemon rpm on the vms? if > it was needed - how do I resolve the error now? and any idea why it was > missing? I never had to install it before > if not - if you have any other thoughts/suggestions I'll be glad to hear :)If virt-manager is connecting to the host OS, there's no reason to install libvirtd in any guests VM. The error message is telling you that the 'default' storage pool already exists - "virsh pool-list" should show it. THe existance of this error message in the logs is not in itself a problem. It may just show that virt-manager is blindly trying to create the pool even when it already exists. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
if I understand correctly then I shouldn't have installed libvirt-daemon on the guests VMs? On Tue, May 12, 2020 at 2:34 PM Daniel P. Berrangé <berrange@redhat.com> wrote:> On Tue, May 12, 2020 at 02:25:29PM +0300, Dana Elfassy wrote: > > Thanks, Daniel > > I verified I had libvirt-daemon rpm on my laptop and reloaded its units, > > but that didn't solve the issue. I then checked the vms- > > libvirt-daemon rpm was indeed missing on my vms. After I installed it & > > reloaded its unit files libvirtd.service was found, but as I started it, > > the error 'operation failed: pool 'default' already exists with uuid > > a42beb54-839e-437b-a48e-d06f6100205c' appeared again on my laptop. > > I'm not sure if I was supposed to install libvirt-daemon rpm on the vms? > if > > it was needed - how do I resolve the error now? and any idea why it was > > missing? I never had to install it before > > if not - if you have any other thoughts/suggestions I'll be glad to hear > :) > > If virt-manager is connecting to the host OS, there's no reason to install > libvirtd in any guests VM. > > The error message is telling you that the 'default' storage pool already > exists - "virsh pool-list" should show it. > > THe existance of this error message in the logs is not in itself a problem. > It may just show that virt-manager is blindly trying to create the pool > even when it already exists. > > Regards, > Daniel > -- > |: https://berrange.com -o- > https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- > https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- > https://www.instagram.com/dberrange :| > >