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-users

[Xen-users] Custom kernel always crashes

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Custom kernel always crashes
From: PAINCHAUD Christophe <cpainchaud@xxxxxxxxxxx>
Date: Thu, 3 Nov 2005 17:12:01 +0100
Delivery-date: Thu, 03 Nov 2005 16:09:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hello there,

        I am running a few Xen hosts. Until now I've always been using your binary packages and I was happy with them. But I needed to compile MPPE support for a customer domU. So I downloaded kernel sources et xen sources. I "Xenefied" my kernel sources, played a bit with its configuration and ran

  1 - make ARCH=xen menuconfig
  2 - make ARCH=xen
  3 - make ARCH=xen install

        My problem happens when I try to use this new kernel for the domU : xm create /etc/xen/testdom -c  opens a console but nothing happens, it remains empty. And if I check logs it says that my domain crashed (copy of xend.log and xen-debug.log below). In my domain config file, if I put back the stock kernel from your binary package, it works perfectly again. Doest it come from the fact that I used a custom kernel with your binaries (incompatible compiling options or anything like that) ?

Xend.log output:

[2005-11-03 16:30:51 xend] DEBUG (XendDomainInfo:720) init_domain> Created domain=18 name=TestDom memory=64
[2005-11-03 16:30:51 xend] INFO (console:94) Created console id=14 domain=18 port=9618
[2005-11-03 16:30:51 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=18 uname=file:/xen_filesystems/testdom.ext2
[2005-11-03 16:30:51 xend] DEBUG (blkif:155) Connecting blkif <BlkifBackendInterface 18 0>
[2005-11-03 16:30:51 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=18 uname=phy:hda4
[2005-11-03 16:30:51 xend] DEBUG (blkif:155) Connecting blkif <BlkifBackendInterface 18 0>
[2005-11-03 16:30:51 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=18 vif=0 mac=aa:00:00:00:00:11
[2005-11-03 16:30:51 xend] INFO (XendRoot:113) EVENT> xend.console.create [14, 18, 9618]
[2005-11-03 16:30:51 xend] INFO (XendRoot:113) EVENT> xend.domain.create ['TestDom', '18']
[2005-11-03 16:30:51 xend] INFO (XendRoot:113) EVENT> xend.domain.unpause ['TestDom', '18']
[2005-11-03 16:30:52 xend] DEBUG (XendDomain:244) XendDomain>reap> domain died name=TestDom id=18
[2005-11-03 16:30:52 xend] INFO (XendDomain:568) Destroying domain: name=TestDom
[2005-11-03 16:30:52 xend] DEBUG (XendDomainInfo:665) Destroying vifs for domain 18
[2005-11-03 16:30:52 xend] DEBUG (netif:305) Destroying vif domain=18 vif=0
[2005-11-03 16:30:52 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain 18
[2005-11-03 16:30:52 xend] DEBUG (blkif:552) Destroying blkif domain=18
[2005-11-03 16:30:52 xend] DEBUG (blkif:408) Destroying vbd domain=18 idx=0
[2005-11-03 16:30:52 xend] DEBUG (blkif:408) Destroying vbd domain=18 idx=1
[2005-11-03 16:30:52 xend] DEBUG (XendDomainInfo:634) Closing console, domain 18
[2005-11-03 16:30:52 xend] DEBUG (XendDomainInfo:622) Closing channel to domain 18
[2005-11-03 16:30:52 xend] INFO (XendRoot:113) EVENT> xend.virq 4
[2005-11-03 16:30:52 xend] DEBUG (blkif:363) Unbinding vbd (type file) from /dev/loop1
[2005-11-03 16:30:52 xend] DEBUG (blkif:363) Unbinding vbd (type phy) from hda4
[2005-11-03 16:30:52 xend] INFO (XendRoot:113) EVENT> xend.domain.exit ['TestDom', '18', 'crash']
[2005-11-03 16:30:52 xend] INFO (XendRoot:113) EVENT> xend.domain.destroy ['TestDom', '18']
[2005-11-03 16:30:53 xend] INFO (XendRoot:113) EVENT> xend.domain.died ['TestDom', '18']

Xend-debug.log

vif-bridge down vif=vif-testdom domain=TestDom mac=aa:00:00:00:00:11 bridge=xen-br0
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c05b2fe4
 Init. ramdisk: c05b3000->c05b3000
 Phys-Mach map: c05b3000->c05c3000
 Page tables:   c05c3000->c05c6000
 Start info:    c05c6000->c05c7000
 Boot stack:    c05c7000->c05c8000
 TOTAL:         c0000000->c0800000
 ENTRY ADDRESS: c0100000
ioctl: LOOP_SET_FD: Device or resource busy
25: vif21.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
25: vif-testdom: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
vif-bridge up vif=vif-testdom domain=TestDom mac=aa:00:00:00:00:11 bridge=xen-br0
VirqClient.virqReceived> 4
vif-bridge down vif=vif-testdom domain=TestDom mac=aa:00:00:00:00:11 bridge=xen-br0

PAINCHAUD Christophe

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Custom kernel always crashes, PAINCHAUD Christophe <=