While attempting to install snv_85 as a domU, Debian etch as the dom0, the kernel panics before the rest of the system starts to boot. Currently I'm using the sid releases of xen 3.2 found in Debian sid. I stopped using 3.0.3, as it appears I'm unable to use a ramdisk setting.
# dmesg | grep -i mem ... Memory: 1903728k/1949252k available (1623k kernel code, 36208k reserved, 593k data, 148k init, 1203788k highmem) 2.3.6.ds1-13etch5 libc6-xen 3.2.0-4 libxenstore3.0 2.6.18+6etch3 linux-image-2.6-xen-vserver-686 2.6.18.dfsg.1-18etch1 linux-image-2.6.18-6-xen-vserver-686 2.6.18.dfsg.1-18etch1 linux-modules-2.6.18-6-xen-vserver-686 3.2.0-4 xen-docs-3.2 3.2.0-4 xen-hypervisor-3.2-1-i386 3.2.0-4 xen-utils-3.2-1 3.2.0-2 xen-utils-common 3.2.0-4 xenstore-utils I was able to boot and start installing off of a 66-0624 kernel+ramdisk. However, when I boot the installed system I get the same results. I can boot with 66 manually, and I'm forced to choose between two installed OS's. The suggested workaround for editing blkif.py was already applied. I decided to start over and only use svn_85. I already wiped the first 20mb of /dev/mapper/Debian-opensolaris with 0's. I don't think chgset 'unavailable' has anything to do with it, as I've seen that same message in an Oracle blog screen-shot. Here's what happens when I try to install... # cat /etc/solaris.py on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' # vif = [ 'mac=00:16:3e:85:86:70' ] name = 'solaris' memory = '1024' disk = [ 'file:/usr/local/lib/xen/sol-nv-b85-x86-dvd.iso,6:cdrom,r' , 'phy:mapper/Debian-opensolaris,0,w' ] bootloader = '/usr/lib/xen-3.2-1/bin/pygrub' kernel = '/boot/platform/i86xpv/kernel/unix' ramdisk = '/boot/x86.miniroot' extra = '/platform/i86xpv/kernel/unix - nowin -B install_media=cdrom' # xm create -c solaris.py Using config file "./solaris.py". Started domain solaris v3.2-1 chgset 'unavailable' SunOS Release 5.11 Version snv_85 32-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. panic[cpu0]/thread=f5028f20: [b]recursive mutex_enter[/b], lp=d245efd8 owner=f5028f20 thread=f5028f20 f5053454 unix:mutex_panic+55 (f50099e8, d245efd8) f5053494 unix:mutex_vector_enter+185 (d245efd8) f50534cc unix:x86pte_mapin+5f (3e244, 0, d26d7e38) f50534e4 unix:x86pte_access_pagetable+32 (d26d7e38, 0) f5053504 unix:x86pte_get+15 (d26d7e38, 0) f5053538 unix:htable_getpte+72 (d2461f68, d2800000,) f5053570 unix:hat_getattr+2c (d2461f68, d2800ee8,) f5053600 unix:trap+12f (f5053614, d2800ee8,) f5053614 unix:_cmntrap+aa (f4c101b1, 32b0000, ) f50536c0 unix:atomic_cas_64+16 (d26d7e38, 1dd, 23b6) f505371c unix:hati_pte_map+143 (d26d7e38, 1dd, 0, 2) f5053760 unix:hati_load_common+12f (d2461f68, d29dd000,) f50537c4 unix:hat_devload+10b (d2461f68, d29dd000,) f5053818 unix:gnttab_init+bb (f4c4fe1e, 3, f50538) f5053828 unix:startup_modules+fb (f5053840, f4d3d64a,) f5053830 unix:startup+35 (f4c00010, f504f648,) f5053840 genunix:main+1e () skipping system dump - no dump device configured rebooting... This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
