[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 850] Random crash after relaunching a xen domU halted



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=850





------- Comment #1 from baco@xxxxxxxx  2007-01-09 07:49 -------
You can reproduce this by

# create a myxen.cfg binded to xenbr0
xm create -c myxen.cfg
# after a while in the myxen do "halt"
# change myxen.cfg to bind to xenbr1
# juste after "haled" launch
xm create myxen.cfg
# at this point random failure of Xen
# failure experimented can be :
# - all domU down, dom0 too with "kernel BUG at drivers/xen/core/evtchn.c:481!"
# - vif/network of a random running domU got disconnected

As workaround i have the following bash script
to be sure the xen domU was correctly shutdown

# Be sure the xen was shutdown before restart
sync; sync; sync
open=1
running=1
dryrun=""
while [ $open -ne 0 ] || [ $running -ne 0 ]; do
        open=$(lvdisplay "/dev/${volume_group}/${host_name}.sda2" | \
        awk '/# open/ { print $3 }')
        if ! ${XM} list | grep -q -E "^${host_name}"; then
                running=0
        fi
        echo "Waiting shutdown of ${host_name}..."
        sleep 1
done
while [ "$dryrun" != "PASSED" ]; do
        dryrun=$(${XM} dry-run "${host_name}.cfg" | awk '/Dry Run:/ { print $3
}
')
        echo "Waiting for a passed dry-run..."
        sleep 1
done
for (( i=10 ; $i>0 ; i=$(($i-1)) )); do
        echo "Waiting for $i seconds..."
        sleep 1
done


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.