topic Re: Ignite on VM in Operating System - HP-UX

Ignite on VM

Grayh — Fri, 03 Oct 2008 14:51:11 GMT

As I have closed my previous thread and didn't want to reopen it.. Starting this new one..

Now as I am able to install the OS from the media.. I am on safe side.. So the installations are going on..

But still I am wondering why i am unable to ignite my VM guest.I know somewhere I have ommited something or missing something... but what is it is the challange

let us try it out again

On the server side
------------------------
entries in /etc/bootptab on the server side

ignite-defaults:\
ht=ethernet:\
hn:\
gw=10.3.90.1:\
sm=255.255.255.0:\
vm=rfc1048:\
hn=vm03A:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48

vm04A:tc=ignite-defaults:ip=10.3.90.121:ha=02158078CD62

Also the fttpd and tftpd have been uncommented

On the client side
-------------------
Shell> lanaddress

LAN Address Information

LAN Address Path
----------------- ----------------------------------------
Mac(02158078CD62) Acpi(PNP0A03,0)/Pci(1|0)/Mac(02158078CD62))
Primary LAN not found

Shell> lanboot select
01 Acpi(PNP0A03,0)/Pci(1|0)/Mac(02158078CD62)
Select Desired LAN: 01
Selected Acpi(PNP0A03,0)/Pci(1|0)/Mac(02158078CD62)

Running LoadFile()

CLIENT MAC ADDR: 02 15 80 78 CD 62

PXE-E16: Valid PXE offer not received.
Exit status code: Invalid Parameter

dbprofile method:-
---------------------

Shell> lanboot select -dn igniteprof
01 Acpi(PNP0A03,0)/Pci(1|0)/Mac(02158078CD62)
Select Desired LAN: 01
Selected Acpi(PNP0A03,0)/Pci(1|0)/Mac(02158078CD62)

Running LoadFile()

CLIENT MAC ADDR: 02 15 80 78 CD 62

PXE-E16: Valid PXE offer not received.
Exit status code: Invalid Parameter

Shell> dbprofile
Profile List

Profile Name: igniteprof
Network Type: IPv4
Server IP address: 10.3.90.14
Client IP address: 10.3.90.121
Gateway IP address: 10.3.90.1
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

# lanscan -------> At the client
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/2/2/0 0x001F29BC3AEA 2 UP lan2 snap2 1 ETHER Yes 119
0/1/1/0 0x001F29BC3AEC 0 UP lan0 snap0 2 ETHER Yes 119
0/1/1/1 0x001F29BC3AED 1 UP lan1 snap1 3 ETHER Yes 119
0/2/2/1 0x001F29BC3AEB 3 UP lan3 snap3 4 ETHER Yes 119

I don't know .... http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcpdump-3.9.8/

dosen't seem to be working

Messages in the syslog

