search for: elfassi

Thanks, I discovered I had wrong permissions for /var/lib/libvirt/qemu/, after setting them to drwxr-x--x. qemu qemu and executing daemon-reload libvirtd.service exists now on my vms :) However - I'm not able to get it to run. In the journal I see the message libvirtd[6800]: Unable to import CA certificate list /etc/pki/vdsm/certs/cacert.pem I have verified its permissions and that it's

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

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

Thanks, Michal, On my laptop I do have libguestfs and libvirt-daemon-qemu. both libvirtd.service and libvirtd.socket are running ok on my laptop I just realized I haven't mentioned - my vms intend to serve as hosts themselves, and that's why they, too, need to have libvirtd.service running on them. up to recently I didn't have such a problem when I installed a vm on my laptop -

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

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

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

On 5/12/20 1:41 PM, Dana Elfassy wrote: > if I understand correctly then I shouldn't have installed libvirt-daemon > on the guests VMs? > > Just a little background to Daniel's response. Libvirt and QEMU treat guests as black boxes, to some extent. There are some exceptions to this rule, when it comes to para-virtualization (that is when the guest knows it is running

On 5/13/20 12:59 PM, Dana Elfassy wrote: > Thanks, Michal, > On my laptop I do have libguestfs and libvirt-daemon-qemu. both > libvirtd.service and libvirtd.socket are running ok on my laptop > I just realized I haven't mentioned - my vms intend to serve as hosts > themselves, and that's why they, too, need to have libvirtd.service > running on them. > up to