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

[Soren Hansen]

Gosh. I'd happily forgotten about that video. I was so young and so
mumbly. :D

I'm not sure I understand. If you're not uploading to groovy, how are
you collecting test results?

Also, I don't know what sort of test facilities or processes you have
available, so I don't know how time consuming or expensive a complete
regression test run is, but in general I find that smaller changes are
better than larger, batched changes for finding problems and identifying
their cause. If something doesn't work after pushing a big batch of
changes, it can be really hard to identify which one of the many changes
is the culprit.

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