PGNet Dev
2009-Jun-03 04:58 UTC
runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
i''ve installed 2009.06 as DomU on a openSUSE 11.1 x86_64 Dom0. no apparent glitches or errors -- with the pre-reboot, install step. prior to the 1st step reboot, in Dom0, i''ve cp''d the zfs-aware kernel/ramdisk from the just-installed guest, from, Guest: /tmp/root/platform/i86xpv/kernel/amd64/unix to, Dom0: /home/xen/kernel.opensolaris from, Guest: /tmp/root/platform/i86pc/amd64/boot_archive to, Dom0: /home/xen/ramdisk.opensolaris the next-step, run-time xen config i''m attempting to use is, 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/opensolaris,bootpath=/xpvd/xdf@51712:a'' disk = [ ''phy:/dev/vg01/vm_solaris,xvda,w'' ] boot = "cd" vif = [ ''bridge=br05'' ] memory = 1024 on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' @ xm create -c /home/xen/osol.cfg it rerutns, 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. NOTICE: spa_import_rootpool: error 22 Cannot mount root on /xpvd/xdf@51712:a fstype zfs panic[cpu0]/thread=fffffffffbc60560: vfs_mountroot: cannot mount root fffffffffbc93360 genunix:vfs_mountroot+350 () fffffffffbc93390 genunix:main+f0 () fffffffffbc933a0 unix:_locore_start+80 () skipping system dump - no dump device configured rebooting... at naive glance, given the "Cannot mount root ...", it _looks_ like a zfs-support issue ... ? have i misconfigured, or is there a problem at hand ? thanks.
PGNet Dev
2009-Jun-03 06:36 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
searching on,> vfs_mountroot: cannot mount rooti did come across, "[xen-discuss] vfs_mountroot: cannot mount root" http://opensolaris.org/jive/thread.jspa?messageID=315743 following (correctly, i think ... ?) jens-n''s suggestion, i checked for the ID of the ZPOOL inside the zfs pool, export ZP_ID=`pfexec zpool import | grep id: | awk ''{print $2}''` pfexec zdb -d -e $ZP_ID | grep "/ROOT/opensolaris " Dataset 8373487873486394375/ROOT/opensolaris [ZPL], ID 56, cr_txg 26, 2.82G, 117190 objects then replacing in my cfg file, --- extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/ROOT/opensolaris,bootpath=/xpvd/xdf@51712:a'' +++ extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/56,bootpath=/xpvd/xdf@51712:a'' @ ''xm create ..." i still get the same error as above :-/ any further hints? thanks.
Juergen Keil
2009-Jun-03 07:57 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
2009/6/3 PGNet Dev <pgnet.dev+opensolaris@gmail.com>:> searching on, > >> vfs_mountroot: cannot mount root > > i did come across, > > "[xen-discuss] vfs_mountroot: cannot mount root" > http://opensolaris.org/jive/thread.jspa?messageID=315743 > > extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/56,bootpath=/xpvd/xdf@51712:a''rpool/56 looks ok.> @ ''xm create ..." i still get the same error as above :-/ > > any further hints?I''m not yet sure why it doesn''t work with "xvda" on the disk config line, and /xpvd/xdf@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/xdf@0:a - that''s what I''m using.
Boris Derzhavets
2009-Jun-03 08:02 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
> searching on, > > > vfs_mountroot: cannot mount root > > i did come across, > > "[xen-discuss] vfs_mountroot: cannot mount root" > http://opensolaris.org/jive/thread.jspa?messageID=315 > 43 > > following (correctly, i think ... ?) jens-n''s > suggestion, i checked > for the ID of the ZPOOL inside the zfs pool, > > export ZP_ID=`pfexec zpool import | grep id: | awk > ''{print $2}''` > pfexec zdb -d -e $ZP_ID | grep "/ROOT/opensolaris " > Dataset 8373487873486394375/ROOT/opensolaris [ZPL], > , ID 56, cr_txg 26, > 2.82G, 117190 objects > > then replacing in my cfg file, > > --- extra = ''/platform/i86xpv/kernel/amd64/unix -B > fs-bootfs=rpool/ROOT/opensolaris,bootpath=/xpvd/xdf@51 > 712:a'' > +++ extra = ''/platform/i86xpv/kernel/amd64/unix -B > fs-bootfs=rpool/56,bootpath=/xpvd/xdf@51712:a''Just take a look at :- http://www.neuhalfen.name/2008/12/04/Installing_OpenSolaris_2008_11_in_a_Linux_dom0/ It worked for me under Xen 3.3.1 Hypervisor. ******************** Runtime profile :- ******************** name = "sol200811" vcpus = 1 memory = "1024" kernel = "/srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86xpv/kernel/unix" ramdisk = "/srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86pc/boot_archive" extra = "/platform/i86xpv/kernel/unix - nowin -B bootpath=/xpvd/xdf@0:a -B console=xen -B zfs-bootfs=rpool/56" disk = [''phy:sdc,0,w''] vif = [''mac=aa:00:00:00:03:34, vifname=vif.solgr, bridge=brgreen''] on_shutdown = "destroy" on_reboot = "destroy" on_crash = "destroy" -- This message posted from opensolaris.org
Juergen Keil
2009-Jun-03 08:41 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
2009/6/3 PGNet Dev <pgnet.dev+opensolaris@gmail.com>:> i''ve installed 2009.06 as DomU on a openSUSE 11.1 x86_64 Dom0. no > apparent glitches or errors -- with the pre-reboot, install step. > > prior to the 1st step reboot, in Dom0, i''ve cp''d the zfs-aware > kernel/ramdisk from the just-installed guest, >> cat osol.cfg...> disk = [ ''phy:/dev/vg01/vm_solaris,xvda,w'' ]Was the same python disk configuration used during installation, using "xvda" as the frontend device? Or did you perhaps install using the os200906 ISO image as "xvda" and the vm_solaris virtual disk as "xvdb" ?
Juergen Keil
2009-Jun-03 10:11 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
2009/6/3 Juergen Keil <jrgn.keil@googlemail.com>:> I''m not yet sure why it doesn''t work with "xvda" on the disk config line, > and /xpvd/xdf@51712:a as the bootpath, but I can reproduce the same > "NOTICE: spa_import_rootpool: error 22" error when using such a config.Apparently you gets this error when the "phys_path" for the disk in the zpool disk label doesn''t point to the disk''s current physical device path, e.g. because the frontend device was changed in the python disk config. Can be fixed by booting from the livecd media, with the disk at the new frontend location, and doing a "zpool import -f rool". This updates the phys_path in the zpool''s label. The phys_path in the label can be checked using the command "zdb rpool".
John Levon
2009-Jun-03 11:09 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 03, 2009 at 09:57:32AM +0200, Juergen Keil wrote:> Try to replace the "xvda" front-end device on the disk config > line with "0", and the bootpath with /xpvd/xdf@0:a - that''s > what I''m using.0 should not be a valid disk number (and hasn''t been for a long, long time) regards john
Juergen Keil
2009-Jun-03 11:49 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
2009/6/3 John Levon <john.levon@sun.com>:> On Wed, Jun 03, 2009 at 09:57:32AM +0200, Juergen Keil wrote: > >> Try to replace the "xvda" front-end device on the disk config >> line with "0", and the bootpath with /xpvd/xdf@0:a - that''s >> what I''m using. > > 0 should not be a valid disk number (and hasn''t been for a long, long > time)0 is invalid in a HVM domU. But as far as I remember opensolaris PV domU support started with using small integer values as the frontend disk device numbers: http://mail.opensolaris.org/pipermail/xen-discuss/2006-August/000253.html
John Levon
2009-Jun-03 14:25 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 03, 2009 at 01:49:49PM +0200, Juergen Keil wrote:> But as far as I remember opensolaris PV domU support started with > using small integer values as the frontend disk device numbers: > > http://mail.opensolaris.org/pipermail/xen-discuss/2006-August/000253.htmlYes. As I said that hasn''t been the case for a long time now: we use xvd*. john
PGNet Dev
2009-Jun-03 14:28 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
hi juergen, On Wed, Jun 3, 2009 at 12:57 AM, Juergen Keil <jrgn.keil@googlemail.com> wrote:> I''m not yet sure why it doesn''t work with "xvda" on the disk config line, > and /xpvd/xdf@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/xdf@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'' ] 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/xdf@51712:a'' --- disk = [ ''phy:/dev/vg01/vm_solaris,xvda,w'' ] +++ extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/ROOT/56,bootpath=/xpvd/xdf@0:a'' +++ disk = [ ''phy:/dev/vg01/vm_solaris,0,w'' ] 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!
Boris Derzhavets
2009-Jun-03 14:42 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
Could you post "brctl show & ifconfig " Dom0 reports --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Juergen Keil" <jrgn.keil@googlemail.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 10:28 AM hi juergen, On Wed, Jun 3, 2009 at 12:57 AM, Juergen Keil <jrgn.keil@googlemail.com> wrote:> I''m not yet sure why it doesn''t work with "xvda" on the disk config line, > and /xpvd/xdf@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/xdf@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/xdf@51712:a'' --- disk = [ ''phy:/dev/vg01/vm_solaris,xvda,w'' ] +++ extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/ROOT/56,bootpath=/xpvd/xdf@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 xen-discuss@opensolaris.org
PGNet Dev
2009-Jun-03 15:05 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
hi boris, On Wed, Jun 3, 2009 at 7:42 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Could you post "brctl show & ifconfig " Dom0 reports@ Dom0, with, currently, one minor/conveninence change to my vif, vif = [ ''bridge=br05, vifname=vif05.INT''] per request, brctl show bridge name bridge id STP enabled interfaces br05 8000.00504301354e no eth0 vif05.INT ifconfig br05 Link encap:Ethernet HWaddr 00:50:43:01:36:4E inet addr:192.168.1.2 Bcast:172.30.11.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1650348 errors:0 dropped:0 overruns:0 frame:0 TX packets:896185 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2124923329 (2026.4 Mb) TX bytes:69567846 (66.3 Mb) eth0 Link encap:Ethernet HWaddr 00:50:43:01:36:4E UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2287916 errors:0 dropped:7708 overruns:0 frame:0 TX packets:1434761 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2904563266 (2770.0 Mb) TX bytes:280665172 (267.6 Mb) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3656 errors:0 dropped:0 overruns:0 frame:0 TX packets:3656 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:311442 (304.1 Kb) TX bytes:311442 (304.1 Kb) vif05.INT Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:170 errors:0 dropped:3 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:11471 (11.2 Kb) TX bytes:16766 (16.3 Kb)
Boris Derzhavets
2009-Jun-03 15:20 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
Please , remove "boot" from both profiles. Just simulate install and login as jack/jack. Wait a bit and run $ pfexec ifconfig -a What would happen ? You should get IP for VNC connection to run installer. Right ? Then destroy Domain. Boris. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Juergen Keil" <jrgn.keil@googlemail.com>, xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 11:05 AM hi boris, On Wed, Jun 3, 2009 at 7:42 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Could you post "brctl show & ifconfig " Dom0 reports@ Dom0, with, currently, one minor/conveninence change to my vif, vif = [ ''bridge=br05, vifname=vif05.INT''] per request, brctl show bridge name bridge id STP enabled interfaces br05 8000.00504301354e no eth0 vif05.INT ifconfig br05 Link encap:Ethernet HWaddr 00:50:43:01:36:4E inet addr:192.168.1.2 Bcast:172.30.11.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1650348 errors:0 dropped:0 overruns:0 frame:0 TX packets:896185 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2124923329 (2026.4 Mb) TX bytes:69567846 (66.3 Mb) eth0 Link encap:Ethernet HWaddr 00:50:43:01:36:4E UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2287916 errors:0 dropped:7708 overruns:0 frame:0 TX packets:1434761 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2904563266 (2770.0 Mb) TX bytes:280665172 (267.6 Mb) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3656 errors:0 dropped:0 overruns:0 frame:0 TX packets:3656 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:311442 (304.1 Kb) TX bytes:311442 (304.1 Kb) vif05.INT Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:170 errors:0 dropped:3 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:11471 (11.2 Kb) TX bytes:16766 (16.3 Kb)
Boris Derzhavets
2009-Jun-03 15:31 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
One more question. I presume eth0 obtains IP via dhcp and br05 is described as a bridge in /etc/network/interfaces. Can you "nslookup whatever.com" at your Dom0 ? Boris. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Juergen Keil" <jrgn.keil@googlemail.com>, xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 11:05 AM hi boris, On Wed, Jun 3, 2009 at 7:42 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Could you post "brctl show & ifconfig " Dom0 reports@ Dom0, with, currently, one minor/conveninence change to my vif, vif = [ ''bridge=br05, vifname=vif05.INT''] per request, brctl show bridge name bridge id STP enabled interfaces br05 8000.00504301354e no eth0 vif05.INT ifconfig br05 Link encap:Ethernet HWaddr 00:50:43:01:36:4E inet addr:192.168.1.2 Bcast:172.30.11.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1650348 errors:0 dropped:0 overruns:0 frame:0 TX packets:896185 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2124923329 (2026.4 Mb) TX bytes:69567846 (66.3 Mb) eth0 Link encap:Ethernet HWaddr 00:50:43:01:36:4E UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2287916 errors:0 dropped:7708 overruns:0 frame:0 TX packets:1434761 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2904563266 (2770.0 Mb) TX bytes:280665172 (267.6 Mb) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3656 errors:0 dropped:0 overruns:0 frame:0 TX packets:3656 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:311442 (304.1 Kb) TX bytes:311442 (304.1 Kb) vif05.INT Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:170 errors:0 dropped:3 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:11471 (11.2 Kb) TX bytes:16766 (16.3 Kb)
PGNet Dev
2009-Jun-03 15:45 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
hi boris, On Wed, Jun 3, 2009 at 8:20 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Please , remove "boot" from both profiles. > Just simulate install and login as jack/jack.done.> Wait a bit and runpfexec ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 xnf0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 inet 192.168.1.126 netmask ffffff00 broadcast 192.168.1.255 ether 0:16:3e:1:2:0 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 xnf0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2 inet6 fe80::216:3eff:fe01:200/10 ether 0:16:3e:1:2:0 hm. IP=192.168.1.126 & mtu=1500. not what i''d set statically during install. x.x.x.102 was successfully used for both VNC and ssh (ListenAddress in /etc/ssh/sshd_config was set to 192.168.1.102) apparently, my static IP set was NOT persistent ... ? On Wed, Jun 3, 2009 at 8:31 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> One more question. I presume eth0 obtains IP via dhcpno, it''s statically set> br05 is described as a bridge in /etc/network/interfaces.yes, although, in opensuse, it''s in, /etc/sysconfig/network cat ifcfg-brINT NAME=''88E8053'' LLADDR=''00:50:43:00:41:5E'' BRIDGE=''yes'' BRIDGE_PORTS=''eth0'' BOOTPROTO=''static'' STARTMODE=''auto'' BRIDGE_FORWARDDELAY=''0'' BRIDGE_STP=''off'' ETHTOOL_OPTIONS='''' IPADDR=''192.168.1.2/22'' BROADCAST=''192.168.1.255'' NETWORK=''192.168.1.0'' PREFIXLEN=''24'' GATEWAY=''192.168.1.1'' MTU=''1492'' USERCONTROL=''no'' NM_CONTROLLED=''no''> Can you "nslookup whatever.com" at your Dom0 ?nslookup whatever.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: whatever.com Address: 69.64.147.249 host whatever.com whatever.com has address 69.64.147.249 whatever.com mail is handled by 0 oogieoogieboogieaaaxxx.com. dig whatever.com ; <<>> DiG 9.6.0-P1 <<>> whatever.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22808 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;whatever.com. IN A ;; ANSWER SECTION: whatever.com. 492 IN A 69.64.147.249 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Jun 3 08:38:34 2009 ;; MSG SIZE rcvd: 46
Boris Derzhavets
2009-Jun-03 15:59 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
Could you try to load OS 2009.06 PV DomU with "boot" entry removed one more time ? I believe OS 2009.06 DomU by default does DHCP request at startup. If it fails you get a problem. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 11:45 AM hi boris, On Wed, Jun 3, 2009 at 8:20 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Please , remove "boot" from both profiles. > Just simulate install and login as jack/jack.done.> Wait a bit and runpfexec ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 xnf0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 inet 192.168.1.126 netmask ffffff00 broadcast 192.168.1.255 ether 0:16:3e:1:2:0 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 xnf0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2 inet6 fe80::216:3eff:fe01:200/10 ether 0:16:3e:1:2:0 hm. IP=192.168.1.126 & mtu=1500. not what i''d set statically during install. x.x.x.102 was successfully used for both VNC and ssh (ListenAddress in /etc/ssh/sshd_config was set to 192.168.1.102) apparently, my static IP set was NOT persistent ... ? On Wed, Jun 3, 2009 at 8:31 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> One more question. I presume eth0 obtains IP via dhcpno, it''s statically set> br05 is described as a bridge in /etc/network/interfaces.yes, although, in opensuse, it''s in, /etc/sysconfig/network cat ifcfg-brINT NAME=''88E8053'' LLADDR=''00:50:43:00:41:5E'' BRIDGE=''yes'' BRIDGE_PORTS=''eth0'' BOOTPROTO=''static'' STARTMODE=''auto'' BRIDGE_FORWARDDELAY=''0'' BRIDGE_STP=''off'' ETHTOOL_OPTIONS='''' IPADDR=''192.168.1.2/22'' BROADCAST=''192.168.1.255'' NETWORK=''192.168.1.0'' PREFIXLEN=''24'' GATEWAY=''192.168.1.1'' MTU=''1492'' USERCONTROL=''no'' NM_CONTROLLED=''no''> Can you "nslookup whatever.com" at your Dom0 ?nslookup whatever.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: whatever.com Address: 69.64.147.249 host whatever.com whatever.com has address 69.64.147.249 whatever.com mail is handled by 0 oogieoogieboogieaaaxxx.com. dig whatever.com ; <<>> DiG 9.6.0-P1 <<>> whatever.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22808 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;whatever.com. IN A ;; ANSWER SECTION: whatever.com. 492 IN A 69.64.147.249 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Jun 3 08:38:34 2009 ;; MSG SIZE rcvd: 46
PGNet Dev
2009-Jun-03 16:11 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 3, 2009 at 8:59 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Could you try to load OS 2009.06 PV DomU with "boot" entry removed one more > time ? > I believe OS 2009.06 DomU by default does DHCP request at startup. If it > fails you get a problem.with, cat /home/xen/osol.cfg name = ''nas'' kernel = ''/home/xen/kernel.opensolaris'' ramdisk = ''/home/xen/ramdisk.opensolaris'' extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/56,bootpath=/xpvd/xdf@0:a'' disk = [ ''phy:/dev/vg01/vm_solaris,0,w'',] vif = [ ''bridge=br05, vifname=vif05.INT'', ] memory = 1024 on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' @ xm create -c /home/xen/osol.cfg 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 Reading ZFS config: done. Mounting ZFS filesystems: (6/6) Jun 3 16:06:42 opensolaris sshd[466]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:42 opensolaris sshd[466]: fatal: Cannot bind any address. opensolaris console login: Jun 3 16:06:42 opensolaris sshd[477]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:42 opensolaris sshd[477]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[491]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[491]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[501]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[501]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[507]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[507]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[512]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[512]: fatal: Cannot bind any address. Jun 3 16:06:44 opensolaris sshd[526]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:44 opensolaris sshd[526]: fatal: Cannot bind any address. Jun 3 16:06:44 opensolaris sshd[531]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:44 opensolaris sshd[531]: fatal: Cannot bind any address. Jun 3 16:06:45 opensolaris svc.startd[7]: network/ssh:default failed repeatedly: transitioned to maintenance (see ''svcs -xv'' for details) at this point, the Guest is apparently, launched, xm list nas Name ID Mem VCPUs State Time(s) nas 43 1024 1 -b---- 31.8 but, all logins fail :-/ opensolaris console login: pgnet Password: (pwd assigned @ install) Login incorrect opensolaris console login: root Password: (pwd assigned @ install) Login incorrect opensolaris console login: jack Password: jack Login incorrect opensolaris console login:
Boris Derzhavets
2009-Jun-03 16:25 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
Wait.>hm. IP=192.168.1.126 & mtu=1500. not what i''d set statically during >install. x.x.x.102 was successfully used for both VNC and ssh >(ListenAddress in /etc/ssh/sshd_config was set to 192.168.1.102)I guess you have to reinstall DomU with IP obtained via DHCP for VNC installer. Please, go through install not touching /etc/ssh/sshd_config I would try to reproduce install 2009.06 per old manual (2008.11):- http://www.neuhalfen.name/2008/12/04/Installing_OpenSolaris_2008_11_in_a_Linux_dom0/ Quote:- Find out your IP with ifconfig -a and connect with your favorite VNC viewer to display :1 ( xxx.xxx.xxx.xxx:1 ). Start setup and let it partition the disk. Do not close the installer window, because we do not want to reboot before we have kernel and ramdisk downloaded to the dom0. The new installer unmounts the new boot environment before we can ge a hold on it. So we mount it by ourself: $ beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris R - 2.21G static 2008-12-05 06:58 $ pfexec beadm mount opensolaris /a Update the boot archive $ pfexec bootadm update-archive -R /a And now get the kernel and boot_archive for you dom0 from /a/platform/i86xpv/kernel/unix and /a/platform/i86pc/boot_archive. Copy the Kernel to dom0 The kernel (unix) and the boot_archive should be copied into a directory in your dom0 (scp comes in handy). I choose kernel = "/srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86xpv/kernel/unix" ramdisk = "/srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86pc/boot_archive" So from your dom0: $ scp jack@172.20.0.103:/a/platform/i86xpv/kernel/unix /srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86xpv/kernel/unix $ scp jack@172.20.0.103:/a/platform/i86pc/boot_archive /srv/xen/systems/opensolaris200811/be-0811-rc2/platform/i86pc/boot_archive You will need the ZFS-ID of your boot-environment. Your harddisk will be known as c3d0, your boot-slice containing the ZPOOL is on c3d0s0. We need the ID of the /ROOT/opensolaris zpool. First, determine the pool_guid: $ zpool get guid rpool NAME PROPERTY VALUE SOURCE rpool guid 14025158204312238343 - The guid by iself is useless – we need the ID of the ZPOOL inside the pool. $ pfexec zdb -d -e 14025158204312238343 Dataset mos [META], ID 0, cr_txg 4, 512K, 84 objects Dataset 14025158204312238343/ROOT/opensolaris@install [ZPL], ID 84, cr_txg 276, 2.21G, 101427 objects Dataset 14025158204312238343/ROOT/opensolaris [ZPL], ID 50, cr_txg 72, 2.21G, 101427 objects Dataset 14025158204312238343/ROOT [ZPL], ID 44, cr_txg 69, 18.0K, 4 objects Dataset 14025158204312238343/dump [ZVOL], ID 36, cr_txg 13, 512M, 3 objects Dataset 14025158204312238343/export/home/jens [ZPL], ID 68, cr_txg 80, 20.5K, 6 objects Dataset 14025158204312238343/export/home [ZPL], ID 62, cr_txg 78, 19.0K, 5 objects Dataset 14025158204312238343/export [ZPL], ID 56, cr_txg 76, 19.0K, 5 objects Dataset 14025158204312238343/swap [ZVOL], ID 30, cr_txg 8, 16K, 3 objects Dataset 14025158204312238343 [ZPL], ID 16, cr_txg 1, 72.0K, 12 objects Your output might look different. Look out for /ROOT/opensolaris (here: 50). Remember it! Disable gdm (unless you want a graphical login) $ svcadm disable svc:/application/graphical-login/gdm:default And reboot from within the installer window. Quote ends. Personally, i did straight forward install due to Xen 3.4 Hypervisor. It already has pygrub ZFS support. Boris. --- On Wed, 6/3/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "PGNet Dev" <pgnet.dev+opensolaris@gmail.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 11:59 AM Could you try to load OS 2009.06 PV DomU with "boot" entry removed one more time ? I believe OS 2009.06 DomU by default does DHCP request at startup. If it fails you get a problem. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 11:45 AM hi boris, On Wed, Jun 3, 2009 at 8:20 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Please , remove "boot" from both profiles. > Just simulate install and login as jack/jack.done.> Wait a bit and runpfexec ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 xnf0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 inet 192.168.1.126 netmask ffffff00 broadcast 192.168.1.255 ether 0:16:3e:1:2:0 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 xnf0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2 inet6 fe80::216:3eff:fe01:200/10 ether 0:16:3e:1:2:0 hm. IP=192.168.1.126 & mtu=1500. not what i''d set statically during install. x.x.x.102 was successfully used for both VNC and ssh (ListenAddress in /etc/ssh/sshd_config was set to 192.168.1.102) apparently, my static IP set was NOT persistent ... ? On Wed, Jun 3, 2009 at 8:31 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> One more question. I presume eth0 obtains IP via dhcpno, it''s statically set> br05 is described as a bridge in /etc/network/interfaces.yes, although, in opensuse, it''s in, /etc/sysconfig/network cat ifcfg-brINT NAME=''88E8053'' LLADDR=''00:50:43:00:41:5E'' BRIDGE=''yes'' BRIDGE_PORTS=''eth0'' BOOTPROTO=''static'' STARTMODE=''auto'' BRIDGE_FORWARDDELAY=''0'' BRIDGE_STP=''off'' ETHTOOL_OPTIONS='''' IPADDR=''192.168.1.2/22'' BROADCAST=''192.168.1.255'' NETWORK=''192.168.1.0'' PREFIXLEN=''24'' GATEWAY=''192.168.1.1'' MTU=''1492'' USERCONTROL=''no'' NM_CONTROLLED=''no''> Can you "nslookup whatever.com" at your Dom0 ?nslookup whatever.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: whatever.com Address: 69.64.147.249 host whatever.com whatever.com has address 69.64.147.249 whatever.com mail is handled by 0 oogieoogieboogieaaaxxx.com. dig whatever.com ; <<>> DiG 9.6.0-P1 <<>> whatever.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22808 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;whatever.com. IN A ;; ANSWER SECTION: whatever.com. 492 IN A 69.64.147.249 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Jun 3 08:38:34 2009 ;; MSG SIZE rcvd: 46
Boris Derzhavets
2009-Jun-03 16:27 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
I''ve already responded regarding this issue. Boris. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 12:11 PM On Wed, Jun 3, 2009 at 8:59 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> Could you try to load OS 2009.06 PV DomU with "boot" entry removed one more > time ? > I believe OS 2009.06 DomU by default does DHCP request at startup. If it > fails you get a problem.with, cat /home/xen/osol.cfg name = ''nas'' kernel = ''/home/xen/kernel.opensolaris'' ramdisk = ''/home/xen/ramdisk.opensolaris'' extra = ''/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/56,bootpath=/xpvd/xdf@0:a'' disk = [ ''phy:/dev/vg01/vm_solaris,0,w'',] vif = [ ''bridge=br05, vifname=vif05.INT'', ] memory = 1024 on_shutdown = ''destroy'' on_reboot = ''destroy'' on_crash = ''destroy'' @ xm create -c /home/xen/osol.cfg 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 Reading ZFS config: done. Mounting ZFS filesystems: (6/6) Jun 3 16:06:42 opensolaris sshd[466]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:42 opensolaris sshd[466]: fatal: Cannot bind any address. opensolaris console login: Jun 3 16:06:42 opensolaris sshd[477]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:42 opensolaris sshd[477]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[491]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[491]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[501]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[501]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[507]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[507]: fatal: Cannot bind any address. Jun 3 16:06:43 opensolaris sshd[512]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:43 opensolaris sshd[512]: fatal: Cannot bind any address. Jun 3 16:06:44 opensolaris sshd[526]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:44 opensolaris sshd[526]: fatal: Cannot bind any address. Jun 3 16:06:44 opensolaris sshd[531]: error: Bind to port 22 on 192.168.1.102 failed: Cannot assign requested address. Jun 3 16:06:44 opensolaris sshd[531]: fatal: Cannot bind any address. Jun 3 16:06:45 opensolaris svc.startd[7]: network/ssh:default failed repeatedly: transitioned to maintenance (see ''svcs -xv'' for details) at this point, the Guest is apparently, launched, xm list nas Name ID Mem VCPUs State Time(s) nas 43 1024 1 -b---- 31.8 but, all logins fail :-/ opensolaris console login: pgnet Password: (pwd assigned @ install) Login incorrect opensolaris console login: root Password: (pwd assigned @ install) Login incorrect opensolaris console login: jack Password: jack Login incorrect opensolaris console login:
PGNet Dev
2009-Jun-03 16:48 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 3, 2009 at 9:25 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> I guess you have to reinstall DomU with IP obtained via DHCP for VNC > installer. Please, go through install not touching /etc/ssh/sshd_config > I would try to reproduce install 2009.06 per old manual (2008.11):-unfortunately, DHCP will not be an option in our target/production env. so getting this working with static_IP, as it done for every other Guest env we deploy, is a key requirement ... it looks like jumpstart/caiman may provide an option to pass static_IP assignements via xen cfg ... but it''s not clear if that''s even functionally available as yet, or if it works for the installer. so, is the message for now -- opensolaris can''t be installed as a DomU guest in a static_IP-only environment ?> http://www.neuhalfen.name/2008/12/04/Installing_OpenSolaris_2008_11_in_a_Linux_dom0/ > > Quote:-(snip) sure. that''s the procedure i followed to get the zpool ID, as above.> Personally, i did straight forward install due to Xen 3.4 Hypervisor. > It already has pygrub ZFS support.i''m interested in deploying on a Dom0 production system. atm, opensuse 11.1 has Xen 3.3.1.
Boris Derzhavets
2009-Jun-03 17:16 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
I would try install via DHCP. Then shutdown xenf0 and bring it up with static IP desired. Then check would DomU keep staying on subnet or no. They should have a kind of Network Manager. Network Magic or something like that. It should be possible to disable this NM. It''s not a problem for Solaris Nevada. Installer itself suggested static IP configuration. The last build i tried was 106. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 12:48 PM On Wed, Jun 3, 2009 at 9:25 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:> I guess you have to reinstall DomU with IP obtained via DHCP for VNC > installer. Please, go through install not touching /etc/ssh/sshd_config > I would try to reproduce install 2009.06 per old manual (2008.11):-unfortunately, DHCP will not be an option in our target/production env. so getting this working with static_IP, as it done for every other Guest env we deploy, is a key requirement ... it looks like jumpstart/caiman may provide an option to pass static_IP assignements via xen cfg ... but it''s not clear if that''s even functionally available as yet, or if it works for the installer. so, is the message for now -- opensolaris can''t be installed as a DomU guest in a static_IP-only environment ?> http://www.neuhalfen.name/2008/12/04/Installing_OpenSolaris_2008_11_in_a_Linux_dom0/ > > Quote:-(snip) sure. that''s the procedure i followed to get the zpool ID, as above.> Personally, i did straight forward install due to Xen 3.4 Hypervisor. > It already has pygrub ZFS support.i''m interested in deploying on a Dom0 production system. atm, opensuse 11.1 has Xen 3.3.1.
John Levon
2009-Jun-03 17:21 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 03, 2009 at 09:48:01AM -0700, PGNet Dev wrote:> so, is the message for now -- opensolaris can''t be installed as a DomU > guest in a static_IP-only environment ?I''m confused where you got that message. The message is simply that you have to use the work-around you already are. It''s unpleasant but it does work... regards john
John Levon
2009-Jun-03 17:22 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 03, 2009 at 09:48:01AM -0700, PGNet Dev wrote:> unfortunately, DHCP will not be an option in our target/production > env. so getting this working with static_IP, as it done for everyBTW, if static config is very important for you, you should file an RFE on defect.opensolaris.org asking for installer and post-install static config support in OpenSolaris john
PGNet Dev
2009-Jun-03 17:30 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 3, 2009 at 10:21 AM, John Levon <john.levon@sun.com> wrote:> On Wed, Jun 03, 2009 at 09:48:01AM -0700, PGNet Dev wrote: > I''m confused where you got that message.in part, "I believe OS 2009.06 DomU by default does DHCP request at startup. If it fails you get a problem."> The message is simply that you > have to use the work-around you already are. It''s unpleasant but it does > work...as detailed in my prior posts, it''s not (yet) working here ... admitting i''m ''new'' to this, this install is cumbersome, at best. tbh, a far cry from the "it works" messages from speakers & product_mgmt received at JavaOne "-/> BTW, if static config is very important for you, you should file an RFE > on defect.opensolaris.org asking for installer and post-install static > config support in OpenSolarisi suppose i''ll have to do that, but frankly a bit surprised that that would not have been considered already -- static-ip deployments, of servers in particular, are not particularly uncommon ...> I would try install via DHCP.likely doable ... but, again, DHCP is not going to be an option here at all (eventually) ...> They should have a kind of Network Manager. Network Magic or something > like that. It should be possible to disable this NM.iiuc, i believe that''d be, pfexec svcadm disable network/physical:nwam && \ pfexec svcadm enable network/physical:default pfexec ifconfig xnf0 down pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492 pfexec ifconfig xnf0 up pfexec route add default 192.168.1.102 which i can/do @ installer time to use static IP assignements. i just can''t seem to get them to ''stick'' or ''be happy'' after reboot and xen, run-time launch.> It''s not a problem for Solaris Nevada. Installer it self suggested static IP configuration. The last build i tried was 106.@ JavaOne i was repeatedly told that SXCE (that''s ''Nevada'', yes?) is "going away soon" and that I should be using opensolaris _now_. given these experiences, i''m not sure that''s the wisest choice, particularly for a server deployment in a static-ip env. given your coment, Boris, and reading, http://whacked.net/2005/06/21/confused-so-was-i/ is ''Nevada'' likely a more-functional, or at least better-behaved, option for me?
PGNet Dev
2009-Jun-03 17:43 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 3, 2009 at 10:43 AM, John Levon <john.levon@sun.com> wrote:> I''m sure it''s been considered. It''s a matter of priorities. For the > initial focus of OpenSolaris, DHCP is likely.understood. then, perhaps, its "initial focus" doesn''t work for me. given the comments @ JavaOne, including the "sure it installs headless just fine", i''m a bit irritated with the marketing ... nonetheless, SXCE bears investigation -- if i can _find_ the silly DL page ! :-}> That''s strange, I believe the above should work OK post-install as well.that''s what i thought ...> Any networking failures shouldn''t affect your ability to login, anyway. > That''s very peculiar.agreed.
John Levon
2009-Jun-03 17:43 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
On Wed, Jun 03, 2009 at 10:30:20AM -0700, PGNet Dev wrote:> i suppose i''ll have to do that, but frankly a bit surprised that that > would not have been considered already -- static-ip deployments, ofI''m sure it''s been considered. It''s a matter of priorities. For the initial focus of OpenSolaris, DHCP is likely.> > They should have a kind of Network Manager. Network Magic or something > > like that. It should be possible to disable this NM. > > iiuc, i believe that''d be, > > pfexec svcadm disable network/physical:nwam && \ > pfexec svcadm enable network/physical:default > pfexec ifconfig xnf0 down > pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492 > pfexec ifconfig xnf0 up > pfexec route add default 192.168.1.102 > > which i can/do @ installer time to use static IP assignements. i just > can''t seem to get them to ''stick'' or ''be happy'' after reboot and xen, > run-time launch.That''s strange, I believe the above should work OK post-install as well. Any networking failures shouldn''t affect your ability to login, anyway. That''s very peculiar. regards john
Boris Derzhavets
2009-Jun-03 18:34 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
>is ''Nevada'' likely a more-functional, or at least better-behaved, > option for me?OpenSolaris has a package management system kind of Ubuntu & Debian have . It has an analog of Synaptic Manager (ubuntu). As far as i know Nevada doesn''t have such features in meantime. However, i was always under impression that Solaris 11 is supposed to be developed via Nevada Builds. All the efforts to build Xen 3.3.2 (3.4) Dom0 on Solaris Nevada clearly demonstrate mentioned intend. If i am wrong about that, please, correct me. Boris. --- On Wed, 6/3/09, PGNet Dev <pgnet.dev+opensolaris@gmail.com> wrote: From: PGNet Dev <pgnet.dev+opensolaris@gmail.com> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "John Levon" <john.levon@sun.com> Cc: "Boris Derzhavets" <bderzhavets@yahoo.com>, xen-discuss@opensolaris.org Date: Wednesday, June 3, 2009, 1:30 PM On Wed, Jun 3, 2009 at 10:21 AM, John Levon <john.levon@sun.com> wrote:> On Wed, Jun 03, 2009 at 09:48:01AM -0700, PGNet Dev wrote: > I''m confused where you got that message.in part, "I believe OS 2009.06 DomU by default does DHCP request at startup. If it fails you get a problem."> The message is simply that you > have to use the work-around you already are. It''s unpleasant but it does > work...as detailed in my prior posts, it''s not (yet) working here ... admitting i''m ''new'' to this, this install is cumbersome, at best. tbh, a far cry from the "it works" messages from speakers & product_mgmt received at JavaOne "-/> BTW, if static config is very important for you, you should file an RFE > on defect.opensolaris.org asking for installer and post-install static > config support in OpenSolarisi suppose i''ll have to do that, but frankly a bit surprised that that would not have been considered already -- static-ip deployments, of servers in particular, are not particularly uncommon ...> I would try install via DHCP.likely doable ... but, again, DHCP is not going to be an option here at all (eventually) ...> They should have a kind of Network Manager. Network Magic or something > like that. It should be possible to disable this NM.iiuc, i believe that''d be, pfexec svcadm disable network/physical:nwam && \ pfexec svcadm enable network/physical:default pfexec ifconfig xnf0 down pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492 pfexec ifconfig xnf0 up pfexec route add default 192.168.1.102 which i can/do @ installer time to use static IP assignements. i just can''t seem to get them to ''stick'' or ''be happy'' after reboot and xen, run-time launch.> It''s not a problem for Solaris Nevada. Installer it self suggested static IP configuration. The last build i tried was 106.@ JavaOne i was repeatedly told that SXCE (that''s ''Nevada'', yes?) is "going away soon" and that I should be using opensolaris _now_. given these experiences, i''m not sure that''s the wisest choice, particularly for a server deployment in a static-ip env. given your coment, Boris, and reading, http://whacked.net/2005/06/21/confused-so-was-i/ is ''Nevada'' likely a more-functional, or at least better-behaved, option for me?
PGNet Dev
2009-Jun-03 18:53 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
boris, On Wed, Jun 3, 2009 at 11:34 AM, Boris Derzhavets <bderzhavets@yahoo.com> wrote:>>is ''Nevada'' likely a more-functional, or at least better-behaved, >> option for me? > > OpenSolaris has a package management system kind of Ubuntu & Debian > have . It has an analog of Synaptic Manager (ubuntu). > As far as i know Nevada doesn''t have such features in meantime.as long as it has _some_ form of reliable cmd-line pkg mgmt, and access to reasonably up-to-date repos (and, i assume it has both), personally i don''t care ...> However, i was always under impression that Solaris 11 is supposed to be > developed via Nevada Builds. All the efforts to build Xen 3.3.2 (3.4) Dom0 > on > Solaris Nevada clearly demonstrate mentioned intend. > If i am wrong about that, please, correct me.well, i''m certainly no authority ... but, again, @ javaone i was told that *opensolaris*, not SXCE, is the basis for "Solaris future" (whatever that _actually_ means ...) @ specific questions re: availability of xen 3.3/3.4, i was told "February-ish" -- in the context of opensolaris. this which-version-does-what-for-whom business is confusing. atm, i''m DL''ing nevada b115. we''ll see how that works ...
Juergen Keil
2009-Jun-03 19:30 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
2009/6/3 PGNet Dev <pgnet.dev+opensolaris@gmail.com>:> iiuc, i believe that''d be, > > pfexec svcadm disable network/physical:nwam && \ > pfexec svcadm enable network/physical:default > pfexec ifconfig xnf0 down > pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492 > pfexec ifconfig xnf0 up > pfexec route add default 192.168.1.102 > > which i can/do @ installer time to use static IP assignements. i just > can''t seem to get them to ''stick'' or ''be happy'' after reboot and xen, > run-time launch.Use the same commands with the installed system. To make the settings permanent you also need: echo 192.168.1.102 netmask 255.255.255.0 mtu 1492 > /etc/hostname.xnf0 rm /etc/dhcp.xnf0 echo 192.168.1.102 > /etc/defaultrouter
Boris Derzhavets
2009-Jul-26 10:25 UTC
Re: runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0
> > pfexec svcadm disable network/physical:nwam && \ > > pfexec svcadm enable network/physical:defaultAll ifconfig commands hang after enabling network/physical:default several minutes later in my enviromment.> > pfexec ifconfig xnf0 down > > pfexec ifconfig xnf0 192.168.1.102 netmask > 255.255.255.0 mtu 1492 > > pfexec ifconfig xnf0 up > > pfexec route add default 192.168.1.102 > > > > which i can/do @ installer time to use static IP > assignements. i just > > can''t seem to get them to ''stick'' or ''be happy'' > after reboot and xen, > > run-time launch.-- This message posted from opensolaris.org