分类：
2009-06-26 11:50:50
Here is Sun's announcement on Sun xVM hypervisor, which is based on the OpenSolaris Xen community.
As the hypervisor becomes productized, it is necessary to consider the choice of feature name. As a result, the official name for this implementation has become Sun xVM hypervisor.
Sun is still fully committed to working with, and being an active member of, the Xen opensource community.
Please read the attached FAQ for further information about the reason for the change.
Sun xVM hypervisor
Q: Why are we doing the name change?
As the hypervisor becomes productized, it is necessary to consider the choice of feature name. As a result, the official name for this implementation will become Sun xVM hypervisor. Sun is still fully committed to working with, and being an active member of, the Xen opensource community.
Q: Does the change to Sun xVM hypervisor imply that Sun is no longer committed to Xen?
Sun is fully committed to working with, and being an active member of, the Xen opensource community. The Xen community page on OpenSolaris.org will continue to be maintained and updated with the latest developments.
Q: Can I use the Xen trademark with Solaris?
The product that will provide virtualization capabilities on x86 based Solaris platforms will be called the Sun xVM hypervisor and will not include the Xen trademark.
Q: Why was Sun xVM hypervisor chosen as the product name?
Sun xVM hypervisor was chosen to reflect that the xVM product is Sun virtualization technology that runs on x86 platforms.
Q: Does this mean that you are not porting the x86 virtual machine to SPARC?
The Sun xVM hypervisor product will target and run on x86 platforms. For SPARC, Sun already has the SPARC hypervisor technology (Logical Domains) and Solaris OS Virtualization (Solaris Containers) is already well established for cross platform support of x86 and SPARC architectures.
Q: What other technologies are available?
The Sun xVM hypervisor product will target and run on x86 platforms. For SPARC, Sun already has the SPARC hypervisor technology (Logical Domains) and Solaris OS Virtualization (Solaris Containers) is already well established for cross platform support of x86 and SPARC architectures.
Sun has also announced its intention to provide the Sun xVM Product Group. This product group includes the Sun xVM Server, which in turn contains the Sun xVM hypervisor.
In this first release, there is no support for virtual disk devices in OpenSolaris domU. What follows is a procedure for creating a diskless client domU.
Loopback mount the build 31 Solaris DVD ISO image
# mount -F hsfs `lofiadm -a /full/path/to/the/iso/image` /mnt
Create a Solaris root image that the client (the Solaris domU) will boot from using smosservice(1M) to install the client OS services from the DVD image:
dlserver# /usr/sadm/bin/smosservice add -u root -- \ -x mediapath=/path/to/install/media \ -x platform=i386.i86pc.Solaris_11 \ -x cluster=SUNWCXall
Obtain a static IP address and hostname to use for each OpenSolaris domU you want to start.
Now configure each diskless client on the server with:
dlserver# /usr/sadm/bin/smdiskless add -u root -- \ -i-e -n \ -x os=i386.i86pc.Solaris_11 \ -x root=/export/root/ \ -x swap=/export/swap/ \ -x dump=/export/dump/ \ -x swapsize=512 -x dumpsize=512
where
As a prerequisite, the ON Specific build tools package (SUNWonbld) must be installed on the diskless client server. SPARC and x86 version of the SUNWonbld package are available here.
The Solaris i86xen archives must be bfu'd over the top of the root image(s) and usr image that were created by smosservice(1M).
First create an empty directory for the i86xen kernel bits in each client root filesystem so that bfu knows that these need to be added:
dlserver# mkdir /export/root//platform/kernel/i86xen
At this point, BFU should be used to update the root image for diskless clients using the following syntax (note the -c):
dlserver# /opt/onbld/bin/bfu -c/export/exec/Solaris_11_i386.all
Then carefully use ACR to resolve any BFU conflicts:
dlserver# /opt/onbld/bin/acr /export/root/
Finally, use bootadm(1M) to update the boot archive on the client root image
dlserver# bootadm update-archive -R /export/root/
If you do modify and then rebuild the OpenSolaris on Xen code base, BFU should be used in exactly the same way to update the root images and the usr filesystem (/export/exec/Solaris_11_i386.all). Note, however, because that usr filesystem is shared between the clients, that all client roots are (and must be) updated by BFU at the same time.
Back on the dom0 machine, NFS mount the diskless root(s) so that the dom0 domain builder can access them. You will almost certainly have to fiddle with the default restrictive NFS export permissions on dlserver to enable the dom0 kernel to mount them.
On the dom0 box, add an entry like this to /etc/fstab to automatically mount the Solaris domU root image at boot.
dlserver:/export/root /x/root nfs defaults,rw 0 0
Don't forget the mount point!
dom0# mkdir -p /x/root dom0# mount -a
Create a domain configuration file with entries like the following:
memory = 256 name = "" kernel = "/x/root/ /platform/i86xen/kernel/unix" extra = "/platform/i86xen/kernel/unix -B console=xen" ramdisk = "/x/root/ /platform/i86pc/boot_archive" nics = 1 ip = " " vif = [ 'mac= , bridge=xenbr0' ] nfs_root = "dlserver:/export/root/ " nfs_server = " " restart = 'none'
You can now boot the Solaris domain by typing the following command as root on the dom0 kernel:
dom0# xm create -c
Be patient with the first boot; SMF initialization is not particularly efficient yet on diskless clients, and it may appear to be hung.
Quite a journey, but worth it once you get there!
If you need to manage a Solaris 10 box with a minimal install, and SSH is not available, you can install it off of the 2nd CD. Rather than figure out the path to your CDROM , it was easier in our case to just tar up the needed packages and FTP them to our Solaris box:
root@srv-3 Product # cp -R SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr SUNWsshu /home/srv-1/sshpkg/ root@srv-3 Product # cd /home/srv-1/sshpkg/ root@srv-3 sshpkg # ls SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr SUNWsshu root@srv-3 sshpkg # tar -cf ../ssh.tar * root@srv-3 sshpkg # tar -tf ../ssh.tar SUNWsshcu/ SUNWsshcu/archive/ . . . SUNWsshu/reloc/ SUNWsshu/reloc/usr/ SUNWsshu/reloc/usr/bin/ SUNWsshu/reloc/usr/lib/ SUNWsshu/reloc/usr/lib/ssh/ root@srv-3 sshpkg # |
tar -xf ssh.tar pkgadd -d . svcadm enable ssh svcadm restart ssh |
vi /etc/ssh/sshd_config
....
# Are root logins permitted using sshd.
# Note that sshd uses pam_authenticate(3PAM) so the root (or any other) user
# maybe denied access by a PAM module regardless of this setting.
# Valid options are yes, without-password, no.
PermitRootLogin yes
....
Install sis900 on solaris 10 i386
This page describes the installation of the July 2007 update of OpenSolaris on a domU running under a Linux dom0. It has all been written based on my experiences with Debian GNU/Linux 4.0 as the dom0 so some details might not match your system and others might just be wrong. If you have any corrections or additions, please email me here:
The installer is available as DVD image from Sun's Download Centre . It is distributed as an ISO file, which has been split into six parts and where each part has been zipped.
I downloaded each file, verified them using the supplied md5sums, and then ran the following from bash to unzip and recombine them:
mkdir /usr/lib/xen-solaris/
for foo in `ls 66-0624-nd-iso-[a-f].zip`; do
unzip -p $foo;
done >/usr/lib/xen-solaris/66-0624-nd.iso] Extracting the Kernel and Initial ramdisk
To boot OpenSolaris under you need both a kernel and initial ramdisk available on your dom0. The documentation seems to assume that you are running an OpenSolaris dom0 and so will already have a copy of the kernel and ramdisk available. In our case, with a Linux dom0, we will need to extract the kernel and ramdisk from the ISO image like so:
mkdir /mnt/tmp mount -o loop,ro 66-0624-nd.iso /mnt/tmp cp /mnt/tmp/boot/x86.miniroot /usr/lib/xen-solaris/x86.miniroot-66-0624-nd cp /mnt/tmp/boot/platform/i86xpv/kernel/unix /usr/lib/xen-solaris/unix-66-0624-nd umount /mnt/tmp] Configuring Xen for the Installation
Before you can boot OpenSolaris to begin the installation you will need to create a configuration file defining the virtual disk, virtual DVD drive, kernel, ramdisk, memory size and kernel parameters. Here's an example:
name = 'argolin' memory = '1024' disk = [ 'file:/mnt/tmp/66-0624-nd.iso,6:cdrom,r', 'phy:/dev/xenvg/argolin.disk,0,w' ] vif = [ '' ] on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' kernel = '/usr/lib/xen-solaris/unix-66-0624-nd' ramdisk = '/usr/lib/xen-solaris/x86.miniroot-66-0624-nd' extra = '/platform/i86xpv/kernel/unix - nowin -B install_media=cdrom'
This creates a domU called argolin with 1024MB of RAM, a virtual DVD drive from the image in '/mnt/tmp/66-0624-nd.iso', a virtual disk from the device '/dev/xenvg/argolin.disk', the default virtual network interface and the kernel and ramdisk extracted earlier. This configuration file should be saved in '/etc/xen/' and given a name like 'argolin.conf' but this is up to you.
] SMP-related IO Hang (part 1)My first tries at booting OpenSolaris as a domU resulted in the installer hanging at some point during the main package installation process. After much help from the kind folk of #solaris-xen on irc.oftc.net we found that this was an IO hang which is only seen on SMP systems. A work-around for this bug exists in the kernel but has to be enabled manually using the kernel's built in debugger. The '-kd' kernel parameter, shown below, causes the kernel to open the debugger as soon as possible after boot.
extra = '/platform/i86xpv/kernel/unix -kd - nowin -B install_media=cdrom'] Booting the Installer
Once you have the DVD image, have extracted the kernel and ramdisk, and have created the configuration file you can boot the installer like so:
xm create -c argolin.conf
The last argument to the command is the name of the configuration file created above.
You should then see:
Using config file "/etc/xen/argolin.conf". Started domain argolin SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Found xen v3.0.3-1 but need xen v3.0.4-1-sun WARNING: The kernel may not function correctly Configuring /dev Solaris Interactive Text (Console session) Using install cd in /dev/dsk/c0d6p0 ... ...
The warnings about the Xen version mismatch may be ignored as these apparently only apply to 64bit systems (thanks again #solaris-xen).
] SMP-related IO Hang (part 2)Following a boot with the '-kd' parameter you should see the following:
Using config file "/etc/xen/argolin.conf". Started domain argolin Loading kmdb... Welcome to kmdb Loaded modules: [ unix krtld genunix ] [0]>
You type:
workaround_6557577?W 1
It shows:
workaround_6557577: 0 = 0x1 [0]>
You type:
:c
It shows:
SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Found xen v3.0.3-1 but need xen v3.0.4-1-sun WARNING: The kernel may not function correctly Configuring /dev ... ...] The Installation
Once OpenSolaris has booted the installer will ask you for details of your location and terminal. Make sure you are using a standard 80x25 terminal and select option 6 (PC console). You should then see a shiny, coloured installer. Make sure you say no to the automatic reboot as we need to transfer the kernel and ramdisk to the dom0 after the install.
] SMP-related IO Hang (part 3)You'll be glad to hear that this is the last section dealing with the SMP-related IO hang. To avoid having to use kmdb to enable the workaround during each boot, I added the following line to '/etc/system':
set workaround_6557577 = 1] TCP/UDP Checksum Problem
I also had a problem with the OpenSolaris kernel not generating checksums for TCP and UDP packets. The fix for this is another addition to '/etc/system':
set xnf:xnf_cksum_offload = 0] Finishing up and Rebooting into the Installed System
Unfortunately we need to update the ramdisk after editing '/etc/system' so:
bootadm update-archive -R /a
As mentioned above, we need to make the OpenSolaris kernel and ramdisk available inside the dom0. It is not strictly necessary to transfer the kernel from the domU to the dom0 as it is identical to the installer's kernel but I have shown the scp for both kernel and ramdisk because this may be necessary if the kernel is upgraded at a later point. I chose a full install so that I could use scp to do this but if you have an ftp server handy you should be OK with a more minimal install. At the post-install console I did the following:
/a/usr/bin/scp -S /a/usr/bin/ssh /a/platform/i86xpv/kernel/unix /a/platform/i86pc/boot_archive \
10.0.0.1:/usr/lib/xen-solaris/
I didn't really know how to shut down the system so I did:
umount /a shutdown -y -g0 -i0
Once back at your dom0's prompt you need to edit the domU's configuration file to look something like this:
name = 'argolin' memory = '1024' disk = [ 'phy:/dev/xenvg/argolin.disk,0,w' ] vif = [ '' ] on_shutdown = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' kernel = '/usr/lib/xen-solaris/unix' ramdisk = '/usr/lib/xen-solaris/boot_archive' extra = '/platform/i86xpv/kernel/unix' root = '/dev/dsk/c0d0s0'
Then fire up the domU again and you're away:
xm create -c argolin.conf
Using config file "/etc/xen/argolin.conf". Started domain argolin SunOS Release 5.11 Version xen-nv66-2007-06-24 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Found xen v3.0.3-1 but need xen v3.0.4-1-sun WARNING: The kernel may not function correctly ip: joining multicasts failed (4) on xnf0 - will use link layer broadcasts for multicast Hostname: argolin.xen.tardis.ed.ac.uk ... ... argolin.xen.tardis.ed.ac.uk console login:
One final note: I was unable to login to the system as root via ssh by default. I only mention this because most Linux distributions now allow ssh root login by default.
root@nwtgz # showrev
Hostname: nwtgz
Hostid: 83a0ea91
Release: 5.8
Kernel architecture: sun4u
Application architecture: sparc
Hardware provider: Sun_Microsystems
Domain:
Kernel version: SunOS 5.8 Generic 117350-14 Oct 2004
root@nwtgz # prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 2048 Megabytes
System Peripherals (Software Nodes):
SUNW,Sun-Fire-V240
packages (driver not attached)
SUNW,builtin-drivers (driver not attached)
deblocker (driver not attached)
disk-label (driver not attached)
terminal-emulator (driver not attached)
dropins (driver not attached)
kbd-translator (driver not attached)
obp-tftp (driver not attached)
SUNW,i2c-ram-device (driver not attached)
SUNW,fru-device (driver not attached)
SUNW,asr (driver not attached)
ufs-file-system (driver not attached)
chosen (driver not attached)
openprom (driver not attached)
client-services (driver not attached)
options, instance #0
aliases (driver not attached)
memory (driver not attached)
virtual-memory (driver not attached)
SUNW,UltraSPARC-IIIi (driver not attached)
memory-controller, instance #0
SUNW,UltraSPARC-IIIi (driver not attached)
memory-controller, instance #1
pci, instance #0
network, instance #0
network, instance #1
pci, instance #1
isa, instance #0
flashprom (driver not attached)
rtc (driver not attached)
i2c, instance #0
i2c-bridge (driver not attached)
i2c-bridge (driver not attached)
motherboard-fru-prom (driver not attached)
chassis-fru-prom (driver not attached)
power-supply-fru-prom (driver not attached)
power-supply-fru-prom (driver not attached)
dimm-spd (driver not attached)
dimm-spd (driver not attached)
dimm-spd (driver not attached)
dimm-spd (driver not attached)
rscrtc (driver not attached)
nvram (driver not attached)
idprom (driver not attached)
gpio (driver not attached)
gpio (driver not attached)
gpio (driver not attached)
gpio (driver not attached)
gpio (driver not attached)
gpio (driver not attached)
power, instance #0
serial, instance #0
serial, instance #1
rmc-comm, instance #0
pmu, instance #0
i2c (driver not attached)
gpio, instance #0
usb, instance #0
ide, instance #0
disk (driver not attached)
cdrom (driver not attached)
sd, instance #30
pci, instance #2
scsi, instance #0
disk (driver not attached)
tape (driver not attached)
sd, instance #0
sd, instance #1
sd, instance #2
sd, instance #3
sd, instance #4 (driver not attached)
sd, instance #5 (driver not attached)
sd, instance #6 (driver not attached)
sd, instance #7 (driver not attached)
sd, instance #8 (driver not attached)
sd, instance #9 (driver not attached)
sd, instance #10 (driver not attached)
sd, instance #11 (driver not attached)
sd, instance #12 (driver not attached)
sd, instance #13 (driver not attached)
sd, instance #14 (driver not attached)
scsi, instance #1
disk (driver not attached)
tape (driver not attached)
sd, instance #15 (driver not attached)
sd, instance #16 (driver not attached)
sd, instance #17 (driver not attached)
sd, instance #18 (driver not attached)
sd, instance #19 (driver not attached)
sd, instance #20 (driver not attached)
sd, instance #21 (driver not attached)
sd, instance #22 (driver not attached)
sd, instance #23 (driver not attached)
sd, instance #24 (driver not attached)
sd, instance #25 (driver not attached)
sd, instance #26 (driver not attached)
sd, instance #27 (driver not attached)
sd, instance #28 (driver not attached)
sd, instance #29 (driver not attached)
pci, instance #3
network, instance #2
network, instance #3
pseudo, instance #0
root@nwtgz # mpstat
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
0 1 0 18 8 3 174 0 11 4 0 180 0 1 5 94
1 1 0 17 416 312 212 0 11 2 0 143 0 0 5 95
root@nwtgz # iostat -En
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373307LSUN72G Revision: 0507 Serial No: 3HZ9KV2N00007518
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 7716 Hard Errors: 34 Transport Errors: 0
Vendor: SEAGATE Product: ST373307LSUN72G Revision: 0507 Serial No: 3HZ9KD9600007518
Size: 73.40GB <73400057856 bytes>
Media Error: 32 Device Not Ready: 0 No Device: 0 Recoverable: 7716
Illegal Request: 0 Predictive Failure Analysis: 0
c1t2d0 Soft Errors: 1637 Hard Errors: 26 Transport Errors: 1
Vendor: SEAGATE Product: ST373307LSUN72G Revision: 0507 Serial No: 3HZ9Q91Q00007522
Size: 73.40GB <73400057856 bytes>
Media Error: 24 Device Not Ready: 0 No Device: 1 Recoverable: 1637
Illegal Request: 0 Predictive Failure Analysis: 0
c1t3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373307LSUN72G Revision: 0507 Serial No: 3HZ9Q7KH00007522
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t0d0 Soft Errors: 0 Hard Errors: 2 Transport Errors: 0
Vendor: TEAC Product: DV-28E-C Revision: 1.4B Serial No:
Size: 18446744073.71GB <-1 bytes>
Media Error: 0 Device Not Ready: 2 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
root@nwtgz # swap -s
total: 582016k bytes allocated + 72672k reserved = 654688k used, 5180784k available
root@nwtgz # pkginfo -l SUNWypu
PKGINST: SUNWypu
NAME: NIS Server for Solaris (usr)
CATEGORY: system
ARCH: sparc
VERSION: 11.8.0,REV=2000.01.08.18.12
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: NIS Server for Solaris 2.6 and up
PSTAMP: on28-patch20040727125011
INSTDATE: Dec 28 2004 15:14
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 21 installed pathnames
5 shared pathnames
5 directories
16 executables
299 blocks used (approx)
/export/home/pas52mon> psrinfo -v
Status of virtual processor 1 as of: 02/27/08 11:55:03
on-line since 02/26/08 08:57:06.
The sparcv9 processor operates at 1350 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 3 as of: 02/27/08 11:55:03
on-line since 02/26/08 08:57:05.
The sparcv9 processor operates at 1350 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 17 as of: 02/27/08 11:55:03
on-line since 02/26/08 08:57:06.
The sparcv9 processor operates at 1350 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 19 as of: 02/27/08 11:55:03
on-line since 02/26/08 08:57:06.
The sparcv9 processor operates at 1350 MHz,
and has a sparcv9 floating point processor.
/ue21/as5prog/script> psrinfo -v
Status of processor 0 as of: 02/27/08 11:58:30
Processor has been on-line since 07/13/07 03:38:04.
The sparcv9 processor operates at 450 MHz,
and has a sparcv9 floating point processor.
# psrinfo -v
Status of virtual processor 0 as of: 02/27/08 11:58:08
on-line since 02/13/08 11:28:57.
The sparcv9 processor operates at 1280 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 1 as of: 02/27/08 11:58:08
on-line since 02/13/08 11:28:56.
The sparcv9 processor operates at 1280 MHz,
and has a sparcv9 floating point processor.
/export/home/pas52mon> psrinfo -pv
The UltraSPARC-IV physical processor has 2 virtual processors (1, 17)
The UltraSPARC-IV physical processor has 2 virtual processors (3, 19)
root@nwtgz # route add default 192.168.198.254
add net default: gateway 192.168.198.254
root@nwtgz # netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
192.168.198.0 192.168.198.222 U 1 1493 bge0
224.0.0.0 192.168.198.222 U 1 0 bge0
default 192.168.198.254 UG 1 3
127.0.0.1 127.0.0.1 UH 5 323 lo0
1. 分区简介：（以我的硬盘为例，只做参考）
第一主分区 10G C盘 NTFS格式 安装Windows XP
第二主分区 15G 空闲未分配 准备留给Solaris 10
扩展分区分为三个逻辑盘：
D盘 24G NTFS格式
E盘 26G FAT32格式
F盘 3G FAT32格式
2. 准备过程：
在E盘建一个solaris的文件夹，然后用WinRAR或者虚拟光驱打开sol-10-u2-ga-x86-dvd.iso,将里面boot目录下的 multiboot和x86.miniroot这两个文件提取出来，放在solaris文件夹中，然后把sol-10-u2-ga-x86-dvd.iso镜 像文件也放在solaris文件夹中。（其实这三个文件放在任何地方都可以，但必须是在FAT32分区中）
3. 用grub引导：
用grub或grub for dos引导,在命令提示符下键入以下命令： find /solaris/multiboot 会显示hd(0,5)，这里的hd(0,5)即我的E盘。注意，你的硬盘分区可能和我的不同，因此显示也会不同，请参考grub 的相关资料。 然后再键入以下命令进行引导： kernel hd(0,5)/solaris/multiboot kernel/unix -B install_media=dsk module hd(0,5)/solaris/x86.miniroot boot 如果一切顺利的话，应该就可以进入引导画面。
4. 利用安装过程中出现的shell进行虚拟光驱
正确引导以后，首先会出现6个安装模式选项，选择1或者等待超时（默认是1）。这时屏幕上会出现类似的如下提示：
NOTICE: rtls0 -- link down
ERROR: Unbale to configure network inteface
Exiting to shell
# NOTICE: rtls0 -- link up 100Mbps Full_puplex
这时候安装程序会停止，光标会停止不动。这时敲一下回车，会出现shell提示符 #
这个shell是可以用的，敲几个简单的命令试试。
有了这个shell就好办了，我们可以用它进行虚拟光驱。
首先要知道E盘在Solaris中是怎么表示的：
cd /dev/dsk
然后ls看一下，里面有类似c0d0p0，c0d0p1，c0d0p2，c0d0p3，c0d0p4的设备。这里c0d0p0对应我的硬盘，c0d0p1
至c0d0p4分别对应4个主分区，可是，Solaris没有设备符号用来对应扩展分区中的逻辑分区。我们该如何mount扩展分区中
的E盘、F盘呢？Solaris用了一种很奇怪的设备符号来表示硬盘中的FAT32分区：c0d0p0:x，这儿x的取值为：1,2,3...，
分别表示硬盘中的第1个、第2个、第3个FAT32分区，依此类推。即我的硬盘中的第1个FAT32分区（E盘）可以表示为
c0d0p0:1、第2个FAT32分区（F盘）可以表示为c0d0p0:2。
注意，不要用诸如c0d0p3:x（这儿c0d0p3对应我的扩展分区，x表示扩展分区中的第x个FAT32分区）这种方式来表示扩
展分区中的FAT32分区，当扩展分区的最后一个分区是FAT32、以c0d0p3:x这种设备符号mount它时会出错，使用c0d0p0:x
这种方式表示FAT32分区则没有任何问题。
赶紧把E盘mount上去吧:
mount -F pcfs /dev/dsk/c0d0p0:1 /mnt
然后进入mnt目录下去看看吧，应该可以看到E盘的文件了。这时候就可以用Solaris的DVD镜像做虚拟光驱了。
lofiadm -a /mnt/solaris/sol-10-u2-ga-x86-dvd.iso
mount -F hsfs /dev/lofi/1 /cdrom （必须mount在/cdrom目录中）
再进入cdrom里面去看看吧，应该成功了。这时系统会认为光驱里面有光盘了。
等这一切做完之后，然后键入 exit ，就会退出shell，安装程序会自动继续进行下去。
来自feel2008, , 有修正
硬盘安装Solaris 10
1. 分区简介：（以我的硬盘为例，只做参考）
第一主分区 10G C盘 NTFS格式 安装Windows XP
第二主分区 15G 空闲未分配 准备留给Solaris 10
扩展分区分为三个逻辑盘：
D盘 24G NTFS格式
E盘 26G FAT32格式
F盘 3G FAT32格式
2. 准备过程：
在E盘建一个solaris的文件夹，然后用WinRAR或者虚拟光驱打开sol-10-u2-ga-x86-dvd.iso,将里面boot目录下的 multiboot和x86.miniroot这两个文件提取出来，放在solaris文件夹中，然后把sol-10-u2-ga-x86-dvd.iso镜 像文件也放在solaris文件夹中。（其实这三个文件放在任何地方都可以，但必须是在FAT32分区中）
3. 用grub引导：
用grub或grub for dos引导,在命令提示符下键入以下命令： find /solaris/multiboot 会显示hd(0,5)，这里的hd(0,5)即我的E盘。注意，你的硬盘分区可能和我的不同，因此显示也会不同，请参考grub 的相关资料。 然后再键入以下命令进行引导： kernel hd(0,5)/solaris/multiboot kernel/unix -B install_media=dsk module hd(0,5)/solaris/x86.miniroot boot 如果一切顺利的话，应该就可以进入引导画面。
4. 利用安装过程中出现的shell进行虚拟光驱
正确引导以后，首先会出现6个安装模式选项，选择1或者等待超时（默认是1）。这时屏幕上会出现类似的如下提示：
NOTICE: rtls0 -- link down
ERROR: Unbale to configure network inteface
Exiting to shell
# NOTICE: rtls0 -- link up 100Mbps Full_puplex
这时候安装程序会停止，光标会停止不动。这时敲一下回车，会出现shell提示符 #
这个shell是可以用的，敲几个简单的命令试试。
有了这个shell就好办了，我们可以用它进行虚拟光驱。
首先要知道E盘在Solaris中是怎么表示的：
cd /dev/dsk
然后ls看一下，里面有类似c0d0p0，c0d0p1，c0d0p2，c0d0p3，c0d0p4的设备。这里c0d0p0对应我的硬盘，c0d0p1
至c0d0p4分别对应4个主分区，可是，Solaris没有设备符号用来对应扩展分区中的逻辑分区。我们该如何mount扩展分区中
的E盘、F盘呢？Solaris用了一种很奇怪的设备符号来表示硬盘中的FAT32分区：c0d0p0:x，这儿x的取值为：1,2,3...，
分别表示硬盘中的第1个、第2个、第3个FAT32分区，依此类推。即我的硬盘中的第1个FAT32分区（E盘）可以表示为
c0d0p0:1、第2个FAT32分区（F盘）可以表示为c0d0p0:2。
注意，不要用诸如c0d0p3:x（这儿c0d0p3对应我的扩展分区，x表示扩展分区中的第x个FAT32分区）这种方式来表示扩
展分区中的FAT32分区，当扩展分区的最后一个分区是FAT32、以c0d0p3:x这种设备符号mount它时会出错，使用c0d0p0:x
这种方式表示FAT32分区则没有任何问题。
赶紧把E盘mount上去吧:
mount -F pcfs /dev/dsk/c0d0p0:1 /mnt
然后进入mnt目录下去看看吧，应该可以看到E盘的文件了。这时候就可以用Solaris的DVD镜像做虚拟光驱了。
lofiadm -a /mnt/solaris/sol-10-u2-ga-x86-dvd.iso
mount -F hsfs /dev/lofi/1 /cdrom （必须mount在/cdrom目录中）
再进入cdrom里面去看看吧，应该成功了。这时系统会认为光驱里面有光盘了。
等这一切做完之后，然后键入 exit ，就会退出shell，安装程序会自动继续进行下去。
5. 进入图形化安装界面后，我就不再多说了吧........ ^_^
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0
/pci@1c,600000/scsi@2/sd@3,0
# isainfo -b
64
用psrinfo(1M)就可以查看。由于多内核/多线程技术的广泛采用，要查出物理CPU的数目可以使用-vp参数，例如：
＃ psrinfo -vp The physical processor has 32 virtual processors (0-31) UltraSPARC-T1 (cpuid 0 clock 1000 MHz)
UltraSPARC-T1的CPU共有8内核，每内核4个线程，因此如果单用-v参数看到的CPU数目是32个，而不是1个。
# psrinfo -vp
The UltraSPARC-IIIi physical processor has 1 virtual processor (0)