Yes I think you are true. But the Debian bug (debbugs #567818) in relation to this bug is the same. Maybe I could try to report my bug as a new one?
I already check the xml configuration of my VM. Apparently, this path is created directly by the hypervisor when the VM is started. I tried to set up it in the configuration file with "virsh edit", but libvirt didn't commit the modification (even if the VM is not started).
Yes I think you are true. But the Debian bug (debbugs #567818) in relation to this bug is the same. Maybe I could try to report my bug as a new one?
I already check the xml configuration of my VM. Apparently, this path is created directly by the hypervisor when the VM is started. I tried to set up it in the configuration file with "virsh edit", but libvirt didn't commit the modification (even if the VM is not started).
And apparently, this bug is fixed in libvirt 0.7.5 (http:// libvirt. org/git/ ?p=libvirt. git;a=commit; h=c0a9b6a5338e5 4b64a4a28415ffb db6bcc2b38c5).