Comment 2 for bug 223993

I am also having this bug.

It's doing a GET /xend/node/ over a Unix socket, and the response (from strace) is:

read(18, "(node (system Linux) (host xen) (release 2.6.19-4-generic-amd64) (version \'#2 SMP Thu Apr 5 05:57:13 UTC 2007\') (machine x86_64) (nr_cpus 2) (nr_nodes 1) (cores_per_socket 2) (threads_per_core 1) (cpu_mhz 1800) (hw_caps 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f) (total_memory 4094) (free_memory 2) (max_free_memory 747) (max_para_memory 743) (max_hvm_memory 733) (node_to_cpu node0:0-1) (xen_major 3) (xen_minor 2) (xen_extra .1-rc1-pre) (xen_caps \'xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 \') (xen_scheduler credit) (xen_pagesize 4096) (platform_params \'virt_start=0xffff800000000000\') (xen_changeset unavailable) (cc_compiler \'gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)\') (cc_compile_by buildd) (cc_compile_domain buildd) (cc_compile_date \'Fri Apr 11 01:13:51 UTC 2008\') (xend_config_format 4))", 852) = 852
close(18) = 0
--- SIGFPE (Floating point exception) @ 0 (0) ---
+++ killed by SIGFPE +++
Process 13794 detached