HP-UX Virtual Partitions 6.0 Release Notes

3 HP-UX Virtual Partitions v6.0 features and advantages
The management of virtual partitions is now converged under an overall framework, which you
can access from the VSP.
vPars v6.0 features
Installation
Ignite-UX support for installing HP-UX on vPars
User interface
HP SMH GUI tool HP Integrity Virtual Server Manager for virtual partition configuration and
management
CLI (vPars v6.0) for virtual partition configuration and management
Accessibility
Dedicated virtual console per vPar
EFI access from the vPar console
Virtual iLO Remote Console for each vPar
Users on one virtual partition cannot access files or file systems on other partitions unless the
file systems are NFS-mounted, or access is otherwise given through networking or for
cluster-aware volume groups used within Serviceguard. Further, users configured on one virtual
partition do not automatically have access on any other partition.
Resources
Each virtual partition is assigned its own resources (cores, memory, and shared I/O), so there
are no resource conflicts between virtual partitions.
Processor cores can be added to or removed from a virtual partition without rebooting
(CPU-OL*).
Shared I/O
Storage (whole LUNs, LVM, SLVM, file backing stores, and NPIV HBA)
Networking (virtual switch and virtual NICs)
Configuration
From within a single VSP (the OS instance hosting the vPars), you manage (create, modify,
delete) multiple virtual partitions.
Each virtual partition runs its own instance of HP-UX. Therefore, each virtual partition has a
separate instance of HP-UX running different applications (or the same applications) at the
same time without conflicts.
The patch level of each instance of HP-UX can be different.
Virtual partitions can be individually reconfigured and rebooted (for patches and other changes
that require a reboot) using the VSP GUI and CLI.
Max number of vPars per hard partition is raised from 16 to the available resource limit.
vPars v6.0 features 7