hpvmcreate -P vm-name -a network:adapter-type:[hardware-address]:vswitch:vswitch-name

[Grayh]

hpvmcreate -P vm-name -a network:adapter-type:[hardware-address]:vswitch:vswitch-name

How to find the adapter-type, [hardware-address]

[Torsten.]

Please continue to read and understand the manual (I posted the link already for you), if this is done come back with detailed questions, please.

[Kapil Jha]

why do u bother bout it if HPUX is automatically doing it for you.
Hust leave that and run nirmal command.
Thanks,
Kapil+

[Torsten.]

start here:

http://docs.hp.com/en/T2767-90105/ch08s01.html?btnPrev=%AB%A0prev

[melvyn burnard]

RTFM, or take a training course.
All the VM manuals are here:
http://docs.hp.com/en/vse#HP%20Integrity%20Virtual%20Machines

[Grayh]

disk:scsi::lv:/dev/vg01/rvdisk1

Here I has a sas disk ... So can I put

disk:sas::lv:/dev/vg01/rvdisk1 or is it ok it leave it as it is

[Torsten. · Accepted solution]

It can only be

disk:scsi

or

disk:avio_stor

this is how the device is mapped into the guest. Using the first the guest will see this device as SCSI device, no matter what it really is (sas, fc, ...).

[Torsten.]

Now take some time and read this chapter:

http://docs.hp.com/en/T2767-90105/ch07.html

[Grayh]

# hpvmmodify -P VM03A -a disk:scsi::/dev/rdsk/c0t0d0
hpvmmodify: Invalid backing type '/dev/rdsk/c0t0d0'.
hpvmmodify: Missing required device fields.
hpvmmodify: Incompatible backing type '/dev/rdsk/c0t0d0' for 'disk'.
hpvmmodify: The device_name '' has invalid characters.
hpvmmodify: Invalid value specified with the -a option (disk:scsi::/dev/rdsk/c0t
0d0).

# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
VM03A 1 HPUX Off 2 0 0 4 GB 0
VM03B 2 HPUX Off 2 0 0 3 GB 0

[Grayh]

# hpvmstart -P VM03A
HPVM guest VM03A configuration problems:
Warning 1: There is insufficient free host memory for this guest.
These problems may prevent HPVM guest VM03A from starting.
hpvmstart: Unable to continue.
# hpvmstart -P VM03B
HPVM guest VM03B configuration problems:
Warning 1: There is insufficient free host memory for this guest.
These problems may prevent HPVM guest VM03B from starting.
hpvmstart: Unable to continue.

[Grayh]

Now after changing the memory to 1G each it looks like this...

# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
VM03A 1 HPUX On (EFI) 2 0 0 1 GB 0
VM03B 2 HPUX On (EFI) 2 0 0 1 GB 0

[Torsten.]

You still did NOT read the manual, right?



Why do you resist to read???



Syntax is

disk:scsi::disk:/dev/rdsk/cXtYdZ

[Grayh]

Actyally I am reading and doing this parally....

Issue is I have a timeline to give the system back to them and as I have never worked on VM's... I am rushing through and requesting your help..

And it's like from you guys.. it is On Job Training to me... and learning & updating my self..

I have only 2 days left out to create & install 2VM Guests on each of the two blade servers..

--So I have installed the VM software on both the servers.. And really not sure where to go next..

--After reading the manual somehow created the following..
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
VM03A 1 HPUX On (EFI) 2 0 0 1 GB 0
VM03B 2 HPUX On (EFI) 2 0 0 1 GB 0

And then not sure what to do next.. Then I thought to install OS on VM03A & VM03B I need to have disk space...not really sure if I am correct...

[Torsten.]

Is this still your BL860c?

Where do you want to put the data for the guests? Internal disk or external?

[Grayh]

Yes this is the same bl860c

Data for guests will be on the internal disks as of now...

Later they are trying to get some external enclosures...

[Torsten.]

OK, currently you have 2 VMs without any devices.

To assign disks (I would prefer to use LVM logical volumes here) you need to create a new VG and 2 LVOLs first. Each lvol will be the root disk of a single VM.

Assign the LVOLS:

# hpvmmodify -P VM03A -a disk:scsi::lv:/dev/vg01/rlvol1

# hpvmmodify -P VM03B -a disk:scsi::lv:/dev/vg01/rlvol2

Now each VM has a disk.

Next is LAN.

Create a virtual switch on a physical NIC (here lan0), name it vswitch01:

# hpvmnet -c -S vswitch01 -n 0

power on the vswitch:

# hpvmnet -b -S vswitch01

assign the network:

# hpvmmodify -P VM03A -a network:lan::vswitch:vswitch01

# hpvmmodify -P VM03B -a network:lan::vswitch:vswitch01

start the VMs:

# hpvmstart -P VM03A
# hpvmstart -P VM03B

Connect to the vMP of the first VM:

# hpvmconsole -P VM03A

and proceed to install HP-UX via ignite.


These are basic steps to create basic guests, adjust them to your needs.

[Grayh]

Torsten... thanks for helping me out..

