| commit | f0138a63a41fe26bcef61d031ae53d872d12a992 | |
| author | Anthony Liguori <aliguori@us.ibm.com> | |
| Thu, 17 Dec 2009 22:08:07 +0000 (18 08:08 +1000) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Fri, 18 Dec 2009 17:26:31 +0000 (18 11:26 -0600) | ||
| tree | d4b795d9339137211b020c22a7ac6a4b6070b9c8 | treesnapshot (tar.gz zip) |
| parent | f351d050dccfc469fecd353d095526d52e4632c6 | commitdiff |
Make sure to enable dirty tracking of VBE vram mapping
Apparently, VBE maps the VGA vram to a fixed physical location. KVM requires
that all mappings of the VGA vram have dirty tracking enabled on them. Any
access to the VGA vram through the VBE mapping currently fails to result in
dirty page tracking updates causing a black screen.
This is the true root cause of VMware VGA not working correctly under KVM and
likely also an issue with some of the std-vga black screen issues too.
Cirrus does not enable VBE so it would not be a problem when using Cirrus.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Rebased-by: Dave Airlie <airlied@redhat.com>
Apparently, VBE maps the VGA vram to a fixed physical location. KVM requires
that all mappings of the VGA vram have dirty tracking enabled on them. Any
access to the VGA vram through the VBE mapping currently fails to result in
dirty page tracking updates causing a black screen.
This is the true root cause of VMware VGA not working correctly under KVM and
likely also an issue with some of the std-vga black screen issues too.
Cirrus does not enable VBE so it would not be a problem when using Cirrus.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Rebased-by: Dave Airlie <airlied@redhat.com>
| hw/vga-isa.c | diffblobblamehistory | |
| hw/vga-pci.c | diffblobblamehistory | |
| hw/vga.c | diffblobblamehistory | |
| hw/vga_int.h | diffblobblamehistory | |
| hw/vmware_vga.c | diffblobblamehistory |