Daniel P. Berrange wrote:
On Mon, Aug 07, 2006 at 11:40:34PM -0700, Matt C wrote:
System is kernel-xen-2.6.17-1.2157_FC5 on a 2p opteron (older
non-hardware-virt). This happens when I try to run the 'dmidecode' tool
from within a non-privileged guest. The guest is running the same kernel
as above. One other note is that the console on this system is serial,
ttyS0 at 9600bps... which may have something to do with the CPU lockup
bugs below.
The guest should not be trying to do those operations. I can
take a look into tightening our /dev/mem patch, since it does
not seem to happen with some of our Xen kernels but it does
with others.
Indeed, thre is no SMBios data made available to ParaVirt guests so it is
not currently possible to make dmidecide work for PV guests. This may change
in the future, but I don't think anyone is actively working on SMBios support
for PV just yet.
Yeah, I'm pretty sure we don't want SMBios data for paravirt
guests. After all, they're not running on real hardware...
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
