http://bugzilla.suse.com/show_bug.cgi?id=999070 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com Assignee|bnc-team-screening@forge.pr |kvm-bugs@forge.provo.novell |ovo.novell.com |.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 http://bugzilla.suse.com/show_bug.cgi?id=999070#c1 Lin Ma changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |brogers@suse.com, | |krahmer@suse.com Flags| |needinfo?(krahmer@suse.com) | |, | |needinfo?(brogers@suse.com) --- Comment #1 from Lin Ma --- The execution permission was changed by https://bugzilla.suse.com/show_bug.cgi?id=988279#c6 Finally, it causes that non-privileged user can't launch a guest which has bridged network backends through libvirt, says: $virt-install ... --network=bridge=br0 ... error: '/usr/libexec/qemu-bridge-helper' is not a suitable bridge helper: No such file or directory @Bruce, I'd like to make some changes like this: -%verify(not mode) %attr(4750,root,kvm) %_libexecdir/qemu-bridge-helper +%verify(not mode) %attr(4755,root,kvm) %_libexecdir/qemu-bridge-helper Is it ok? If you think 4755 is not good, then 4751 at least is needed. @Sebastian, how about making the corresponding permissions changes in /etc/permissions.easy ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 http://bugzilla.suse.com/show_bug.cgi?id=999070#c3 Lin Ma changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(brogers@suse.com) | --- Comment #3 from Lin Ma --- (In reply to Sebastian Krahmer from comment #2)

Mode 04750 reflects that only users in the kvm group should be allowed to use/setup (critical-) ressources such as bridging stuff. We should not change that (and its not necessary indeed).

Its clearly a packaging problem. I wonder why in the qemu-tools.rpm it has got the wrong pathname? Everything (even the libvirt build scripts) expect it in /usr/libexec. Its no problem updating the permissions git to have that pathname. The Apparmor policy would need the same change as well as the qemu-tools.rpm to put it at appropriate place.

The other option is to keep the qemu-tools.rpm and permissions config as is, and running the libvirt configure script as user who is part of kvm group (as its expected to be executed later). This would integrate the /usr/lib path I guess.

I just discussed with Bruce and Jim about it, So far option 2 perhaps is the best choice, I'll try to go this way. Sebastian, Thank you very much. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| maint:planned:update |maint:planned:update | |ibs:running:4037:moderate -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:4037:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:6431:moderate -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=999070 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:6431:moderate | -- You are receiving this mail because: You are on the CC list for the bug.