© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Ubuntu kernels use CONFIG_STRICT_MEM which prevents access to physical mem other than BIOS and PCI region so that X or dmidecode tools can read this info. On a native ARM system since there is no BIOS (yet) this causes mmap() of /dev/mem to return a -1. But with KVM/QEMU emulating ARM (mach virt) on native ARM, mmap() /dev/mem does not return a -1 but returns a valid address (or what looks like a valid address). Could it be that kvm/qemu is not passing protections correctly for phy mem ?