Bug 742699
Summary: | [abrt] xen-4.1.1-3.fc16: image.py:46:<module>:Error: (1, 'Internal error', 'xc_interface_open failed: Permission denied') | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Henry Rust <henryrust89> |
Component: | xen | Assignee: | Michael Young <m.a.young> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | berrange, crobinso, cruz, jamundso, jforbes, joanayma, jonathanjstevens, kraxel, mail, majid.merkava, marek90, m.a.young, oberfaulersgeist, raistlin, sergiovl, virt-maint, xen-maint, zhoutaomtv |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:7b3e98c5f19a39d97b36c2aff3e9bc6b3b27428a | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-11 21:36:13 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: |
Description
Henry Rust
2011-10-01 18:40:44 UTC
This may be selinux. I think it blocks some actions between libvirt and xen. Does it work any better if you run setenforce 0 (ie. put selinux in permissive mode) first? Package: xen-4.1.1-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- opened virt-manager connected to localhost (nothing more) Package: xen-4.1.1-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- opened virt-manager connected to localhost (nothing more) (In reply to comment #1) > This may be selinux. I think it blocks some actions between libvirt and xen. > Does it work any better if you run setenforce 0 (ie. put selinux in permissive > mode) first? No, it doesn't help. I set selinux in permessive mode in /etc/selinux/config so it's already permissive on boot up. I wanted to be sure that all xen services could be started, if selinux was the problem. But this changed nothing, still getting the same error. If I check with getenforce, whetver selinux is really in permissive mode, it tells me: "Permissive". Package: xen-4.1.1-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Running virt-manager, then added connection to local xen. Package: xen-4.1.1-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This happens each and every time I start "Virtual Machine Manager" while on Xen. I tried disabling SELinux, but that didn't help either. Package: xen-4.1.1-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Know this is already up here... but retested following update to xen. Still same problem. Boot machine. Login. Open virt-manager. Connect to localhost xen. Double-click Dom0. Virt-manager crashes and so does xen. Package: xen-4.1.1-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Started virt-manager from the KDE start menu. It looks like virt-manager is trying to run xend as an ordinary user, but xend expects to run as root. It may be possible to get xend to work as another user but some of the things it does will need root permissions to work. Package: xen-4.1.1-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I started the virt-manager. it asked me to enter root password. I was entering the password that crashed. Package: xen-4.1.1-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- when executing "Guest Filesystem Browser" or the virtual machine manager Package: xen-4.1.2-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- when open virtual machine manager window, the error message will be shown. But I don't feel any affect. Package: xen-4.1.2-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Tried starting virt-manager You should no longer get a backtrace with xen-4.1.2-2 which hopefully means that virt-manager won't crash. *** Bug 756499 has been marked as a duplicate of this bug. *** *** Bug 757336 has been marked as a duplicate of this bug. *** *** Bug 757462 has been marked as a duplicate of this bug. *** This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Sounds like this was fixed in xen 4.1.2-2, so closing. |