Hi Boris, Boris Derzhavets wrote: ... > [EMAIL PROTECTED] vm]# cat Solaris76run.conf > name = "Solaris76" > vcpus = 1 > memory = "1024" > kernel = "/usr/lib/xen-solaris/unix-76" > ramdisk = "/usr/lib/xen-solaris/x86.miniroot-76" > extra = "/platform/i86xpv/kernel/amd64/unix -kd" > disk = ['phy:sdb8,sdb8,w'] > vif = [''] > root ="/dev/dsk/c0d134511472s0" > on_shutdown = "destroy" > on_reboot = "destroy" > on_crash = "destroy" ... > [EMAIL PROTECTED] vm]# xm create -c Solaris76run.conf > Using config file "./Solaris76run.conf". > Started domain Solaris76 > Loading kmdb... > > Welcome to kmdb > Loaded modules: [ unix krtld genunix ] > [0]> ::bp xnf`xnf_attach > [0]> :c > SunOS Release 5.11 Version snv_76 64-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > > panic[cpu0]/thread=fffffffffbc3fe60: cannot mount root path /xpvd/[EMAIL > PROTECTED]:a > > fffffffffbc72f90 genunix:rootconf+11f () > fffffffffbc72fe0 genunix:vfs_mountroot+65 () > fffffffffbc73010 genunix:main+d3 () > fffffffffbc73020 unix:_locore_start+80 () > > panic: entering debugger (no dump device, continue to reboot)
Given that you're panicing in vfs_mountroot, that means the device which your /etc/vfstab tells your domU to look at for / is not valid. I'm very curious how you got > root ="/dev/dsk/c0d134511472s0" since I have never seen an PATA- or SATA-attached disk ever have a dY larger than 1 (ie, cXdYsZ). How did you get that value? And if you change it in the conf file to c0d1s0, does that help your booting process? James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ xen-discuss mailing list [email protected]
