Bug 654639
| Summary: | [vgabios] bochs vga lfb @ 0xe0000000 causes trouble for hot-plug | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Gerd Hoffmann <kraxel> |
| Component: | vgabios | Assignee: | Gerd Hoffmann <kraxel> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | alex.williamson, amit.shah, bcao, cmeadors, fnadge, Jes.Sorensen, kcao, khong, kraxel, lihuang, mkenneth, tburke, virt-maint, ypu |
| Target Milestone: | beta | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | vgabios-0.6b-3.5.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: The vgabios for the qemu standard vga expected to find the framebuffer memory at the magic address 0xe0000000. This makes qemu-kvm exit due to overlapping memory reservations in case the guest OS tries to use the address space at 0xe0000000 for something else, for example mapping ressources of hot-plugged PCI devices there.
Consequence: The vgabios has been changed to lookup the framebuffer memory in PCI space instead.
qemu-kvm has been changed to not create the framebuffer mapping at 0xe0000000 any more (see bug #638468).
Result: The address space at 0xe0000000 can freely be used by the guest OS.
|
Story Points: | --- |
| Clone Of: | 638468 | Environment: | |
| Last Closed: | 2011-05-19 14:28:18 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: | |||
| Bug Depends On: | 638468 | ||
| Bug Blocks: | 580954 | ||
|
Comment 11
Florian Nadge
2011-04-20 13:35:14 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
This field is the basis of the errata or release note for this bug. It can also be used for change logs.
When documenting a Known Issue, use the CCWR variation as follows:
Cause
What actions or circumstances cause the bug to present (if known).
Note: if the cause is not known or is not fully diagnosed,
current hypotheses or theories should be noted.
Consequence
What happens when the bug presents.
Workaround
What actions, if any, reduce the bug’s effects or prevent it from presenting entirely.
Result
If the bug’s effect is only reduced, what consequences still flow;
if the bug is prevented, what restrictions does the workaround impose.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,15 +1,7 @@
-This field is the basis of the errata or release note for this bug. It can also be used for change logs.
+Cause: The vgabios for the qemu standard vga expected to find the framebuffer memory at the magic address 0xe0000000. This makes qemu-kvm exit due to overlapping memory reservations in case the guest OS tries to use the address space at 0xe0000000 for something else, for example mapping ressources of hot-plugged PCI devices there.
-When documenting a Known Issue, use the CCWR variation as follows:
+Consequence: The vgabios has been changed to lookup the framebuffer memory in PCI space instead.
-Cause
+qemu-kvm has been changed to not create the framebuffer mapping at 0xe0000000 any more (see bug #638468).
- What actions or circumstances cause the bug to present (if known).
+
- Note: if the cause is not known or is not fully diagnosed,
+Result: The address space at 0xe0000000 can freely be used by the guest OS.- current hypotheses or theories should be noted.
-Consequence
- What happens when the bug presents.
-Workaround
- What actions, if any, reduce the bug’s effects or prevent it from presenting entirely.
-Result
- If the bug’s effect is only reduced, what consequences still flow;
- if the bug is prevented, what restrictions does the workaround impose.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0776.html |