Virtual Partitions are supported on all HP server models.
Cell -based server complexes support Virtual Partitions.
Currently, Virtual Partitions support only HP-UX.
A and B are correct.
A and C are correct.
B and C are correct.
A, B, and C are correct.
None of the answers is correct.
2:
Virtual Partitions (T1335A) is a selectable software component available on the 11i Enterprise Operating Environment installation media. As such, the software can be installed during an installation of the HP-UX Operating Software. When such a selection is made, in addition to installing the Operating System, the first Virtual Partition will be created once the Operating System is installed.
In its entirety, is the above statement True or False?
3:
Which of the following statements pertain to creating Virtual Partitions? Select all correct answers.
A vPar must contain at least one bound CPU.
A vPar must contain at least one unbound CPU.
Every vPar requires at least 1GB of RAM.
The system console for a server/nPar is used to manage all vPars configured within that server/nPar.
The kernel (/stand/vmunix) is used to locate and load the Virtual Partition Monitor (vpmon) at system boot time.
4:
The partition number assigned by vparcreate / vparmgr is calculated based on existing vPars and any existing nPars, where appropriate. True or False?
5:
The scenario is as follows :
An nPar has eight CPU installed and configured.
We have created two vPars (vPar0 and vPar1) each with four CPU.
vPar0 bound has three bound and one unbound CPU.
vPar1 has two bound and two unbound CPU.
vPar0 is experiencing significant CPU performance bottleneck problems. We are attempting to remedy this situation by utilizing the spare CPU capacity in vPar1. We have read in the system documentation that we can dynamically move a CPU from one vPar to another without a reboot. Choose all the appropriate actions in order to move a bound CPU from vPar1 to vPar0.
Use vparmodify to redefine the total number of CPU in both vPars and then restart vpmon.
Use the kill “STOP <pid> on all processes running on the CPU that is to be reassigned and then use vparmodify to redefine the total number of CPU in both vPars.
Use vparmodify to redefine the total number of CPU in both vPars.
Use the OLA/R command "rad “o <CPU>" to turn the CPU OFF on vPar1 and then use "rad “i <CPU>" on vPar0 to turn the CPU on.
The above can be accomplished by redefining the ioconfig file in /etc and /stand. Once redefined, it can be loaded into the kernel IO tree by using the command "ioinit “f <filename>".
Action B is required. Additionally, if we wanted to re-assign instance numbers because of the additional/new CPU, action E would also be necessary.
Actions C and E need to be performed before the changes can take effect.
This operation cannot be accomplished without a reboot.
