Could you post "brctl show & ifconfig " Dom0 reports --- On Wed, 6/3/09, PGNet Dev <[email protected]> wrote:
From: PGNet Dev <[email protected]> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Juergen Keil" <[email protected]> Cc: [email protected] Date: Wednesday, June 3, 2009, 10:28 AM hi juergen, On Wed, Jun 3, 2009 at 12:57 AM, Juergen Keil <[email protected]> wrote: > I'm not yet sure why it doesn't work with "xvda" on the disk config line, > and /xpvd/x...@51712:a as the bootpath, but I can reproduce the same > "NOTICE: spa_import_rootpool: error 22" error when using such a config. > > Try to replace the "xvda" front-end device on the disk config > line with "0", and the bootpath with /xpvd/x...@0:a - that's > what I'm using. as you suspected, my init config was, cat osol_i.cfg name = 'nas' bootloader = '/usr/bin/pygrub' kernel = '/platform/i86xpv/kernel/amd64/unix' ramdisk = '/boot/amd64/x86.microroot' extra = '/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom' disk = [ 'phy:/dev/loop0,6:cdrom,r', 'phy:/dev/vg01/vm_solaris,0,w' ] ************************************* What is that is PV DomU profile ? ************************************* boot = "dc" vif = [ 'bridge=br05' ] memory = 1024 on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' changing, per suggestion, cat osol.cfg name = 'nas' kernel = '/home/xen/kernel.opensolaris' ramdisk = '/home/xen/ramdisk.opensolaris' --- extra = '/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/ROOT/56,bootpath=/xpvd/x...@51712:a' --- disk = [ 'phy:/dev/vg01/vm_solaris,xvda,w' ] +++ extra = '/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/ROOT/56,bootpath=/xpvd/x...@0:a' +++ disk = [ 'phy:/dev/vg01/vm_solaris,0,w' ] ************************************* What is that is PV DomU profile ? ************************************* boot = "cd" vif = [ 'bridge=br05' ] memory = 1024 on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' then @, xm create -c /home/xen/osol.cfg it now returns, Using config file "/home/xen/osol.cfg". Started domain nas v3.3.1_18494_03-1.8 chgset '18494' SunOS Release 5.11 Version snv_111b 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Configuring devices. Loading smf(5) service descriptions: 150/150 svccfg import warnings. See /var/svc/log/system-manifest-import:default.log . Reading ZFS config: done. Mounting ZFS filesystems: (6/6) opensolaris console login: Jun 3 14:14:20 opensolaris sshd[891]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 14:14:20 opensolaris sshd[891]: fatal: Cannot bind any address. Jun 3 14:14:21 opensolaris sshd[904]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. ... Jun 3 14:14:24 opensolaris sshd[952]: fatal: Cannot bind any address. Jun 3 14:14:24 opensolaris sshd[958]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 14:14:24 opensolaris sshd[958]: fatal: Cannot bind any address. Jun 3 14:14:25 opensolaris svc.startd[7]: network/ssh:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details) which looks like the original mount problem is (?) remedied, & that i've a 'next' issue ... in light of the add'l discussion in this thread, what's the final verdict in terms of what disk id, etc _should_, correctly, be used? thanks! _______________________________________________ xen-discuss mailing list [email protected]
_______________________________________________ xen-discuss mailing list [email protected]
