>name = "storage" >uuid = "f4b21d4b-f5c7-46a4-8a62-7765fbdb2cb0" >vcpus = 1 >memory = "1536" > kernel = "/var/xen/boot/opensolaris/kernel" >ramdisk = "/var/xen/boot/opensolaris/ramdisk" >extra = "/platform/i86xpv/kernel/amd64/unix -B >zfs-bootfs=rpool/ROOT/opensolaris"
I believe the mistake is in extra kernel boot command line. Details here for Nevada DomU with ZFS image :- http://bderzhavets.wordpress.com/2008/12/08/install-snv103-pv-domu-with-zfs-image-at-xen-331-opensuse-111-dom0-all-64-bit/ Get the ZFS-ID of the /ROOT/snv_103 zpool. First, find out the pool_guid. # zpool get guid rpool # NAME PROPERTY VALUE SOURCE rpool guid 17306096753167233998 ************ Then run :- ************ bash-3.2# zdb -d -e 17306096753167233998 Dataset mos [META], ID 0, cr_txg 4, 1.74M, 131 objects Dataset 17306096753167233998/swap [ZVOL], ID 37, cr_txg 15, 4.27M, 3 objects Dataset 17306096753167233998/ROOT/snv_103 [ZPL], ID 57, cr_txg 31, 5.99G, 286127 objects name = “SNV103PV” vcpus = 1 memory = “2048″ kernel = “/etc/xen/nevada/unix” ramdisk = “/etc/xen/nevada/boot_archive” extra = “/platform/i86xpv/kernel/amd64/unix – nowin -B bootpath=/xpvd/x...@0:a -B console=xen -B zfs-bootfs=rpool/57″ disk = ['phy:/dev/sdb12,0,w'] vif = [ 'bridge=br1'] on_shutdown = “destroy” on_reboot = “destroy” on_crash = “destroy” --- On Thu, 7/2/09, Josh Carter <[email protected]> wrote: From: Josh Carter <[email protected]> Subject: Re: [xen-discuss] can't boot 2009.06 domU on Xen 3.4.1 / CentOS 5.3 dom0 To: [email protected] Date: Thursday, July 2, 2009, 4:13 PM > Please, post > 1. your installation profile and shell commands to copy & solaris kernel and > microroot off the disk to Dom0. > 2. uname -a > 3. xm info > 4. brctl show Ok, here goes: 1) Install and run profiles attached. Shell commands to copy kernel/boot archive are verbatim from [1]. 2) uname -a (dom 0): Linux bashful.localdomain 2.6.18.8-xen #1 SMP Mon Jun 29 09:21:28 MDT 2009 x86_64 x86_64 x86_64 GNU/Linux 3) xm info attached. 4) brctl show bridge name bridge id STP enabled interfaces eth0 8000.001517348ead no peth0 Note that at the moment I'm turning off iptables in dom0 to get domU networking to work, I haven't yet changed iptables to allow the traffic. Not relevant to the problem, anyway. Also note that I did some more digging on the panic mentioned in my first note, which led me to [2] that has the same stack trace. This problem was related to grub, so I goofed around with updating the grub in my domU disk, but it had no effect. Since I'm providing the kernel and ramdisk, I assume the domU's grub isn't involved much (if at all) during domU boot. Thanks for any help you can provide, Josh [1]: http://blogs.sun.com/levon/entry/opensolaris_2009_06_guest_domain [2]: https://opensolaris.org/jive/message.jspa?messageID=309582 -- This message posted from opensolaris.org -----Inline Attachment Follows----- _______________________________________________ xen-discuss mailing list [email protected]
_______________________________________________ xen-discuss mailing list [email protected]
