WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xend crashing due to change in virt_kend value...??

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xend crashing due to change in virt_kend value...??
From: Sandesh <sandesh.ahiremath@xxxxxxxxx>
Date: Thu, 31 Jul 2008 06:03:50 +0530
Delivery-date: Wed, 30 Jul 2008 17:22:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,
  All of a sudden my xend is crashing, when i do "xm create domu" due to
which the domains are created in paused state. 

Iam using minios as domU kernel, but the problem occurs even for
linux-2.6.18.1 pv kernel as domu kernel.

xend.log shows

[2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to
signal 11!  Restarting it....

after doing some preliminary investigation i found out the problem is
due to the change in virt_kend value, being derived from elf->pend
value. Due to this domU is throwing seg_faults

When things were fine the value of virt_kend used to be 0x1e1a4, but now
virt_kend is having value 0x1dfa4. I have no clue why this is happening
suddenly. Any clue or hints would be very helpful.   

here is a sample domain_builder log when xend crashes....

xc_dom_parse_image: called
xc_dom_find_loader: trying ELF-generic loader ... OK
elf_parse_binary: phdr: paddr=0x0 memsz=0x1dfa4
elf_parse_binary: memory: 0x0 -> 0x1dfa4
elf_xen_parse: __xen_guest:
"GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,PAE=yes,LOADER=generic"
elf_xen_parse_guest_info: GUEST_OS="Mini-OS"
elf_xen_parse_guest_info: XEN_VER="xen-3.0"
elf_xen_parse_guest_info: VIRT_BASE="0x0"
elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0"
elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2"
elf_xen_parse_guest_info: PAE="yes"
elf_xen_parse_guest_info: LOADER="generic"
elf_xen_addr_calc_check: addresses:
    virt_base        = 0x0
    elf_paddr_offset = 0x0
    virt_offset      = 0x0
    virt_kstart      = 0x0
    virt_kend        = 0x1dfa4
    virt_entry       = 0x0
xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0x0 -> 0x1dfa4
xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each
xc_dom_mem_init: 0x2000 pages
xc_dom_boot_mem_init: called
x86_compat: guest xen-3.0-x86_32p, address size 32


here is the log when xend is intact....

xc_dom_parse_image: called
xc_dom_find_loader: trying ELF-generic loader ... OK
elf_parse_binary: phdr: paddr=0x0 memsz=0x1e1a4
elf_parse_binary: memory: 0x0 -> 0x1e1a4
elf_xen_parse: __xen_guest:
"GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,PAE=yes,LOADER=generic"
elf_xen_parse_guest_info: GUEST_OS="Mini-OS"
elf_xen_parse_guest_info: XEN_VER="xen-3.0"
elf_xen_parse_guest_info: VIRT_BASE="0x0"
elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0"
elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2"
elf_xen_parse_guest_info: PAE="yes"
elf_xen_parse_guest_info: LOADER="generic"
elf_xen_addr_calc_check: addresses:
    virt_base        = 0x0
    elf_paddr_offset = 0x0
    virt_offset      = 0x0
    virt_kstart      = 0x0
    virt_kend        = 0x1e1a4
    virt_entry       = 0x0
xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0x0 -> 0x1e1a4
xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each
xc_dom_mem_init: 0x2000 pages
xc_dom_boot_mem_init: called
x86_compat: guest xen-3.0-x86_32p, address size 32



Thanks,
  Sandesh

\m/   \m/


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] xend crashing due to change in virt_kend value...??, Sandesh <=