I get an error here..
# hpvmmodify -P VM03A -a disk:scsi::lv:/dev/vg01/rlvol1
hpvmmodify: ERROR (VM03A): '/dev/vg01/rlvol1' backing device does not exist.
hpvmmodify: Unable to create device disk:scsi:0,0,0:lv:/dev/vg01/rlvol1.
hpvmmodify: Unable to dynamically create device disk:scsi:0,0,0:lv:/dev/vg01/rlv
ol1 - Protocol error.
hpvmmodify: Guest needs to be restarted for all changes to take effect.
HPVM guest VM03A configuration problems:
Warning 1 on item /dev/vg01/rlvol1: '/dev/vg01/rlvol1' backing device does n
ot exist.
These problems may prevent HPVM guest VM03A from starting.
hpvmmodify: The modification process is continuing.

[Torsten.]

Well, I can accept that you can't read and *understand* the 260 pages of the manual now (but promise me to do so!), but I CANNOT accept that you CANNOT read the few lines I posted!!!

[Grayh]

Torsten... I will definitely read the book over this week-end..

I thought of creating a new VG but now I have only one disk online as I have Implemented raid on the internal disks..

# pvcreate -f /dev/rdsk/c0t1d0
Couldn't stat physical volume "/dev/rdsk/c0t1d0":
pvcreate: Couldn't open physical volume "/dev/rdsk/c0t1d0":
No such file or directory

[Torsten.]

So you have 2 choices:

Delete the internal (hardware) RAID and start over from beginning (your data will be lost)
or
create new LVOLs in vg00, if you have enough space.

These are the only solutions if you have the 2 internal disks only.

[Grayh]

I have created lvol9 and lvol10 on vg00
# hpvmmodify -P VM03A -a disk:scsi::lv:/dev/vg00/rlvol9
# hpvmmodify -P VM03B -a disk:scsi::lv:/dev/vg00/rlvol10
# hpvmnet -c -S vswth01 -n 0
# hpvmnet -b -S vswth01
# hpvmmodify -P VM03A -a network:lan::vswitch:vswth01
HPVM guest VM03A configuration problems:
Warning 1 on item /dev/vg01/rlvol1: '/dev/vg01/rlvol1' backing device does n
ot exist.
These problems may prevent HPVM guest VM03A from starting.
hpvmmodify: The modification process is continuing.
# hpvmmodify -P VM03A -a disk:scsi::lv:/dev/vg00/rlvol9
hpvmmodify: ERROR (VM03A): Duplicate backing device '/dev/vg00/rlvol9'.
hpvmmodify: ERROR (VM03A): Unable to add device '/dev/vg00/rlvol9'.
hpvmmodify: Unable to create device disk:scsi::lv:/dev/vg00/rlvol9.
hpvmmodify: Unable to modify the guest.
# vxprint
VxVM vxprint ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible

[Grayh]

i am able to start VM03B successfylly... but unable to start VM03A

# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
VM03A 1 HPUX Off 2 2 1 1 GB 0
VM03B 2 HPUX Off 2 1 0 1 GB 0
# cd /dev/vg01
sh: /dev/vg01: not found.
# hpvmmodify -P VM03B -a network:lan::vswitch:vswth01
# hpvmstart -P VM03A
HPVM guest VM03A configuration problems:
Warning 1 on item /dev/vg01/rlvol1: '/dev/vg01/rlvol1' backing device does n
ot exist.
These problems may prevent HPVM guest VM03A from starting.
hpvmstart: Unable to continue.

# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
VM03A 1 HPUX Off 2 2 1 1 GB 0
VM03B 2 HPUX On (EFI) 2 1 1 1 GB 0
#

[Grayh]

hpvmdevmgmt -l all

/rlvol9:CONFIG=gdev,EXIST=YES,DEVTYPE=LV,SHARE=NO:VM03A:HPVM_STATID_190
1_1073741833
/dev/vg00/rlvol10:CONFIG=gdev,EXIST=YES,DEVTYPE=LV,SHARE=NO:VM03B:HPVM_STATID_20
67_1073741834
lan0:CONFIG=gdev,EXIST=YES,DEVTYPE=NIC,SHARE=NO:vswth01:WWID_NULL
vswth01:CONFIG=gdev,EXIST=YES,DEVTYPE=SWITCH,SHARE=YES:VM03A,VM03B:WWID_NULL
HPVM MANAGEMENT_DB EOF


# hpvmstart -P VM03A
HPVM guest VM03A configuration problems:
Warning 1 on item /dev/vg01/rlvol1: '/dev/vg01/rlvol1' backing device does n
ot exist.
These problems may prevent HPVM guest VM03A from starting.
hpvmstart: Unable to continue.

[Torsten.]

You did by accident add a wrong device, now you need to remove it!

# hpvmmodify -P VM03A -d disk:scsi::lv:/dev/vg01/rlvol1

check with

# hpvmstatus -P VM03A

[Emil Velez]

Cookbook to create a VM.. In order to create a switch need to know IF instance number.

netstat -in
hpvmnet -c -S switch1 -n 1
hpvmnet
hpvmnet -b -S switch1
hpvmdevmgmt -S 8000M /home/vmdisk1
hpvmcreate -P vm1 -e 20
hpvmstatus
hpvmmodify -P vm1 -a disk:scsi::file:/home/vmdisk1
hpvmmodify -P vm1 -a network:lan:1,0,aabbccdd0005:vswitch:switch1
hpvmconsole -P vm1