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