https://bugzilla.novell.com/show_bug.cgi?id=422081
User jbeulich@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=422081#c6
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbeulich@novell.com
Info Provider|jbeulich@novell.com |novell.com-pnt@ladisch.de
--- Comment #6 from Jan Beulich 2008-09-05 07:34:24 MDT ---
Unfortunately I have a hard time understanding #3: How can the frame buffer
validly live at (physcial) address 0?
/dev/mem under Xen is somewhat different from native for obvious reasons: It
doesn't allow you to access RAM, only MMIO regions (as reported by BIOS INT 15
Fn E820) can be accessed (and the region mmap()-ed must be consisting of only
MMIO, there may not be any RAM portions, but that's probably not the problem
here).
It would certainly help seeing the system's E820 map (as reported by Xen [xm
dmesg] and/or the native kernel [/var/log/boot.msg]) - chaning needinfo
accordingly.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.