xen discuss - Dec 2007 - How to create profile for SNV76 DomU initial creating at CentOS 5.1 Dom0 ?

**************************************************************
Try the way it works for Xen 3.1 SNV76 DomU at CentOS 5.0 Dom0
**************************************************************
[root@ServerRHL51 vm]# cat Solaris76.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 - nowin -B
install_media=cdrom"
disk =
[''file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r'',''phy:/dev/sdb8,0,w'']

vif = ['''']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"


[root@ServerRHL51 vm]# xm create -c Solaris76.conf
Using config file "./Solaris76.conf".
Error: Unable to find number for device (0)

********************************************************************
Try the way as shown in examples at CentOS 5.1 (/etc/xen/xmexamle1)
********************************************************************

[root@ServerRHL51 vm]# cat Solaris76.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 - nowin -B
install_media=cdrom"
disk =
[''file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r'',''phy:sdb8,sdb8,w'']
vif = ['''']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"

[root@ServerRHL51 vm]# xm create -c Solaris76.conf
Using config file "./Solaris76.conf".
Started domain Solaris76
SunOS Release 5.11 Version snv_76 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring /dev
NOTICE: xdf@6: failed to read feature-barrier
NOTICE: xdf@sdb8: failed to read feature-barrier
Solaris Interactive Text (Console session)
Using install cd in /dev/dsk/c0d6p0
Using RPC Bootparams for network configuration information.
Attempting to configure interface xnf0...

Starting normal (?) installation   .....

File System and Disk Layout: /               c0d134511472s0 5945 MB
                             swap                        c0d134511472s1  517 MB
                             /export/home          c0d134511472s7 9209 MB


When done:-


[root@ServerRHL51 vm]# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     2976     2 r-----    168.5
Zombie-Solaris76                           2     1024     1 ---s-d    725.8

[root@ServerRHL51 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"



[root@ServerRHL51 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/xdf@8047b70: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)
Loaded modules: [ scsi_vhci xpv_psm ufs specfs ]
kmdb: target stopped at:
kmdb_enter+0xb: movq   %rax,%rdi
 
 
This message posted from opensolaris.org

I had the exact same problems. It seems the root mappings are broken.
 
 
This message posted from opensolaris.org

I''m getting closer, though it doesn''t work yet. You can
override the root path with an entry like:

extra = "/platform/i86xpv/kernel/unix -B bootpath=/xpvd/xdf@hda:a"

But I think I''m giving it the wrong bootpath mapping. I found that info
on this link:

http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#Installing_Solaris_snv_75_in_a_DomU
 
 
This message posted from opensolaris.org

> I''m getting closer, though it doesn''t work yet. You
> can override the root path with an entry like:
> 
> extra = "/platform/i86xpv/kernel/unix -B
> bootpath=/xpvd/xdf@hda:a"
Would try :-
extra = "/platform/i86xpv/kernel/unix -B
bootpath=/xpvd/xdf@0:a"
> 
> But I think I''m giving it the wrong bootpath mapping.
> I found that info on this link:
> 
> http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solar
> is.html#Installing_Solaris_snv_75_in_a_DomU
 
 
This message posted from opensolaris.org

I guess it''s possible to patch xdf_init (-kd boot option) and replace
xdf@sdbX with xdf@0 when "xm create -c sol.conf" runs the first time.
Then do the same procedure at every startup and schedule bug fix for
SNV 8(X). I need Sun''s training urgently :-))
 
 
This message posted from opensolaris.org

Exchanging ''0'' for ''hda'' didn''t
work.
 
 
This message posted from opensolaris.org

Thanks for feed.
 
 
This message posted from opensolaris.org

