[Bug 691590] Re: libvirt restore exactly the old ownership of images

Soren Hansen 691590 at bugs.launchpad.net
Mon Jun 22 11:56:23 UTC 2020


A non-root process that uses qemu:///system to run virtual machines
(which is required for most network configurations) will lose access to
its disk images for good as soon as the domain is started.

First it'll be changed to libvirt-qemu:kvm and once the domain is
terminated it will be set to root:root. As a regular user this is
nuisance that can be worked around with "sudo chown" (the vast majority
of users have this access), but for a daemon that doesn't run as root
and doesn't have a human to take care of it and needs access to *its
own* disk images, this makes libvirtd as shipped by ubuntu unusable.

I'd highly suggest an SRU for this.

I've been away from Ubuntu development for a while. Is there any
particular reason not to just upload the fixed version now?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/691590

Title:
  libvirt restore exactly the old ownership of images

Status in libvirt:
  Fix Released
Status in libvirt package in Ubuntu:
  In Progress

Bug description:
  Natty (and it was also the same on Maverick, IIRC).

  When you assign an ISO to a VM, libvirt will take over onwership of
  the ISO. This creates problems if the ISO is updated.

  For example, I am daily updating the Natty server ISOs, and running
  tests on them via KVM (all automated). The ISO updates will fail
  because libvirt chowns them.

  I see no reason for this: libvirt only needs the ISO as input.

  WORKAROUND:
    edit /etc/libvirt/qemu.conf, change 'dynamic_ownership = 0', restart qemu/KVM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/691590/+subscriptions



More information about the Ubuntu-sponsors mailing list