Xen vs. xserver-xorg
So, I've began to explore Xen. The most visible change when
turning a stand-alone system into a Xen dom0 is that X.Org X
server fails to start with something like the following (as of
Debian Etch):
$ cat /var/log/Xorg.1.log
...
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 16384 kB
(II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
(II) VESA(0): VESA VBE OEM Software Rev: 10.54
(II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) VESA(0): VESA VBE OEM Product: RV610
(II) VESA(0): VESA VBE OEM Product Rev: 01.00
Fatal server error:
xf86MapVidMem: Could not mmap framebuffer (0xe0000000,0x1000000) (Invalid argument)
$
A short summary of what I get on a different software and
hardware configuration is as follows.
It's not the `vesa' driver specific fault.
The same error message appears when using either `s3virge' or
`i810' driver (on the respective hardware), too.
It's not impossible to access the FB when running under Xen.
The `ati' (`radeon') driver (also from Debian Etch) works
correctly (on the respective hardware) when run from within a
Xen dom0.
Apparently, the problem exists in Debian Lenny as well.
I've tried to (partially) upgrade one of these Debian Etch
systems to Debian Lenny, but the `s3virge' driver (now as of
xserver-xorg-video-s3virge 1.10.1-1) fails the same way.
I think that it's quite likely that the problem isn't
Debian-specific. Perhaps [1] may be of any inspiration?
Any ideas on what to do to fix the problem?
[1] https://bugzilla.novell.com/show_bug.cgi?id=422081
Reply to: