Bug 924494
Summary: | kvm f19 guest xorg segfault with spice/qlx on f17 hosts | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||
Component: | xorg-x11-drv-qxl | Assignee: | Alon Levy <alevy> | ||||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 19 | CC: | airlied, alevy, awilliam, dblechte, hdegoede, marcandre.lureau, robatino, sandmann, xgl-maint | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | RejectedBlocker | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-05-15 02:50:41 UTC | Type: | Bug | ||||||||||
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
Reartes Guillermo
2013-03-21 21:45:56 UTC
Created attachment 714120 [details]
anaconda.log
Created attachment 714121 [details]
program.log
Created attachment 714123 [details]
syslog file
The criteria only require virtualization to work at Beta, and then only N on N and N on N-1, not N on N-2. For me, both 19 on 19 and 19 on 18 work at present. So I'm -1 to this. I looked at this issue again, and found that it did not affect all guests just one (i did not test all guest yet), and for the affected one, adding 'selinux=0' boot parameter fixed the issue. I don't known why selinux selected that guest in particular for failing, it has a lot of AVCs. The other guests booted fine with the defaults boot parameters. I'm also -1 to this now, since it is not even a general issue. Discussed at 2013-03-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Rejected as a blocker per criteria and comment #5. Re-assigning to correct component; are you still seeing this one? Any more useful info on the affected VM? > are you still seeing this one? Any more useful info on the affected VM?
no, and that is a good thing.
maybe this can be closed, i will re-open if i encounter it again.
OK, let's go with that. Thanks! |