golden Image, NFS mount, boot error

[Patrick Wallek]

According to the Ignite Admin guide, the recommended NFS shares are:

For Ignite servers running HP-UX 11i v3:

# cat /etc/dfs/dfstab

share -F nfs -o ro /opt/ignite/data

share -F nfs -o ro /var/opt/ignite/data

share -F nfs -o anon=2 /var/opt/ignite/clients

[Syedfurquan]

Hello Expert,

Thanks to everyone for the support to fix my issue.

As per Dennis suggestion I tried removing the "rw=.." from /etc/dfs/dfstab and shared to everyone...

After this am able to boot the virtual machine from the archive image created on ignite server but the virtual machine is not booting it just get crashed after completing the start services...

  Start HP Virtual Machine Monitor ............................... BOOT

"Reboot of system has been requested -- rebooting..." This message comes after starting all teh services and vm get rebooted

attached all the logs related to it.... Appreciate if get any help on it...

[Matti_Kurkela]

For some reason, the startup script for HP Virtual Machine Monitor returns an exit value of 3, which tells the system that a reboot is needed. If that happens each time you try to boot the system, boot it to single user mode instead, and read /etc/rc.log and /etc/rc.log.OLD. Those log files might include a more descriptive error message from the Virtual Machine Monitor.

This error is probably not related to your /etc/dfs/dfstab change, unless the Virtual Machine Monitor is configured to use the share(s) you modified.

[Syedfurquan]

Hello Matti,

Thanks for the reply.

As per your suggestion I tried to boot the HP Integrity virtual machine in single user mode. Checked the logs rc.log and the only thing I get their is:

Start HP Virtual Machine Monitor
Output from "/sbin/rc2.d/S533hpvm start":
----------------------------
Host tunables must be reset on the Integrity virtual machine
NOTE:    The requested changes could not be applied to the currently
         running system, for the following reasons:
         - Requested value of lockable_mem_pct rolled back
         - The requested value of lockable_mem_pct is invalid
       * The requested changes have been saved, and will take effect at
         next boot.
Tunable                         Value  Expression  Changes
lockable_mem_pct  (now)         27838  99%         Imm (auto disabled)
                  (next boot)  (auto)  Default
       * The requested changes have been applied to the currently
         running configuration.
Tunable                       Value  Expression  Changes
filecache_max  (before)    21348352  1%          Auto
               (now)     1067384832  Default
       * The requested changes have been applied to the currently
         running configuration.
Tunable                      Value  Expression  Changes
filecache_min  (before)   21348352  1%          Auto
               (now)     106692608  Default
       * The requested changes have been applied to the currently
         running configuration.
Tunable                        Value  Expression   Changes
maxdsiz_64bit  (before)  34359738368  34359738368  Immed
               (now)      4294967296  Default

There is no rc.log.OLD.

I ma not able to get anythings from this logs. Please let me know if you can find something which will help me in resolving this issue.

Regards,

Syed

[Dennis Handly]

>The requested value of lockable_mem_pct is invalid

This might be the problem.

[Matti_Kurkela]

I agree with Dennis.

Looks like HPVM is trying to set lockable_mem_pct to 27838. Since lockable_mem_pct is a percentage tunable, the new value makes no sense at all.

You may have found a bug. I would recommend opening an Integrity VM support call with HP.

You might also want to investigate how the Integrity VM start-up script determines the required tunable values and see if something is wrong with that.

...Wait. This is trying to start the HP Virtual Machine Monitor. And you said this log is from the virtual machine. Are you trying to start another instance of HP IVM within a HP IVM virtual machine? That is unlikely to work.