James, I've created SNV76 DomU with config:-
[EMAIL PROTECTED] 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" [EMAIL PROTECTED] 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: [EMAIL PROTECTED]: failed to read feature-barrier NOTICE: [EMAIL PROTECTED]: 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: [EMAIL PROTECTED]: failed to read feature-barrier NOTICE: [EMAIL PROTECTED]: 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 "[EMAIL PROTECTED]" installer expects "[EMAIL PROTECTED]".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 _______________________________________________ xen-discuss mailing list [email protected]