Oct 2 16:07:04 MAHP02 inetd[1077]: Rereading configuration
Oct 2 16:07:04 MAHP02 inetd[1077]: Configuration complete
Oct 2 16:38:29 MAHP02 bootpd[1382]: reading new "/etc/bootptab"
Oct 2 16:38:29 MAHP02 bootpd[1382]: syntax error in entry for host "ignite-defa
ults"
Oct 2 16:38:29 MAHP02 bootpd[1382]: entry with hostname "ignite-defaults" will
be ignored.
Oct 2 16:38:29 MAHP02 bootpd[1382]: can't find tc="ignite-defaults"
Oct 2 16:38:29 MAHP02 bootpd[1382]: bad hardware address for host "vm03A"
Oct 2 16:38:29 MAHP02 bootpd[1382]: entry with hostname "vm03A" will be ignored
.
Oct 2 16:38:29 MAHP02 bootpd[1382]: read 0 entries from "/etc/bootptab"
Oct 2 16:38:29 MAHP02 bootpd[1382]: reading "/etc/dhcpdeny"
Oct 2 16:38:29 MAHP02 bootpd[1382]: error opening "/etc/dhcpdeny": No such file
or directory
Oct 3 11:32:03 MAHP02 inetd[1077]: Rereading configuration
Oct 3 11:32:03 MAHP02 inetd[1077]: Configuration complete
Oct 3 11:32:20 MAHP02 bootpd[1382]: reading new "/etc/bootptab"
Oct 3 11:32:20 MAHP02 bootpd[1382]: syntax error in entry for host "ignite-defa
ults"
Oct 3 11:32:20 MAHP02 bootpd[1382]: entry with hostname "ignite-defaults" will
be ignored.
Oct 3 11:32:20 MAHP02 bootpd[1382]: can't find tc="ignite-defaults"
Oct 3 11:32:20 MAHP02 bootpd[1382]: bad hardware address for host "vm04A"
Oct 3 11:32:20 MAHP02 bootpd[1382]: entry with hostname "vm04A" will be ignored
.
Oct 3 11:32:20 MAHP02 bootpd[1382]: read 0 entries from "/etc/bootptab"
Oct 3 11:32:20 MAHP02 bootpd[1382]: reading "/etc/dhcpdeny"
Oct 3 11:32:20 MAHP02 bootpd[1382]: error opening "/etc/dhcpdeny": No such file
or directory
#

Re: Ignite on VM

Tim Nelson — Fri, 03 Oct 2008 15:13:01 GMT

The best way to use an ignite server to boot a vm guest is with a boot helper image.

1) the VM console does not have the dbprofile functionality.
2) Integrity servers do not use bootptab they use instl_adm

save yourself alot of headache and use #/opt/ignite/data/scripts/examples/make_media_install -r B.11.31 -m iso_directory

copy the iso file to your vHost and then present the ISO file as a vDVD, or even better present the directory as a null vDVD which allows you to select a file using the IN and EJ commands from the vConsole. The same ISO file can be presented to every vGuest. Remeber to make a new ISO whenever you upgrade ignite because they must be the same version.

Once the Ignite boot helper image is booted you can modify the installer screen to use your ignite server.

Re: Ignite on VM

Tim Nelson — Fri, 03 Oct 2008 15:14:34 GMT

correction:
newer versions of ignite use /etc/opt/ignite/instl_boottab not bootptab ( they can probably use both but why confuse the matter).

Re: Ignite on VM

Grayh — Fri, 03 Oct 2008 15:28:01 GMT

I found the following note in instl_boottab file

NOTE: This table is only for booting PA-RISC clients. For booting IPF clients
you have to edit /etc/bootptab. Please see the example in
/etc/bootptab for instruction how to add entries.

# _media_install -r B.11.23 -m iso_directory <
WARNING: Non-default -m option value specified along with default -p option valu
e; the default directory could run out of disk space, should both options be giv
en?
=== Step 1: Make Ignite-UX config files for golden image archive(s) ===
=== Step 2: Copy SD depot(s) and make config files for them ===
=== Step 3: Make a boot-image (LIF volume) ===
+ /opt/ignite/bin/make_medialif -a -r B.11.23 -f /opt/ignite/data/Rel_B.11.23/co
nfig -l /var/opt/ignite/media/pseudo_root/bootvol.lif

How to copy this to the virtual host... I am using HP-UX 11.23...

Re: Ignite on VM

Grayh — Fri, 03 Oct 2008 15:28:58 GMT

