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] “domain crashed” when creating new Xen instance (Unhandled i

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] “domain crashed” when creating new Xen instance (Unhandled invalid opcode fault/trap [#6] in domain)
From: Tom <tom@xxxxxxxxxxxxxxxx>
Date: Wed, 02 Mar 2011 08:16:53 +0000
Delivery-date: Wed, 02 Mar 2011 00:18:20 -0800
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
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc13 Lightning/1.0b3pre Thunderbird/3.1.7
I have downloaded a Xen virtual machine image from the appscale project, and I am trying to start it up. However once I run the command;

    xm create -c -f xen.conf

The instance immediately crashes and provides no console output. however it produces logs that I have posted below. but this is the error;

[2011-03-01 12:34:03 xend.XendDomainInfo 3580] WARNING (XendDomainInfo:1178) Domain has crashed: name=appscale-1.4b id=10.

In the output from "xm dmesg" it has this;
(XEN) sysctl.c:51: Allowing physinfo call with newer ABI version
(XEN) mm.c:1471:d2 Bad L1 flags 800000
(XEN) traps.c:405:d2 Unhandled invalid opcode fault/trap [#6] in domain 2 on VCPU 0 [ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 2 (vcpu#0) crashed on cpu#3:
(XEN) ----[ Xen-3.1.2-194.32.1.el5  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    3
(XEN) RIP:    e033:[<ffffffff8020b612>]

here is the full output http://fpaste.org/w1Bm/

I have managed to mount the root.img file locally and verify that it is actually an ext3 file system.

I am running Xen 3.0.3 that is a stock RPM from the CentOS 5 repos;

    # rpm -qa | grep -i xen xen-libs-3.0.3-105.el5_5.5
    xen-3.0.3-105.el5_5.5
    xen-libs-3.0.3-105.el5_5.5
    kernel-xen-2.6.18-194.32.1.el5


any suggestions on how to proceed with troubleshooting? (i am a newbie to Xen)

so far I have enabled console logging, but the log file is empty.

All the output into the log files is included here;
http://fpaste.org/va2s/


my startup configuration is like this;
# cat xen.conf

# Configuration file for the Xen instance AppScale, created
# bn VMBuilder
kernel = '/boot/vmlinuz-2.6.27-7-server'
ramdisk = '/boot/initrd.img-2.6.27-7-server'
memory = 1024
vcpus = 1

#gateway   = 192.168.2.1
#netmask   = 255.255.255.0
#broadcast = 192.168.2.255

root = '/dev/sda1 ro'
disk = [
'file:/local/xen/domains/appscale1.4/root.img,sda1,w',
]

name = 'appscale-1.4b'

dhcp    = 'dhcp'
vif         = [ 'mac=00:16:3B:72:10:E4' ]

on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

extra = 'xencons=tty console=tty1 console=hvc0 debugger=y debug=y sync_console'







any suggestions on what the problem is?

Thanks,
Tom








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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] “domain crashed” when creating new Xen instance (Unhandled invalid opcode fault/trap [#6] in domain), Tom <=