> [root@ServerRHL51 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
Doesn''t make any sence, would be better:-
>[0] ::bp xdf`xdf_init
:: cont
No idea what to do.
:: cont
>[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/xdf@8047b70: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)
> Loaded modules: [ scsi_vhci xpv_psm ufs specfs ]
> kmdb: target stopped at:
> kmdb_enter+0xb: movq   %rax,%rdi
 
 
This message posted from opensolaris.org

Hi Boris,

Boris Derzhavets wrote:
...
> [root@ServerRHL51 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"
...
> [root@ServerRHL51 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/xdf@8047b70: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

James,

I''ve created SNV76 DomU with config:-

[root@ServerRHL51 vm]# cat Solaris76.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 - nowin -B
install_media=cdrom"
disk
=[''file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r'',''phy:/dev/sdb8,sdb8,w'']
vif = ['''']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"

[root@ServerRHL51 vm]# xm create -c Solaris76.conf
Using config file "./Solaris76.conf".
Started domain Solaris76
SunOS Release 5.11 Version snv_76 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights
reserved.
Use is subject to license terms.
Configuring /dev
NOTICE: xdf@6: failed to read feature-barrier
NOTICE: xdf@sdb8: failed to read feature-barrier
Solaris Interactive Text (Console session)
Using install cd in /dev/dsk/c0d6p0
Using RPC Bootparams for network configuration
information.
Attempting to configure interface xnf0...

........

Starting installation .....

File System and Disk Layout: 

/ c0d134511472s0 5945 MB
swap c0d134511472s1 517 MB
/export/home c0d134511472s7 9209 MB

Output above is generated by system
I''ve picked up c0d134511472s0 right from there.
CentOS 5.1 (RHEL 5.1) has unusual for Solaris DomU
disk notation:-

(a) disk=[''phy:/dev/sdbX,sdbX,w'']

  If I specify second parameter 0 (as usual for
Solaris) installer exits immediately with message:-
Error: Unable to find number for device (0)
  If I specify (a) installer doesn''t exit ,but print
to output:-

NOTICE: xdf@6: failed to read feature-barrier
NOTICE: xdf@sdb8: failed to read feature-barrier

and continues to work generating at partitioning
phase:-

File System and Disk Layout: 

/ c0d134511472s0            5945 MB
swap c0d134511472s1         517 MB
/export/home c0d134511472s7 9209 MB

I do believe that instead of "xdf@sdb8" installer
expects "xdf@0".I also believe that xdf_init and
probably some other xdf modules cannot handle RHEL 5.1
"disk entry" notation at mean time and have to be
patched. Situation may be and more complicated as in
Bug 6634322 :-
 Linux dom0 block backend driver doesn''t 
"report / support" the "feature-barrier" property,
and the Solaris block front driver has a problem when
"feature-barrier" isn''t there...

Using rootdisk="/dev/dsk/c0d0s0 doesn''t help 

Thank you.
Boris
 
 
This message posted from opensolaris.org

When DomU started checked for "feature-barrier" (DomId = 5) :
[root@ServerRHL51 ~]# xenstore-ls /local/domain/0/backend/vbd/5
 6 = ""
 domain = "Solaris78"
 frontend = "/local/domain/5/device/vbd/6"
 dev = "6"
 state = "4"
 params = "/usr/lib/xen-solaris/snv78.iso"
 mode = "r"
 online = "1"
 frontend-id = "5"
 type = "file"
 node = "/dev/loop0"
 physical-device = "7:0"
 hotplug-status = "connected"
 sectors = "7177600"
 info = "4"
 sector-size = "512"
2073 = ""
 domain = "Solaris78"
 frontend = "/local/domain/5/device/vbd/2073"
 dev = "sdb9"
 state = "4"
 params = "/dev/sdb9"
 mode = "w"
 online = "1"
 frontend-id = "5"
 type = "phy"
 physical-device = "8:19"
 hotplug-status = "connected"
 sectors = "32146002"
 info = "0"
 sector-size = "512"

Property not present

[root@ServerRHL51 vm]# vi Solaris78.conf
[root@ServerRHL51 vm]# cat Solaris78.conf
name = "Solaris78"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-78"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-78"
extra = "/platform/i86xpv/kernel/amd64/unix -kd - nowin -B
install_media=cdrom"
disk =
[''file:/usr/lib/xen-solaris/snv78.iso,6:cdrom,r'',''phy:/dev/sdb9,sdb9,w'']
# root="/dev/dsk/c0d0s0"
vif = ['''']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"

[root@ServerRHL51 vm]# xm create -c Solaris78.conf
Using config file "./Solaris78.conf".
Started domain Solaris78
Loading kmdb...

Welcome to kmdb
Loaded modules: [ unix krtld genunix ]
[0]> ::bp xdf`xdf_init
[0]> ::cont
v3.1.0-53.el5 chgset ''unavailable''
SunOS Release 5.11 Version snv_78 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring /dev
Loaded modules: [ scsi_vhci crypto neti ptm xpv_psm ufs mpt zfs uhci hook ip 
logindmux usba specfs random sctp arp ]
kmdb: breakpoint xdf`xdf_init activation failed: unknown symbol name
kmdb: target stopped at:
kmt_defbp_enter_debugger:       pushq  %rbp
[0]> xdf_barrier_flush_disable/W 1
xdf`xdf_barrier_flush_disable:  0               =       0x1
[0]> ::cont

NOTICE: xdf@6: failed to read feature-barrier
NOTICE: xdf@sdb9: failed to read feature-barrier
Solaris Interactive Text (Console session)
Using install cd in /dev/dsk/c0d6p0
Using RPC Bootparams for network configuration information.
Attempting to configure interface xnf0...
Skipped interface xnf0
Reading ZFS config: done.
Setting up Java. Please wait...

. . . . . . . . . . . . . . . . . . . .

The summery below is your current file system and disk layout, based on the
  information you''ve supplied.

  NOTE: If you choose to customize, you should understand file systems, their
  intended purpose on the disk, and how changing them may affect the operation
  of the system.

      File sys/Mnt point Disk/Slice                                       Size
      ==================================================================      /
c0d-25243072s0                              5985    MB
      swap     c0d-25243072s1                     517     MB
      overlap  c0d-25243072s2                     15664   MB
      /export/home   c0d-25243072s7               9154    MB
=================================================================== 
 
This message posted from opensolaris.org

Might old issue (still affecting RHEL 5.1) :-
*********************************************************************************
http://www.opensolaris.org/os/community/xen/docs/linux-dom0/
*********************************************************************************
Solaris domU on RHEL5 / CentOS5
These versions of Linux are based on a very old version of Xen, and need
tweaking to work at all. The simplest fix is to do the following:

cd /usr/lib/python2.4/site-packages/xen/xend/server
vi blkif.pyand make this change:

devid = blkif.blkdev_name_to_number(dev)
-if not devid:
+if devid is None:
    raise VmError(''Unable to find number for device (%s)'' %
(dev))finally:

# /etc/init.d/xend restart

View also:-
https://bugzilla.redhat.com/show_bug.cgi?id=253222
 
 
This message posted from opensolaris.org

Install Solaris 78 DomU on RHEL5.1 / CentOS 5.1

# cd /usr/lib64/python2.4/site-packages/xen/xend/server
# vi blkif.py     and made this change:

devid = blkif.blkdev_name_to_number(dev)
-if not devid:
+if devid is None:
    raise VmError(''Unable to find number for device (%s)'' %
(dev))finally:

# /etc/init.d/xend restart

Create SNV78 DomU with usual profile 
Select DHCP during install.
For first booting up configure runtime profile with "unix -kd"
to patch xnf_attach at boot time.
Modify /etc/system as usual for build < 81
Copy boot_archive to Dom0
Make final changes to profile:-
ramdisk = "/usr/lib/xen-solaris/boot_archive
 
 
This message posted from opensolaris.org

On Sat, Dec 29, 2007 at 10:07:13PM -0800, Boris Derzhavets
wrote:
> disk
=[''file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r'',''phy:/dev/sdb8,sdb8,w'']
Try:

disk
=[''file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r'',''phy:/dev/sdb8,0,w'']