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] Trying to Run OpenSolaris PV

To: "XEN Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Trying to Run OpenSolaris PV
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Mon, 07 Dec 2009 08:48:00 -0700
Delivery-date: Mon, 07 Dec 2009 07:49:36 -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
Hey, everyone,
I'm running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run 
correctly.  I've followed a couple of the instruction sets out on the Xen wiki 
and other folks blogs, but I'm running into an issue with the domU crashing.  
The OpenSolaris version is the latest development release - 5.11-0.128.  The 
config looks like this:

name="ImageServer"
uuid="e1ba32be-9789-d187-dc94-6cf25ea17d9e"
memory=1024
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
kernel="/etc/xen/vm/osol-5.11-0.128a"
ramdisk="/etc/xen/vm/osol-5.11-0.128a.boot"
extra="/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"
disk=[ 'file:/xenstore/nfs/ImageServer/disk0,0,w', 
'file:/xenstore/iso/Solaris/osol-dev-128a-ai-x86.iso,6:cdrom,r', ]
vif=[ 'mac=00:16:3e:11:be:de,bridge=xenbr30', ]
serial="pty"

The domU appears to try to start, but immediately crashes.  When I look at xm 
dmesg, I get the following output:


(XEN) Unhandled page fault in domain 119 on VCPU 0 (ec=0002)
(XEN) Pagetable walk from 0000000000000000:
(XEN)  L4[0x000] = 00000001e7127067 0000000000007a0c
(XEN)  L3[0x000] = 0000000000000000 ffffffffffffffff 
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 119 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.2.3_17040_17-0.5_24_xtp  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e033:[<fffffffffb891e08>]
(XEN) RFLAGS: 0000000000000206   CONTEXT: guest
(XEN) rax: 000000000000002f   rbx: 0000000000000006   rcx: 0000000000000034
(XEN) rdx: 0000000000000017   rsi: 000000004080ebd0   rdi: 0000000000000000
(XEN) rbp: 000000004080eb30   rsp: 000000004080ead0   r8:  000000004080ebed
(XEN) r9:  0000000047fff000   r10: 0000000000007ff0   r11: 0000000000000246
(XEN) r12: 000000004080ebe7   r13: 0000000000000017   r14: 0000000000000000
(XEN) r15: 000000004080ebd0   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 000000015f45f000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=000000004080ead0:
(XEN)    0000000000000034 0000000000000246 0000000000000002 fffffffffb891e08
(XEN)    000000010000e030 0000000000010006 000000004080eb18 000000000000e02b
(XEN)    000000004080f010 0000000000000017 000000004080ebd0 0000000000000000
(XEN)    000000004080eb90 fffffffffb831f6d 000000004080eb60 ff003436646d612f
(XEN)    0000000000000000 0000000000000000 0000000000000000 000000004080ebd0
(XEN)    0000000000000000 0000000000000000 000000004080ebd0 0000000000000000
(XEN)    000000004080ebc0 fffffffffb8b5df3 000000004080f010 0000000000000000
(XEN)    000000004080f010 000000004080ebd0 000000004080f000 fffffffffb8b4e0b
(XEN)    726f6674616c702f 7670783638692f6d 2f6c656e72656b2f 6e752f3436646d61
(XEN)    0000000000007869 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000

xm log indicates that memory is assigned correctly, and that all of the hotplug 
scripts to assign network and block devices run just fine.  Then I get the 
following entry:

[2009-12-07 08:46:00 12618] WARNING (XendDomainInfo:1269) Domain has crashed: 
name=ImageServer id=119.

Can anyone offer any advice as to what may be going on, what I need to do to 
debug it further, or what to do to solve this issue?

Thanks!
-Nick


--------
This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

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