Hello!
When creating a VM with 16MByte xend cores with
Program received signal SIGBUS, Bus error.
[Switching to Thread 0xb45ffb90 (LWP 27606)]
0xb7ecf6af in memset () from /lib/libc.so.6
and a stack trace like the one in the attachment.
(detected during a run of xm-test '16_create_smallmem_neg')
xend should throw / return some error - but must not core.
Environment:
xen-unstable
i386
Debian 5.0.1
Kind regards
Andreas
P.S.: Started some deeper analyse of this problem which leads me to some
hints that 'mmap(2)' does not work - which I cannot believe. (Some more
notes and stack traces to my (possible wrong) analyse can be found in my
notebook [1].)
[1] http://87.230.77.133/blog/?p=42
===========================================
(gdb) bt
#0 0xb7f446af in memset () from /lib/libc.so.6
#1 0xb7ad4d6e in xc_dom_alloc_segment (dom=0x9efd9c0, seg=0x9efdb80,
name=0xb7adc763 "kernel", start=3238002688, size=9732096)
 at xc_dom_core.c:424
#2 0xb7ad4e48 in xc_dom_build_image (dom=0x9efd9c0) at xc_dom_core.c:730
#3 0xb7ad7267 in xc_linux_build_internal (dom=0x9efd9c0, xc_handle=,
domid=, mem_mb=16, flags=0,
 store_evtchn=1, store_mfn=0xb495468c, console_evtchn=2,
console_mfn=0xb4954688) at xc_dom_compat_linux.c:47
#4 0xb7ad734c in xc_dom_linux_build (xc_handle=8, dom=0×9efd9c0,
domid=198, mem_mb=16, image_name=0×9ebcfbc “/boot/vmlinuz-2.6.30-rc3-tip”,
 initrd_name=0×9eb1a54
“/data/xu-add-bridge-to-kernel-config-01/tools/xm-test/ramdisk/initrd.img”,
flags=0, store_evtchn=1,
 store_mfn=0xb495468c, console_evtchn=2, console_mfn=0xb4954688) at
xc_dom_compat_linux.c:145
#5 0xb7b01ffb in pyxc_linux_build (self=0xb7e51340, args=0xb7e9102c,
kwds=0×9ecf68c) at xen/lowlevel/xc/xc.c:441
#6 0×0805d477 in PyObject_Call ()
#7 0×080ccbef in PyEval_EvalFrameEx ()
#8 0×080d0685 in PyEval_EvalCodeEx ()
#9 0×08117171 in ?? ()
#10 0×0995d6e0 in ?? ()
#11 0×099569bc in ?? ()
#12 0×00000000 in ?? ()
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel