Bug 862335
Summary: | non-kvm qemu guests fail to start due to execmem: libvirt needs to label with svirt_nokvm_t | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christophe Fergeau <cfergeau> | ||||||
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 18 | CC: | berrange, clalancette, crobinso, dominick.grift, dwalsh, eischmann, fran, itamar, jforbes, jyang, laine, libvirt-maint, mgrepl, veillard, virt-maint | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | abrt_hash:9d2cc420dc38d7438434c2480a2fe20533d39b059c9d0bddc1cd7143a9f17d7d | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2012-12-12 14:59:14 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Christophe Fergeau
2012-10-02 16:45:14 UTC
Created attachment 620391 [details]
File: type
Created attachment 620392 [details]
File: hashmarkername
:#============= svirt_t ============== :#!!!! This avc can be allowed using the boolean 'virt_use_execmem' (In reply to comment #3) > :#============= svirt_t ============== > :#!!!! This avc can be allowed using the boolean 'virt_use_execmem' Doesn't this mean that non-kvm qemus are broken out of the box, and that this is done on purpose? This does not sound great from a user point of view... Since 3.5.4 Boxes allows to create QEMU VMs without KVM capabilities: http://ftp.acc.umu.se/pub/GNOME/sources/gnome-boxes/3.5/gnome-boxes-3.5.4.news Well open this up for discussion on the virt list. I don't care either way. Allowing virt to use execmem, makes it more susceptable to buffer overflow attacks. I guess we could have libvirt set the boolean when running a qemu process without kvm or select a different svirt label svirt_nokvm_t. I would go for having a separate svirt label for non-KVM based QEMU. Ok I just checked changes into F18 policy to support to types svirt_t, and svirt_nokvm_t, only difference is execmem, and execstack for svirt_nokvm_t. Context file has changed to include two labels. cat virtual_domain_context system_u:system_r:svirt_t:s0 system_u:system_r:svirt_nokvm_t:s0 Now libvirt needs to change to be able to use the alternate label. I was trying to create a virtual machine in Boxes. Package: (null) Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow) Jiri just turn on the boolean. *** This bug has been marked as a duplicate of bug 885837 *** |