The files in /etc/libvirt/qemu are designed to be used and managed by
libvirt and not to be edited by hand. The correct and documented way to
make changes to your machine definition is mentioned in comment #8 in
this bug.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Invalid
--
Per
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Wishlist
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launchpad.net/bugs/235386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Mario: I think the process Bryan describes is the way to do it.
E.G.
$ virsh dumpxml foo > /tmp/foo.xml
(edit /tmp/foo.xml as needed)
$ virsh define /tmp/foo.xml
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launchpad.net/bugs/235386
You received this bug notifi
Brian,
Have you found a work around?
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launchpad.net/bugs/235386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Confirmed
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launchpad.net/bugs/235386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I can confirm.
If you load virsh as a user in the libvirtd group, and define a domain
from a user readable xml file, libvirt creates a copy in
/etc/libvirt/qemu/ that's mode 600 root/root. The user can no longer
read these files.
One could use 'dumpxml domain', copy and paste into a new file, the
This bug is marked as incomplete. Is there any more information I can
provide?
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launchpad.net/bugs/235386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
I had edited the xml file to change some settings of the domain.
According to https://help.ubuntu.com/community/KVM#head-
3d3cc318838c52784822e7550dfba68bc7f25084
"If you have made a change to the XML configuration file, you need to
tell KVM to reload it before restarting the VM:
virsh # define
Ah, yes, I misread your original report. I'm not sure why you're trying
to define a domain that is already defined? The files in
/etc/libvirt/qemu describe domains that are already defined, so defining
them again would be a no-op. What are you actually trying to do?
--
Permissions of files in /et
No, I have not changed the configuration. libvirtd may be running as
root, but virsh is running as me. It tries to open the file and fails.
When I
virsh # define /etc/libvirt/qemu/opensolaris.xml
error: Failed to open '/etc/libvirt/qemu/opensolaris.xml': Permission denied
strace on virsh shows
This makes no sense. The libvirtd process managing qemu:///system runs
as root, so that should work fine. Did you change libvirtd.conf in some
way?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
Permissions of files in /etc/libvirt/qemu are too restrictive
https://bugs.launc
11 matches
Mail list logo
