hpvmmodify question...

[bfrice]

i am running hpux 11.23, vmmgr 3.5, and would like to re-provision a 1TB lun that is current assigned to a windows guest host.
i believe we can delete the lun from the current guest using the following command syntax:
hpvmmodify -P myvmm -d disk:scsi::disk:/dev/rdisk/disk5
the question is what has to be done (if anything) at the vm host server to make it available for different hosts, ideally we would like to add smaller sized luns to other windows guests. thanks in advance.

[Kapil Jha]

same thing the way you deleted from one server add it to other server.
If you like to add smaller LUNs on your window server you may create a VG in HOST and assign LVs of specific size.
To add disk
hpvmmodify -P host_add -a disk:scsi::disk:/dev/rdisk/disk5

BR,
Kapil+

[Kapil Jha]

to add LV disk for LVM
use
disk:scsi::lv:/dev/vg_name/rlvol_name

for VxVM use
disk:scsi::lv:/dev/vx/rdsk/dg_name/v_name

BR,
Kapil+

[Eric SAUBIGNAC]

Bonjour,

"what has to be done (if anything) at the vm host server to make it available for different hosts"

--> as previously said, just add it to the new host with :

hpvmmodify -P OtherHost -a disk:scsi::disk:/dev/rdisk/disk5

"ideally we would like to add smaller sized luns to other windows guests"

Several way to achieve this :

- You want to keep the original 1TB lun "as is" ... then create an LVM or VxVM volume with it and cut into several logical volumes. Each logical volumes will be presented to virtual guests with commands from Kapil's post.

- You absolutly wants that each VM backing stores relies on raw lun. If you have a centralized storage array ... just reduce (or ask your storage admin to do it) the size of the 1 TB lun before adding it to the new guest, (check with diskinfo the new size). Then create (or ask your storage admin to do it) new small luns at storage side. You will have to discover and identify (ioscan, insf, ...) these new LUNs before you add them to other guests.

I do think that second method is better in term of performance, isolation between each VM, and portability.

Eric

[Bhadresh]

Integrity VM supports the following virtual disk types:

Virtual Disk Type Backing Storage Device
--------------------- -----------------------------------
Virtual Disk VM Host disk
Virtual LvDisk VM Host LVM or VxVM logical volume
Virtual FileDisk VM Host VxFS file

Configuring different virtual storage devices is well explained in chapter 7 of HP Integrity Virtual Machines Installation, Configuration, and Administration Book.

The book link is given below:
http://docs.hp.com/en/T2767-90105/T2767-90105.pdf

Regards,
Bhadresh

[bfrice]

thanks for the quick replies everyone...
a few other points...
in another post i read where a reboot was required,
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1211908
what can we look for to avoid this?

[Eric SAUBIGNAC]

Well, you are pointing a thread that is speaking about HP-UX as VM Guest OS.

The problem described about HP-UX is that you can add new disk online, only to an existing virtual controller in the VM Guest. In other words to the same bus-device than an existing device like a disk.

I am not an expert with windows, but as far as I know, you can add online disks. What I don't know : does it depends or no to an existing virtual controllers or if a new controller can be online created ?

If you have a test Guest, just try and tell us.

Eric

[Kapil Jha]

the list line of past tell you ur answer
********************
To "plan ahead," one can explicitly create the first two or three storage devices so that virtual controllers are established. For example,

hpvmcreate -P myvm \
-a disk:scsi:0,4,0:lv: \
-a disk:scsi:0,5,0:lv:<2nd path> \
-a disk:scsi:0,6,0:lv:<3rd path>

That will create 3 controllers, allowing for up to 45 total virtual storage devices.
*******************

How many disk you want to add on a server.

BR,
Kapil+