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] DomU stuck in boot

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] DomU stuck in boot
From: Thomas Graves <tgraves@xxxxxxxxxxxxx>
Date: Wed, 16 Jun 2010 14:31:05 -0700
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Wed, 16 Jun 2010 14:35:07 -0700
Domainkey-signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:from:to:date:subject:thread-topic:thread-index: message-id:accept-language:content-language:x-ms-has-attach: x-ms-tnef-correlator:acceptlanguage:content-type: content-transfer-encoding:mime-version; b=BXjN9PqVBo1NGEy5Xo1pDqo33g5ey269A/kDZd1ZspZpXMoZrJymvO3xzZBHvmzj
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsNmzm9r8Qs6aFGSkW2Oj0tJShIjQ==
Thread-topic: DomU stuck in boot
Hello,

I am running xen-3.3.1 with rhel5.3 dom0.
I have a rhel5.3 domU that is stuck in the boot process. It seems it is
trying to bring up the network.  We see this problem only occassionally.

This is the last console output:
Running configure_os...
Warning: Configuring networking...
Warning: HOSTNAME is not defined
Updating ifcfg-eth0 [  OK  ]
Allowing IPv4 link local addresses [  OK  ]
Warning: Starting networking...
Bringing up loopback interface:  [  OK  ]

It has been stuck for a few days now. I did a dump-core on it and it seems
to be doing network start -> ifup-eth ifcfg-eth0 boot -> ip link set dev
eth0 up -> hypercall.  I'm somewhat assuming it made the hypercall but never
got the event back but I'm not sure as I'm new to this.   Does anyone have a
good pointers on how exactly hypercalls work or any info on looking at
event-channels?  Any ideas why it might be stuck?


PID: 1290   TASK: ffff88007f7b50c0  CPU: 0   COMMAND: "ip"
ARG: ip link set dev eth0 up
ENV: TERM=linux
     OLDPWD=/etc/sysconfig/network-scripts
     PATH=/sbin:/usr/sbin:/bin:/usr/bin
     PWD=/etc/sysconfig/network-scripts
     LANG=en_US.UTF-8
     SHLVL=2
     _=/sbin/ip


Backtrace:
PID: 1290   TASK: ffff88007f7b50c0  CPU: 0   COMMAND: "ip"
 #0 [ffff88007c135d08] schedule at ffffffff80261e17
 #1 [ffff88007c135d50] hypercall_page at ffffffff8020622a
 #2 [ffff88007c135d78] hypercall_page at ffffffff8020622a
 #3 [ffff88007c135da0] __netif_rx_schedule at ffffffff80410360
 #4 [ffff88007c135dc0] network_open at ffffffff8810c992
 #5 [ffff88007c135de0] dev_open at ffffffff80411cd2
 #6 [ffff88007c135df0] dev_change_flags at ffffffff80410263
 #7 [ffff88007c135e20] devinet_ioctl at ffffffff80443763
 #8 [ffff88007c135ec0] sock_ioctl at ffffffff80408968
 #9 [ffff88007c135ee0] do_ioctl at ffffffff802437ba
#10 [ffff88007c135f00] vfs_ioctl at ffffffff80231010
#11 [ffff88007c135f40] sys_ioctl at ffffffff8024ddde
#12 [ffff88007c135f80] system_call at ffffffff8025f106
    RIP: 00002b5bbbf43c77  RSP: 00007fffef0627f8  RFLAGS: 00000246
    RAX: 0000000000000010  RBX: ffffffff8025f106  RCX: ffffffff8025f080
    RDX: 00007fffef062830  RSI: 0000000000008914  RDI: 0000000000000006
    RBP: 00007fffef062830   R8: 00007fffef062834   R9: 0000000000000003
    R10: 0000000000000000  R11: 0000000000000246  R12: 0000000000000001
    R13: 0000000000000001  R14: 0000000000000006  R15: 0000000000000000
    ORIG_RAX: 0000000000000010  CS: e033  SS: e02b

>From dom0 it looks like the network is setup right for the vif, they are
definitely all dropping packets right now though but I figured that was due
to the domU not finishing its setup:

vif912.0  Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109 errors:0 dropped:785242 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 b)  TX bytes:7501 (7.3 KiB)


Thanks,
Tom


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

<Prev in Thread] Current Thread [Next in Thread>