# _media_install -r B.11.23 -m iso_directory <
WARNING: Non-default -m option value specified along with default -p option valu
e; the default directory could run out of disk space, should both options be giv
en?
=== Step 1: Make Ignite-UX config files for golden image archive(s) ===
=== Step 2: Copy SD depot(s) and make config files for them ===
=== Step 3: Make a boot-image (LIF volume) ===
+ /opt/ignite/bin/make_medialif -a -r B.11.23 -f /opt/ignite/data/Rel_B.11.23/co
nfig -l /var/opt/ignite/media/pseudo_root/bootvol.lif
+ /opt/ignite/bin/instl_adm -b -F /var/opt/ignite/media/pseudo_root/bootvol.lif
=== Step 4: Make ISO media image ===
+ cp -p /opt/ignite/boot/Rel_B.11.23/EFI_CD_image /var/opt/ignite/media/pseudo_r
oot
+ /opt/ignite/lbin/mkisofs -U -max-iso9660-filenames -no-emul-boot -b EFI_CD_ima
ge -R -eltorito-alt-boot -no-emul-boot -b bootvol.lif -o iso_directory/image.iso
/var/opt/ignite/media/pseudo_root
Warning: creating filesystem that does not conform to ISO-9660.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
Size of boot image is 10240 sectors -> No emulation
Size of boot image is 597648 sectors -> No emulation
3.29% done, estimate finish Fri Oct 3 12:26:25 2008
6.58% done, estimate finish Fri Oct 3 12:26:25 2008
9.86% done, estimate finish Fri Oct 3 12:26:25 2008
13.15% done, estimate finish Fri Oct 3 12:26:25 2008
16.43% done, estimate finish Fri Oct 3 12:26:25 2008
19.73% done, estimate finish Fri Oct 3 12:26:25 2008
23.01% done, estimate finish Fri Oct 3 12:26:25 2008
26.30% done, estimate finish Fri Oct 3 12:26:21 2008
29.58% done, estimate finish Fri Oct 3 12:26:22 2008
32.87% done, estimate finish Fri Oct 3 12:26:22 2008
36.15% done, estimate finish Fri Oct 3 12:26:25 2008
39.44% done, estimate finish Fri Oct 3 12:26:25 2008
42.72% done, estimate finish Fri Oct 3 12:26:23 2008
46.02% done, estimate finish Fri Oct 3 12:26:23 2008
49.30% done, estimate finish Fri Oct 3 12:26:23 2008
52.59% done, estimate finish Fri Oct 3 12:26:23 2008
55.87% done, estimate finish Fri Oct 3 12:26:23 2008
59.16% done, estimate finish Fri Oct 3 12:26:23 2008
62.44% done, estimate finish Fri Oct 3 12:26:23 2008
65.73% done, estimate finish Fri Oct 3 12:26:23 2008
69.01% done, estimate finish Fri Oct 3 12:26:23 2008
72.31% done, estimate finish Fri Oct 3 12:26:22 2008
75.59% done, estimate finish Fri Oct 3 12:26:22 2008
78.88% done, estimate finish Fri Oct 3 12:26:22 2008
82.16% done, estimate finish Fri Oct 3 12:26:22 2008
85.45% done, estimate finish Fri Oct 3 12:26:23 2008
88.73% done, estimate finish Fri Oct 3 12:26:23 2008
92.02% done, estimate finish Fri Oct 3 12:26:23 2008
95.30% done, estimate finish Fri Oct 3 12:26:23 2008
98.59% done, estimate finish Fri Oct 3 12:26:23 2008
Total translation table size: 2048
Total rockridge attributes bytes: 846
Total directory bytes: 4096
Path table size(bytes): 40
Max brk space used 1c000
152151 extents written (297 MB)
=== Step 5: Combine LIF volume and media image ===
+ /opt/ignite/lbin/instl_combine -C iso_directory/image.iso
El Torito offset for LIF volume is: 0x50e800
Adjusting LIF file: ISL (Old iplstart: 4096; New iplstart: 5306368)
Adjusting LIF file: AUTO
Adjusting LIF file: INDEX
Adjusting LIF file: CONFIG
Adjusting LIF file: HPUX
Adjusting LIF file: FWWKAR6
Adjusting LIF file: FWWKAR7
Adjusting LIF file: FWWKAR8
Adjusting LIF file: WINSTALL
Adjusting LIF file: WINSTALLFS
Adjusting LIF file: IINSTALL
Adjusting LIF file: IINSTALLFS
Adjusting LIF file: INSTCMDS
Adjusting LIF file: SYSCMDS
Adjusting LIF file: INSTCMDSIA
Adjusting LIF file: SYSCMDSIA
Adjusting LIF file: SCRIPTS
Adjusting LIF file: PAD
=== Step 6: Write image file to tape/CD/DVD media ===
+ /opt/ignite/lbin/growisofs -Z /dev/rdsk/c0t0d0=iso_directory/image.iso
:-( unable to open("/dev/rdsk/c0t0d0",O_RDONLY): No such device or address
+ Error 83 /opt/ignite/lbin/growisofs failed.
/opt/ignite/data/scripts/examples/make_media_install: ERROR: /opt/ignite/lbin/gr
owisofs failed.
#

Re: Ignite on VM

Tim Nelson — Fri, 03 Oct 2008 15:36:28 GMT

In the output directory defined by -m you will have a file called image.iso.
(or find /opt/ignite -name "*iso" )

ftp it to your vHost and present it as a vDVD backingstore to your guests. If you wish to present to many vGuests then hpvmdevmgmt to set the share attribute.

hpvmmodify -P guest1 -a dvd:scsi::file:/iux/v7.144.image.iso
or
hpvmmodify -P guest1 -a dvd:scsi::null/iux
(to present the whold directory and use EJ/IN in the vConsole to pick a file)

( sorry about the bootptab info, I had them backwards ). Had so many issues in the past with DHCP that I stopped messing with it and created the boot helper images wherever I could.

Re: Ignite on VM

Rita C Workman — Fri, 03 Oct 2008 15:56:28 GMT

I started writing some documentation for the other guy. Here's what I have on installing via Ignite server.

Let me know if makes any sense to you!
=========================================

To Load via Ignite Server
[Time to Install from IUX approx 1.5 hours]

This is the one that takes a little getting used to with virtualization. Normally the new server to build has no IP, so being able to use the network was out of the question. However, remember that the new Virtual Machine (Client/Guest) is being serviced by the VM Host, and he host is on the network. That is the connection we use to enable loading the O/S via the network. It starts with the virtual network switch that you have already added to your new Virtual Machine (Client/Guest).

Gather Information on VM Client

hpvmstatus â p -v

You are looking for the MAC address of the network interface. Write this address down for your next step.

Edit the install_boottab file

On the Ignite Server edit the /etc/opt/ignite/install_boottab
You want to add the VM Client Mac Address information

1.2.3.4:::reserved

Note: 1.2.3.4 = IP for new VMClient
[You may already see a list of ready IP addresses]
with no dashes or spaces
Two colons
reserved = this notation reserves this IP for this client

Starting the Boot/Install Process from IUX to VM Client
On the Ignite (IUX) Server:

Click on Actions
Click on Boot Client
Complete box with new VM Client name
Continue through screens
You will come to screen that requests you to Install-UX from this
new console.
Respond = Y

The Ignite-UX Installation menu appears
Top section has asterick next to Install from Ignite Server
Bottom Section
Select/enter asterick on Advanced Options

The install will continue and stop at your screen to select the O/S version,
software,filesystems,etc. for your manual selections.

Basics Tab
Select the version of O/S you wish to install

Software Tab
Ensure left panel highlights ALL
Select any changes in right panel to Add or Remove software

System Tab
Put in the correct information for this virtual machine, plus:
TimeZone â ESDT
Set password to virtual machine name
Remember to also enter info under:
Network:
Add
Default GW = 10.25.200.1
hop = 1
DNS
Add 10.25.230.2
Add 10.25.230.3
NIS
Skip at this time
XNTP
Add 10.25.200.130

FileSystem Tab
Modify the sizing standard to â Fixed Megabytesâ (Not % or Range)
Click on Add/Modify disk to add disk for vg00 so you have
sufficient disk space for your O/S.
Set them as:
LVM to vg00
Click on Modify button

Advanced Tab
Skip at this time

Press Go!

Correct any issues if required and press Go! again to install.

Hope it helps,
Rgrds,
Rita

Re: Ignite on VM

Rita C Workman — Fri, 03 Oct 2008 15:58:56 GMT

Sorry...looks like some lines garbaged up in the cut/paste here:

hpvmstatus Ã¢Â Â p -v

Actually reads as:

hpvmstatus -p -v

/rcw

Re: Ignite on VM

Grayh — Mon, 06 Oct 2008 20:38:55 GMT

I am still getting the error

[VM03A] vMP> in

Insertable Guest Devices
Num Hw-path (Bus,Slot,Tgt) Gdev
--------------------------------------------
[1] 0/0/0/0.4.0 (0,0,4) dvd

Enter menu item number or [Q] to Quit: 1

hpvmconsole: Skipped 1 unsuitable file(s) for the following reasons:
World-writeable: 1

** Error: No files are available for the requested device. **

-> Command failed.

Re: Ignite on VM

Torsten. — Tue, 07 Oct 2008 03:51:50 GMT

>>
Oct 2 16:38:29 MAHP02 bootpd[1382]: reading new "/etc/bootptab"
Oct 2 16:38:29 MAHP02 bootpd[1382]: syntax error in entry for host "ignite-defa
ults"

You **STILL** have this syntax error!

Do you remember all the advises in your previous thread?

Delete this entry and type again - I think you have unprintable characters anywhere between.

Re: Ignite on VM

Grayh — Tue, 07 Oct 2008 12:04:01 GMT

Now i get a different error after correcting entries in /etc/bootptab

[VM03B] vMP> in

Insertable Guest Devices
Num Hw-path (Bus,Slot,Tgt) Gdev
--------------------------------------------
[1] 0/0/0/0.3.0 (0,0,3) dvd
[2] 0/0/0/0.4.0 (0,0,4) dvd
[3] 0/0/0/0.5.0 (0,0,5) dvd

Enter menu item number or [Q] to Quit: 3
hpvmconsole: Could not find backing-store parameter "/tmp/image.iso" for this de
vice.

** Error: No files are available for the requested device. **

-> Command failed.

Re: Ignite on VM

Torsten. — Tue, 07 Oct 2008 16:32:55 GMT

Why do you need 3 DVD drives?

The system is searching this file: "/tmp/image.iso" - do you have it?

Re: Ignite on VM

Doug O'Leary — Tue, 07 Oct 2008 17:44:43 GMT

Hey;

I freely admit I didn't read through all the posts on this topic nor in your previous topic, so if this is completely out of whack, please feel free to ignore it

With that said: why are you using the bootptab or a helper? I had asked a related question about booting an itanium box using the console (http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1263785) and was told about the dbprofile.

I just built two ivms and ignited them using that same exact process. It worked like a champ.

1. Boot the vm to an efi shell

2. Create the dbprofile:
Shell> dbprofile -dn "${dn_name}" -cip ${client_ip} -sip ${ignite_server} -gip ${gateway_ip} -m ${netmask} -b "/opt/ignite/boot/nbp.efi"

3. Once entered: lanboot select -dn ${dn_name}

I found out, while building the vms, that the quotes around the words are needed - even if they're single words. I didn't put quotes the first time and it choked.

HTH. Like I said, I didn't read the whole post so maybe you're trying to solve a different problem. Using the dbprofile, though, I was able to ignite virtual machines w/o issue.

Doug O'Leary

Re: Ignite on VM

Grayh — Wed, 08 Oct 2008 18:56:09 GMT

I still have issues with ignite on my VM.. but now I have cold- installed it

Thanks everyone for ur valuable time