1.3.1. Date this project was conceived:
		N/A

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:
               Solaris PAC
	1.4.2. The ARC(s) you expect to review your project:
               PSARC
        1.4.3. The Director/VP who is "Sponsoring" this project:
               Scott.Tracy@Sun.COM
        1.4.4. The name of your business unit:
               Solaris SOFTWARE Group

   1.5. Email Aliases:
    	1.5.1. Responsible Manager: Roger.Dong@sun.com
    	1.5.2. Responsible Engineer: Jack.Meng@sun.com
    	1.5.3. Marketing Manager:
	1.5.4. Interest List: npiv-iteam@sun.com

2. Project Summary
   2.1. Project Description:
	Support NPIV device in Solaris xVM
   2.2. Risks and Assumptions:
	This work is for Solaris xVM hosts only, therefore guest domains configured with
	NPIV device may not be able to be migrated to hosts running on other platforms,
	e.g., Linux.

3. Business Summary
   3.1. Problem Area:
	N/A

   3.2. Market/Requester:
	N/A

   3.3. Business Justification:
	N/A

   3.4. Competitive Analysis:
	N/A

   3.5. Opportunity Window/Exposure:
	N/A

   3.6. How will you know when you are done?:
   	They are able to use NPIV within virtual machines in xVM.

4. Technical Description:
    4.1. Details:
	This project introduces two extensions for Solaris xVM utilities to configure NPIV
	devices with paravirtualized guest domains. NPIV is enable in Solaris by PSARC
	2007/501, refer to section 5 for more info.

	The first one is to attach a specified LUN from a virtual FC port to guest domain.
	xVM hypevisor in Solaris is extended to accept a new type of blk device, npiv,
	and to trigger according script to create the virtual port on specified
	physical port, discovery the lun on specified target and finally attach it as
	a normal blk device to guest domain.

	The second one is to attach a specified virtual FC port to guest domain as
	a pseudo device. 'Pseudo' means there will be no corresponding frontend in guest domain
	for that virtual FC port. xVM hypevisor in Solaris is extended to accept a new kind of
	device, pseudo, and to trigger script to work on different pseudo devices. Currently
	the only pseudo device will be NPIV port and the corresponding script will create
	the virtual port on specified physical port and then,
	1)attach existing luns from that virtual port to guest domain
	2)register a script for device sysevents happenning on the virtual port, afterwards newly
	added/deleted luns will be attached/detached from the guest domain.

	Eigher way the npiv device is able to be migrated if the remote the
	destination host has the specified physical FC port and on the same Fabric with the
	physical port on source host.

    4.2. Bug/RFE Number(s):
	6713736 NPIV lun support in XVM	
	6713700 Dynamic blk dev support in kernel

    4.3. In Scope:
	N/A

    4.4. Out of Scope:
	N/A
    
    4.5. Interfaces:
	N/A

    4.6. Doc Impact:
	Man page: virsh(1M), xm(1M)
	System Administration Guide: Virtualization Using the Solaris Operating System	
    
    4.7. Admin/Config Impact:
	Introduces a new format of options in 'virsh' and 'xm'. Refer to
	docs listed in 4.6 for details.

    4.8. HA Impact:
	N/A
    
    4.9. I18N/L10N Impact:
	N/A
    
    4.10. Packaging & Delivery:
	N/A
    
    4.11. Security Impact:
	N/A
    
    4.12. Dependencies:
	N/A
    
5. Reference Documents:
	http://sac.sfbay/PSARC/2007/501/

6. Resources and Schedule:

   6.1. Projected Availability:
	Solaris Nevada B94/B95

   6.2. Cost of Effort:
	N/A	

   6.3. Cost of Capital Resources:
	N/A

   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
		xvm, on
	6.4.3. Type of CPT Review and Approval expected:
		FastTrack
	6.4.4. Project Boundary Conditions:
		N/A
	6.4.5. Is this a necessary project for OEM agreements:
		N/A
	6.4.6. Notes:
		N/A
	6.4.7. Target RTI Date/Release:
		Nevada B94/B95
	6.4.8. Target Code Design Review Date:
		25/06/2008
	6.4.9. Update approval addition:
		N/A
		6.6.1. Rationale:
			N/A