CentOS Bug Tracker
CentOS Website
Main | My View | View Issues | Roadmap | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ View Advanced ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0002561 [CentOS-5] xen major random 2007-12-22 12:34 2007-12-22 12:44
Reporter colo4jax View Status public  
Assigned To
Priority normal Resolution open  
Status new   Product Version 5.1
Summary 0002561: problem in xend prevents console access and routed networking
Description Within an hour of each other, two of my users reported that their domUs are unreachable. Each user is running on a separate box, where the configs are identical installations of Cent 5.1 from kickstart, plus 'yum -y install xen kernel-xen'. Hardware config are both 12GB of RAM, SATA storage and single processors. Both systems are Tyan S5372G2NR-LCs, one system is a 2.66 ghz Xeon Dempsey, the other a 1.6 ghz Xeon Clovertown.

This problem is characterized by no network access; specifically, although the named vif is operational according to ifconfig, and it's IP address is pingable locally or remotely, pings to the domU are returned with an ICMP destination unreachable sourced by the dom0's IP. Further, attempted console access produces this error:

[root@vpsbox4 ~]# xm console chinavps1
xenconsole: Could not open tty `/dev/pts/8': No such file or directory
[root@vpsbox4 ~]#

At this point I would invoke /etc/init.d/xend restart and everything would go back to normal, permitting console access and providing normal networking to my domUs.
Additional Information [root@vpsbox4 ~]# xm dmesg
 __ __ _____ _ ___ ____ _____ _ _ _ _ ____
 \ \/ /___ _ __ |___ / / | / _ \ | ___|___ / / || || | ___| | ___|
  \ // _ \ \047_ \ |_ \ | || | | |_|___ \ |_ \ | || || |_ / _ \ |___ \
  / \ __/ | | | ___) || || |_| |__|__) |__) || ||__ _| __/ |___) |
 /_/\_\___|_| |_| |____(_)_(_)___/ |____/____(_)_(_) |_|(_)___|_|____/

 http://www.cl.cam.ac.uk/netos/xen [^]
 University of Cambridge Computer Laboratory

 Xen version 3.1.0-53.1.4.el5 (mockbuild@) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) Fri Nov 30 00:37:01 EST 2007
 Latest ChangeSet: unavailable

(XEN) Command line: /xen.gz-2.6.18-53.1.4.el5 dom0_mem=510000 noreboot
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bff00000 (usable)
(XEN) 00000000bff00000 - 00000000bff0a000 (ACPI data)
(XEN) 00000000bff0a000 - 00000000bff80000 (ACPI NVS)
(XEN) 00000000bff80000 - 00000000c0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000340000000 (usable)
(XEN) System RAM: 12286MB (12581500kB)
(XEN) Xen heap: 9MB (9852kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 15:6 APIC version 20
(XEN) Processor 0000002 15:6 APIC version 20
(XEN) Processor 0000001 15:6 APIC version 20
(XEN) Processor #3 15:6 APIC version 20
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 5, version 32, address 0xfec80000, GSI 24-47
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2660.158 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Xeon(TM) CPU 2.66GHz stepping 04
(XEN) Mapping cpu 0 to node 255
(XEN) Booting processor 1/2 eip 90000
(XEN) Mapping cpu 1 to node 255
(XEN) CPU1: Intel(R) Xeon(TM) CPU 2.66GHz stepping 04
(XEN) Booting processor 2/1 eip 90000
(XEN) Mapping cpu 2 to node 255
(XEN) CPU2: Intel(R) Xeon(TM) CPU 2.66GHz stepping 04
(XEN) Booting processor 3/3 eip 90000
(XEN) Mapping cpu 3 to node 255
(XEN) CPU3: Intel(R) Xeon(TM) CPU 2.66GHz stepping 04
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xc0400000 memsz=0x25d640
(XEN) elf_parse_binary: phdr: paddr=0xc065e000 memsz=0x15a000
(XEN) elf_parse_binary: memory: 0xc0400000 -> 0xc07b8000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc0400000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc0401000
(XEN) elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xc0000000
(XEN) elf_paddr_offset = 0xc0000000
(XEN) virt_offset = 0x0
(XEN) virt_kstart = 0xc0400000
(XEN) virt_kend = 0xc07b8000
(XEN) virt_entry = 0xc0400000
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0400000 -> 0xc07b8000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000007f000000->0000000080000000 (123404 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c07b8000
(XEN) Init. ramdisk: c07b8000->c0cc8e00
(XEN) Phys-Mach map: c0cc9000->c0d45830
(XEN) Start info: c0d46000->c0d4646c
(XEN) Page tables: c0d47000->c0d54000
(XEN) Boot stack: c0d54000->c0d55000
(XEN) TOTAL: c0000000->c1000000
(XEN) ENTRY ADDRESS: c0400000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc065d640
(XEN) elf_load_binary: phdr 1 at 0xc065e000 -> 0xc0702b64
(XEN) Initrd len 0x510e00, start at 0xc07b8000
(XEN) Scrubbing Free RAM: .....................................................................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen).
(XEN) mm.c:612:d4 Non-privileged (4) attempt to map I/O space 003c26b0
(XEN) mm.c:3263:d4 ptwr_emulate: fixing up invalid PAE PTE 00000003c26b0025
(XEN) mm.c:612:d7 Non-privileged (7) attempt to map I/O space 00373b2c
(XEN) mm.c:3263:d7 ptwr_emulate: fixing up invalid PAE PTE 0000000373b2c025
(XEN) mm.c:636:d12 Error getting mfn 2f73c4 (pfn 9a43) from L1 entry 00000002f73c4025 for dom12
(XEN) mm.c:3263:d12 ptwr_emulate: fixing up invalid PAE PTE 00000002f73c4025
(XEN) mm.c:636:d16 Error getting mfn 299a26 (pfn 1971e) from L1 entry 0000000299a26025 for dom16
(XEN) mm.c:3263:d16 ptwr_emulate: fixing up invalid PAE PTE 0000000299a26025
(XEN) mm.c:636:d18 Error getting mfn 26b3f4 (pfn 8a8f) from L1 entry 000000026b3f4025 for dom18
(XEN) mm.c:3263:d18 ptwr_emulate: fixing up invalid PAE PTE 000000026b3f4025
(XEN) mm.c:636:d19 Error getting mfn 25bc5b (pfn 89c8) from L1 entry 000000025bc5b025 for dom19
(XEN) mm.c:3263:d19 ptwr_emulate: fixing up invalid PAE PTE 000000025bc5b025
(XEN) mm.c:636:d21 Error getting mfn 21d5a5 (pfn 8af8) from L1 entry 000000021d5a5025 for dom21
(XEN) mm.c:3263:d21 ptwr_emulate: fixing up invalid PAE PTE 000000021d5a5025
(XEN) mm.c:636:d22 Error getting mfn 20de73 (pfn 1822a) from L1 entry 000000020de73025 for dom22
(XEN) mm.c:3263:d22 ptwr_emulate: fixing up invalid PAE PTE 000000020de73025
(XEN) mm.c:636:d23 Error getting mfn 1ae8f6 (pfn ab78) from L1 entry 00000001ae8f6025 for dom23
(XEN) mm.c:3263:d23 ptwr_emulate: fixing up invalid PAE PTE 00000001ae8f6025
(XEN) mm.c:636:d25 Error getting mfn 16f4ae (pfn ba10) from L1 entry 000000016f4ae025 for dom25
(XEN) mm.c:3263:d25 ptwr_emulate: fixing up invalid PAE PTE 000000016f4ae025
(XEN) mm.c:636:d26 Error getting mfn 1501e8 (pfn bdca) from L1 entry 00000001501e8025 for dom26
(XEN) mm.c:3263:d26 ptwr_emulate: fixing up invalid PAE PTE 00000001501e8025
(XEN) mm.c:636:d28 Error getting mfn 240795 (pfn 4b73) from L1 entry 0000000240795025 for dom28
(XEN) mm.c:3263:d28 ptwr_emulate: fixing up invalid PAE PTE 0000000240795025
(XEN) mm.c:636:d31 Error getting mfn 240be4 (pfn 4724) from L1 entry 0000000240be4025 for dom31
(XEN) mm.c:3263:d31 ptwr_emulate: fixing up invalid PAE PTE 0000000240be4025
(XEN) mm.c:636:d32 Error getting mfn 2403fe (pfn 4f0a) from L1 entry 00000002403fe025 for dom32
(XEN) mm.c:3263:d32 ptwr_emulate: fixing up invalid PAE PTE 00000002403fe025
(XEN) mm.c:636:d33 Error getting mfn 240bff (pfn 4709) from L1 entry 0000000240bff025 for dom33
(XEN) mm.c:3263:d33 ptwr_emulate: fixing up invalid PAE PTE 0000000240bff025
(XEN) mm.c:636:d34 Error getting mfn 240640 (pfn 4cc8) from L1 entry 0000000240640025 for dom34
(XEN) mm.c:3263:d34 ptwr_emulate: fixing up invalid PAE PTE 0000000240640025

[root@vpsbox4 ~]#
[root@vpsbox4 ~]# cat /etc/xen/chinavps1
kernel = "/home/vmlinuz-2.6.18-4-xen-686"
ramdisk = "/home/initrd.img-2.6.18-4-xen-686"
memory = 249
name = "chinavps1"
vif = ['mac=00:16:3e:3d:a0:17, vifname=chinavps1, script=vif-chinavps1']
disk = [ 'tap:aio:/home/vps/chinavps1.img,sda1,w' ]
root = "/dev/sda1 ro"
extra = "4"
vcpus=1
on_reboot = 'restart'
on_crash = 'restart'
builder = 'linux'
[root@vpsbox4 ~]#
[root@vpsbox4 ~]# cat /etc/xen/scripts/vif-chinavps1
# IPs have been changed to protect the innocent.

dir=$(dirname "$0")
. "$dir/vif-common.sh"

main_ip=$(dom0_ip)

case "$command" in
    online)
        ifconfig ${vif} 38.1.1.1 netmask 255.255.255.255 up
        echo 1 >/proc/sys/net/ipv4/conf/${vif}/proxy_arp
        /sbin/route add -net 38.1.1.0/29 gw 38.1.1.1
        ipcmd='add'
        cmdprefix=''
        ;;
    offline)
        do_without_error ifdown ${vif}
        ipcmd='del'
        cmdprefix='do_without_error'
        ;;
esac

log debug "Successful vif-route $command for $vif."
if [ "$command" = "online" ]
then
  success
fi
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0006599)
colo4jax (reporter)
2007-12-22 12:44

 Some secondary thoughts:

1) both of these domUs happen to be Debian; will continue to monitor this for a potential connection

2) although the domUs were Debian, the problem accessing domU consoles persisted across the board witg every domU that I tried on each respective system

3) In the event that my vif script looks a little strange, in that it provides its own gateway IP as part of a /29 allocation, that's because it is. Moreover, it does not accept a list of IPs in the vif config statement because I found this to be broken in Cent 5.0. I never filed a bug report because I get paid to make things work, not to file bug reports.

4) There are major issues with Xen under Cent 5.1; not all of them I have the time or the inclination to report; again my objective is to solve problems for the people who pay me, and nothing else.

5) I trust that you'll give these issues greater consideration than my previous reports 0002300 and 0002317. 2317 is actually an issue fixed by Xen in 3.1.2 (although I never would have known based on the nonexistant response by you folks). But overall, it would be nice if everyone were as diligent in helping to smash some of these things as they are about turning out RPMs and releases.

- Issue History
Date Modified Username Field Change
2007-12-22 12:34 colo4jax New Issue
2007-12-22 12:34 colo4jax Assigned To => kbsingh@karan.org
2007-12-22 12:44 colo4jax Note Added: 0006599

Copyright © 2000 - 2009 Mantis Group
Powered by Mantis Bugtracker