Hi, List. I''ve been trying for weeks to get a Solaris domU running on my Linux dom0. I''ve tried example configs from numerous sources; current effort is pasted below. (Largely cribbed from http://wiki.tardis.ed.ac.uk/index.php/OpenSolaris_Xen_domU). Currently I''m using Xen 3.2.1 on Linux (Gentoo), kernel version 2.6.21. The domU is trying to boot an ISO of the 2008/05 release of OpenSolaris. I''ve copied i86xpv/kernel/amd64 kernel and /boot/x86.microroot from the OpenSolaris ISO into the locations listed in my config file, and the "extra" line is copied verbatim from the source linked above. When I try to boot with this configuration, ''xm create'' starts the domain, but it immediately crashes. I don''t get any qemu-dm log file for the domain, and I don''t know enough about the contents of xend.log or domain-builder-ng.log to be able to tell if there''s anything nasty being reported there, though nothing jumps out at me as obviously wrong. Any suggestions for further debugging? Thanks, --Michael [begin xm config file] import os, re name = "dumb" memory = "2048" vcpus = "2" disk = [ ''file:/xen/isos/opensolaris200805.iso,6:cdrom,r'', ''phy:/dev/mapper/pile-dumb.solaris.root,0,w'', ''phy:/dev/mapper/pile-dumb.solaris.swap,1,w'' ] vif = [ '''' ] kernel = ''/xen/boot/os200805/amd64/unix'' ramdisk = ''/xen/boot/os200805/x86.microroot'' extra = ''/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom'' vfb = [ ''type=vnc, vnclisten=0.0.0.0, vncpasswd=l3m0n'' ] # eventually i''ll need to pass a PCI device to this domain # pci = [''80:09.0''] on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, i think you have to recompile xen3.2.1 or running solaris not as a HVM - Please refer to these links: http://bderzhavets.blogspot.com/2008/03/install-solaris-0108-hvm-domu-64 -bit-at.html http://bderzhavets.blogspot.com/2008/04/install-hvm-s10-u4-domu-32-bit-a t-xen-3.html If there''s another solution for HVM solaris without recompiling xen, I''m interesting in (-: Question: Is there an impact relating this recompilation with "VMXASSIST disabled" to other HVM''s (windows xp, ..) regards Danny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 12:14:31AM +0200, Daniel Schwager wrote:> Hi, > i think you have to recompile xen3.2.1 or running solaris > not as a HVM - Please refer to these links: > > http://bderzhavets.blogspot.com/2008/03/install-solaris-0108-hvm-domu-64 > -bit-at.html > > http://bderzhavets.blogspot.com/2008/04/install-hvm-s10-u4-domu-32-bit-a > t-xen-3.htmlThose refer to HVM domains. Supposedly, OpenSolaris can run in PVM mode, which is why I''m using the "i86xpv" kernel. They also refer to an older release of OpenSolaris than the one I''m running, which (I read) includes at least a couple of Xen-related fixes, so I don''t know how applicable any of that information will be to my case. I can run in HVM mode if I have to, but previous attempts to do so have failed. I also haven''t been able to find out for sure whether HVM domains can support pass-through of a PCI device, which is something I''ll definitely need to do, so I''m trying to get PVM working if at all possible. Thanks, -m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, May 08, 2008 at 05:08:32PM -0500, Michael Jinks wrote:> The domU is trying to boot an ISO of the 2008/05 release of OpenSolaris. > I''ve copied i86xpv/kernel/amd64 kernel and /boot/x86.microroot from the > OpenSolaris ISO into the locations listed in my config file, and the > "extra" line is copied verbatim from the source linked above.OpenSolaris is different from the versions you tried before. In particular the extra line. See: http://blogs.sun.com/mrj/ Though you say you''ve been trying for weeks, so if both OpenSolaris and SXCE are crashing, it must be some other problem. add " -kd" to the options and it should drop you into the kernel debugger. Type "::stack" to see what the stack trace is. Also which builds of SXCE did you try? regards john _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 12:06:16AM +0100, John Levon wrote:> On Thu, May 08, 2008 at 05:08:32PM -0500, Michael Jinks wrote: > > > The domU is trying to boot an ISO of the 2008/05 release of OpenSolaris. > > I''ve copied i86xpv/kernel/amd64 kernel and /boot/x86.microroot from the > > OpenSolaris ISO into the locations listed in my config file, and the > > "extra" line is copied verbatim from the source linked above. > > OpenSolaris is different from the versions you tried before. In > particular the extra line. See: > > http://blogs.sun.com/mrj/Thanks. I''ve read MRJ''s blog at various points along my journey...> Though you say you''ve been trying for weeks, so if both OpenSolaris and > SXCE are crashing,What''s SXCE?> it must be some other problem.Oh yeah... :) I''ve had several different problems at various stages. For example, using Nevada build 87 and Xen 3.2.0, I was able to get the install CD to boot and install the system, but it would kernel panic when booting into the installed OS. Looking for the cause, I found some indication that my trouble might be fixed by an upgrade, but since moving to Xen 3.2.1 and OS2008/05, I can''t get the install CD to boot.> add " -kd" to the > options and it should drop you into the kernel debugger.Okay, my Solaris kernel command line mojo is pretty weak... I changed my "extra" line to read: extra = ''/platform/i86xpv/kernel/amd64/unix -kd'' Was that right, or should I have left the "-B console=ttya,livemode=text" parts in place? At any rate, when I try to boot with that I do get into the debugger. Typing "::stack" returns: kmdb_enter+0xb() mlsetup+0x35c(fffffffffbc6ee28) _locore_start+0x7b() Does that tell you anything?> Also which builds of SXCE did you try?I''ve only tried Nevada build 87 previous to this. BTW, I''ve just logged into the IRC channel and I see you''re there too, would be happy to take this over there if it''s easier. Thanks much, -m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, May 08, 2008 at 06:28:21PM -0500, Michael Jinks wrote:> On Fri, May 09, 2008 at 12:06:16AM +0100, John Levon wrote: > > On Thu, May 08, 2008 at 05:08:32PM -0500, Michael Jinks wrote: > > > > > The domU is trying to boot an ISO of the 2008/05 release of OpenSolaris. > > > I''ve copied i86xpv/kernel/amd64 kernel and /boot/x86.microroot from the > > > OpenSolaris ISO into the locations listed in my config file, and the > > > "extra" line is copied verbatim from the source linked above. > > > > OpenSolaris is different from the versions you tried before. In > > particular the extra line. See: > > > > http://blogs.sun.com/mrj/ > > Thanks. I''ve read MRJ''s blog at various points along my journey...Should have mentioned... before trying the " -kd" session, I did try again with the config listed on MRJ''s blog, path names adjusted for my system. Whenever I try to use pygrub, xm always gives: Error: Boot loader didn''t return any data! I haven''t had much luck tracking down the meaning of that error... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, May 08, 2008 at 06:28:21PM -0500, Michael Jinks wrote:> > http://blogs.sun.com/mrj/ > > Thanks. I''ve read MRJ''s blog at various points along my journey... > > > Though you say you''ve been trying for weeks, so if both OpenSolaris and > > SXCE are crashing, > > What''s SXCE?Solaris Express Community Edition, presumably how you were testing Nevada.> > it must be some other problem. > > Oh yeah... :) > > I''ve had several different problems at various stages. For example, > using Nevada build 87 and Xen 3.2.0, I was able to get the install CD toYes, Xen 3.2.0 has a compatibility bug with Solaris.> > add " -kd" to the > > options and it should drop you into the kernel debugger. > > Okay, my Solaris kernel command line mojo is pretty weak... I changed my > "extra" line to read: > > extra = ''/platform/i86xpv/kernel/amd64/unix -kd'' > > Was that right, or should I have left the "-B > console=ttya,livemode=text" parts in place? At any rate, when I try to > boot with that I do get into the debugger. Typing "::stack" returns: > > kmdb_enter+0xb() > mlsetup+0x35c(fffffffffbc6ee28) > _locore_start+0x7b()Ooops, first do: :c to continue booting. regards john _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Levon wrote:> On Thu, May 08, 2008 at 06:28:21PM -0500, Michael Jinks wrote: > >>> it must be some other problem. >>> >> Oh yeah... :) >> >> I''ve had several different problems at various stages. For example, >> using Nevada build 87 and Xen 3.2.0, I was able to get the install CD to >> > > Yes, Xen 3.2.0 has a compatibility bug with Solaris. > >Really? I didn''t know that. Glad I sticked with RH''s version of Xen :D Michael, you might find it easier to also look at here http://bderzhavets.blogspot.com/2008/01/install-opensolaris-snv78-domu-at.html It''s for CentOS/RHEL 5.1 x86_64, using RH''s version of Xen, with a minor edit for blkif.py. It also uses a spesific version of Opensolaris (b78), but any later version should work as well. In my setup, I''ve tested b75a and b79b, both worked fine. However, after the install process completed, instead of copying the updated boot-archive to dom0, I simply modify xen config file to use pygrub. Copying doesn''t work because at the time the network (in my case anyway) was unusable (xnf:xnf_cksum_offload = 0 was not activated yet). There is a bug though : everytime the solaris domU is restarted, a zombie domain appears. I was told this was fixed in recent versions of Xen, but since I only use it for testing purposes I decided to wait for RHEL 5.2. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 01:45:29AM +0100, John Levon wrote:> On Thu, May 08, 2008 at 06:28:21PM -0500, Michael Jinks wrote: ><snip>> > extra = ''/platform/i86xpv/kernel/amd64/unix -kd'' > > > > Ooops, first do: > > :c > > to continue booting.Okay, did that. Output is at: http://pastebin.com/d1d7a10ff Thanks for your help. -mrj _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 08:13:07AM +0700, Fajar A. Nugraha wrote:> > Michael, you might find it easier to also look at here > http://bderzhavets.blogspot.com/2008/01/install-opensolaris-snv78-domu-at.html > > It''s for CentOS/RHEL 5.1 x86_64, using RH''s version of Xen, with a minor > edit for blkif.py.Thanks; don''t really have the option of using RedHat currently on this hardware, but you''ve reminded me of something else I should have mentioned, which is that the Xen I am using is the Gentoo build. I don''t know if they do anything weird with their build process or not, if there are any known issues that pertain to Solaris guests... Windows (HVM) and Linux (PVM) domU''s have both worked fine, for whatever that might be worth. Cheers, -mrj _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 01:45:57AM -0500, Michael Jinks wrote:> > don''t know if they do anything weird with their build process or not, if > there are any known issues that pertain to Solaris guests... Windows > (HVM) and Linux (PVM) domU''s have both worked fine, for whatever that > might be worth.This prompted me to double check that other domU''s still work after my upgrade from Xen 3.2.0 to 3.2.1, and that made me realize that I didn''t have my dom0''s tun/tap device loaded, something that''s bitten me in the past. With that in place, Solaris gets further, or appears to; the domain sticks around according to ''xm list'', but the VNC console doesn''t show up, and ''xm console'' croaks: xenconsole: Could not read tty from store: No such file or directory I''ve seen that error before while trying to boot Solaris, and googling for it leaves me thinking that there are lots of reasons it can happen, but for the moment I don''t know what''s going on in my case, and since I can''t get a console I don''t know what state my domU is really in. Funny, too, since xm console worked fine for this domU a few hours ago, and I don''t think I''ve changed much since then other than loading the tun module. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 02:11:05AM -0500, Michael Jinks wrote:> > This prompted me to double check that other domU''s still work after my > upgrade from Xen 3.2.0 to 3.2.1, and that made me realize that I didn''t > have my dom0''s tun/tap device loaded, something that''s bitten me in the > past. > > With that in place, Solaris gets further, or appears to;I sent too soon. The domain was sticking around, but it was apparently because I still had "-kd" in my kernel command line, not because it was being made happier by a tap device. If I have the tun/tap driver loaded in dom0, "xm console" and "xm create -c" both bail out with the "Could not read tty" message. If I unload the tun module, I get a serial connection again, where I can watch the kernel panic and die just like it did before. But then my HVM domains fail to boot. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
----- Original Message ---- From: Michael Jinks <mjinks@uchicago.edu> To: John Levon <levon@movementarian.org> Cc: Xen-users@lists.xensource.com Sent: Thursday, May 8, 2008 7:28:21 PM Subject: Re: [Xen-users] Solaris domU dies at boot On Fri, May 09, 2008 at 12:06:16AM +0100, John Levon wrote:> On Thu, May 08, 2008 at 05:08:32PM -0500, Michael Jinks wrote: > > > The domU is trying to boot an ISO of the 2008/05 release of OpenSolaris. > > I''ve copied i86xpv/kernel/amd64 kernel and /boot/x86.microroot from the > > OpenSolaris ISO into the locations listed in my config file, and the > > "extra" line is copied verbatim from the source linked above. > > OpenSolaris is different from the versions you tried before. In > particular the extra line. See: > > http://blogs.sun.com/mrj/Thanks. I''ve read MRJ''s blog at various points along my journey...> Though you say you''ve been trying for weeks, so if both OpenSolaris and > SXCE are crashing,What''s SXCE?> it must be some other problem.Oh yeah... :) I''ve had several different problems at various stages. For example, using Nevada build 87 and Xen 3.2.0, I was able to get the install CD to boot and install the system, but it would kernel panic when booting into the installed OS. Looking for the cause, I found some indication that my trouble might be fixed by an upgrade, but since moving to Xen 3.2.1 and OS2008/05, I can''t get the install CD to boot. Yes, it''s based on Nevada build 86 . You are supposed to failure. John Levon''s patch went into build 87. http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6650717 View also:- http://lxer.com/module/newswire/view/102728/index.html> add " -kd" to the > options and it should drop you into the kernel debugger.Okay, my Solaris kernel command line mojo is pretty weak... I changed my "extra" line to read: extra = ''/platform/i86xpv/kernel/amd64/unix -kd'' Was that right, or should I have left the "-B console=ttya,livemode=text" parts in place? At any rate, when I try to boot with that I do get into the debugger. Typing "::stack" returns: kmdb_enter+0xb() mlsetup+0x35c(fffffffffbc6ee28) _locore_start+0x7b() Does that tell you anything?> Also which builds of SXCE did you try?I''ve only tried Nevada build 87 previous to this. BTW, I''ve just logged into the IRC channel and I see you''re there too, would be happy to take this over there if it''s easier. Thanks much, -m _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 09, 2008 at 01:37:23AM -0500, Michael Jinks wrote:> <snip> > > > extra = ''/platform/i86xpv/kernel/amd64/unix -kd'' > > > > > > > Ooops, first do: > > > > :c > > > > to continue booting. > > Okay, did that. Output is at: http://pastebin.com/d1d7a10ff > > Thanks for your help.D''oh, I forgot that OpenSolaris was b86 based. It''s this bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6650717 It''s a Xen compatibility bug that we fixed in Solaris since it was already too late to fix Xen back. A more recent Solaris Express should work. Not sure when a newer OpenSolaris release will happen. regards john _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m still trying to get my Solaris domU working on a Gentoo dom0. With Robert''s help I now know the difference between Express and OpenSolaris, and I''m back to trying this with an Express ISO, Nevada build 87, now armed with the "-kd" kernel command line option. (This is the newest build available, right? And should work...?) I''m still getting a kernel panic when I try to boot the install ISO. Current config file is below, and the kernel panic I get when I try to boot the CD is pasted along with a stack printout, at: http://pastebin.org/35375 Thanks for all the help. -m == begin xm config = import os, re name = "dumb" memory = "2048" vcpus = "2" disk = [ ''file:/xen/isos/opensolaris200805.iso,6:cdrom,r'', ''phy:/dev/mapper/pile-dumb.solaris.root,0,w'', ''phy:/dev/mapper/pile-dumb.solaris.swap,1,w'' ] vif = [ '''' ] kernel = ''/xen/boot/sunos/solaris-b44/kernel/amd64/unix'' ramdisk = ''/xen/boot/sunos/solaris-b44/ramdisk/amd64/x86.miniroot'' extra = ''/boot/platform/i86xpv/kernel/amd64/unix -kd - nowin -B install_media=cdrom'' listen=0.0.0.0, vncpasswd=l3m0n'' ] vfb = [ ''type=vnc, vnclisten=0.0.0.0, vncpasswd=l3m0n'' ] on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[root@dhcppc0 vm]# xm info
host : dhcppc0
release : 2.6.18.8-xen
version : #1 SMP Wed May 7 03:29:50 EDT 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 3005
hw_caps :
bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001
total_memory : 4095
free_memory : 1030
node_to_cpu : node0:0-1
xen_major : 3
xen_minor : 2
xen_extra : .1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Fri May 02 14:23:07 2008 +0100 16888:9733f681d5c5
cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
cc_compile_by : root
cc_compile_domain : (none)
cc_compile_date : Wed May 7 03:31:05 EDT 2008
xend_config_format : 4
[root@dhcppc0 vm]# cat SNV87.conf
name = "Solaris87pvm"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-87"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-87"
extra = "/platform/i86xpv/kernel/amd64/unix"
disk = [''phy:/dev/sdb7,0,w'']
vif = [''bridge=eth0'']
root="/dev/dsk/c0d0s0"
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"
[root@dhcppc0 vm]# xm create -c SNV87.conf
Using config file "./SNV87.conf".
Started domain Solaris87pvm
v3.2.1 chgset ''Fri May 02 14:23:07 2008
+0100 16888:9733f681d5c5''
SunOS Release 5.11 Version snv_87 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: SunSolaris511
/dev/rdsk/c0d0s7 is clean
Reading ZFS config: done.
SunSolaris511 console login: root
Password:
Last login: Mon May 12 10:38:50 on console
May 12 10:45:56 SunSolaris511 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_87 January 2008
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0d0s0 12G 4.5G 7.6G 38% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 1.1G 952K 1.1G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap3.so.1
12G 4.5G 7.6G 38% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 1.1G 40K 1.1G 1% /tmp
swap 1.1G 40K 1.1G 1% /var/run
/dev/dsk/c0d0s7 2.4G 11M 2.3G 1% /export/home
#
----- Original Message ----
From: Michael Jinks <mjinks@uchicago.edu>
To: Xen-users@lists.xensource.com
Sent: Monday, May 12, 2008 1:22:44 AM
Subject: Re: [Xen-users] Solaris domU dies at boot
I''m still trying to get my Solaris domU working on a Gentoo dom0. With
Robert''s help I now know the difference between Express and
OpenSolaris,
and I''m back to trying this with an Express ISO, Nevada build 87, now
armed with the "-kd" kernel command line option. (This is the newest
build available, right? And should work...?)
I''m still getting a kernel panic when I try to boot the install ISO.
Current config file is below, and the kernel panic I get when I try to
boot the CD is pasted along with a stack printout, at:
http://pastebin.org/35375
Thanks for all the help.
-m
== begin xm config =
import os, re
name = "dumb"
memory = "2048"
vcpus = "2"
disk = [ ''file:/xen/isos/opensolaris200805.iso,6:cdrom,r'',
''phy:/dev/mapper/pile-dumb.solaris.root,0,w'',
''phy:/dev/mapper/pile-dumb.solaris.swap,1,w'' ]
vif = [ '''' ]
kernel = ''/xen/boot/sunos/solaris-b44/kernel/amd64/unix''
ramdisk =
''/xen/boot/sunos/solaris-b44/ramdisk/amd64/x86.miniroot''
extra = ''/boot/platform/i86xpv/kernel/amd64/unix -kd - nowin -B
install_media=cdrom''
listen=0.0.0.0, vncpasswd=l3m0n'' ]
vfb = [ ''type=vnc, vnclisten=0.0.0.0, vncpasswd=l3m0n'' ]
on_shutdown = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, May 12, 2008 at 12:22:44AM -0500, Michael Jinks wrote:> I''m still trying to get my Solaris domU working on a Gentoo dom0. With > Robert''s helpOf course I meant John. Sorry, it''s late... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m straightened out, at least partly. (Thanks Boris.) I was trying to go back to NV87 from OS08/05, and I''d switched everything except the ISO file, which was still the OpenSolaris CD. Oops. Putting that back to the Nevada 87 ISO, I''m now booting into the install routine as expected. If history repeats itself I''ll get a kernel panic once the OS is installed and trying to boot into the runtime kernel, but if that happens I''ll start a new thread. Thanks to everybody who pitched in to iron out my brain. Cheers, -- (a different) mrj On Mon, May 12, 2008 at 12:22:44AM -0500, Michael Jinks wrote:> I''m still trying to get my Solaris domU working on a Gentoo dom0. With > Robert''s help I now know the difference between Express and OpenSolaris, > and I''m back to trying this with an Express ISO, Nevada build 87, now > armed with the "-kd" kernel command line option. (This is the newest > build available, right? And should work...?) > > I''m still getting a kernel panic when I try to boot the install ISO. > Current config file is below, and the kernel panic I get when I try to > boot the CD is pasted along with a stack printout, at: > > http://pastebin.org/35375_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael , When you switch to runtime for regular Nevada build (say 87) 1. Add to profile:- root="/dev/dsk/c0d0s0" 2. Modify extra:- extra = "/platform/i86xpv/kernel/amd64/unix" 3. You don''t need cdrom anymore :- disk = [''phy:/dev/sdaXX ,0,w''] It has been done hundreds of times and it works for sure. Regards -b. ----- Original Message ---- From: Michael Jinks <mjinks@uchicago.edu> To: Xen-users@lists.xensource.com Sent: Monday, May 12, 2008 12:53:16 PM Subject: Re: [Xen-users] Solaris domU dies at boot I''m straightened out, at least partly. (Thanks Boris.) I was trying to go back to NV87 from OS08/05, and I''d switched everything except the ISO file, which was still the OpenSolaris CD. Oops. Putting that back to the Nevada 87 ISO, I''m now booting into the install routine as expected. If history repeats itself I''ll get a kernel panic once the OS is installed and trying to boot into the runtime kernel, but if that happens I''ll start a new thread. Thanks to everybody who pitched in to iron out my brain. Cheers, -- (a different) mrj On Mon, May 12, 2008 at 12:22:44AM -0500, Michael Jinks wrote:> I''m still trying to get my Solaris domU working on a Gentoo dom0. With > Robert''s help I now know the difference between Express and OpenSolaris, > and I''m back to trying this with an Express ISO, Nevada build 87, now > armed with the "-kd" kernel command line option. (This is the newest > build available, right? And should work...?) > > I''m still getting a kernel panic when I try to boot the install ISO. > Current config file is below, and the kernel panic I get when I try to > boot the CD is pasted along with a stack printout, at: > > http://pastebin.org/35375_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users