After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
HMC was connected to the machine
then HMC was removed through ASMI
Searching on google found this
Quote:
I/O hosting requires a hosting partition - boot not permitted
exit called ok
This happened with me when I created an AIX LPAR, but a VIO image was installed on the disk, where I wanted to boot from.
(When there is a mismatch between the LPAR type and the booting image this error will pop up....I guess.)
But doesn't mention solution,
how can one solve "mismatch between the LPAR type and the booting image"
When using PowerVM Express and IVM (no HMC) on a Power6 P520 , can I configure 2 LPARs in addition to a VIO server, or does the VIO Server count as one of the two LPAR's that PowerVM Express allows? (1 Reply)
Hi everyone,
Sorry if this post is in the wrong place. I searched the forums for "IVM" and it turned up no results. Hopefully someone knows about this. My dilemma is that I have multiple IBM JS12 Express blades in our blade center, each running VIOS 2.1.0.10-FP-20.1 and hosting a couple LPARs. Out... (2 Replies)
hi guys,
i need to develop following setup for a customer:
high availability oracle database on aix7 and linux in 2 different LPAR using dual ps700 blande a ds3400 and HMC.
the question is, it is possible to have automatic vioc failover(aix,linux) when for example 1 vios goes down?
in... (6 Replies)
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Hi,
When I try to login on my vios ivm website http://vios through the browser -- all three of them -- firefox , chrome , Internet Explorer , i get this error
http://vioserver/j_security_check
I have java installed on the machine from where i am trying to open up the IVM/VIOS webpage.
I... (2 Replies)
Hello,
I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization.
So when booted , it goes into OPEN Firmware
I/O Hosting requires a hosting partition boot not permitted exit called
> ok
Panel shows > IO... (3 Replies)
I am facing problems in moving CD-ROM from one lpar to another.
CDROM can be seen on the POWERVM (IVM) server , but through the web-access if I move it ( assign it ) to LPAR it will be assigned. I run cfgmgr , and the cdrom does not show up in the LPAR. I firmly believe this is the reason why I... (2 Replies)
Hi All,
I have a p520 box running 3 LPARs, 1 x VIOS, 1 x AIX 6.1 and 1 x AIX 7.1 and no HMC, all configuration is performed via VIOS/IVM
Until recently the box did not have the AIX7.1 LPAR and everything was fine with the box.
We needed to use AIX 7.1 for a new project, so I created a... (11 Replies)
coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html
PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies
LEARN ABOUT LINUX
installgrub
installgrub(1M)installgrub(1M)NAME
installgrub - install GRUB in a disk partition or a floppy
SYNOPSIS
/sbin/installgrub [-fm] stage1 stage2 raw-device
The installgrub command is an -only program. GRUB stands for GRand Unified Bootloader.
installgrub installs GRUB stage 1 and stage 2 files on the boot area of a disk partition. If you specify the -m option, installgrub
installs the stage 1 file on the master boot sector of the disk.
The installgrub command accepts the following options:
-f
Suppresses interaction when overwriting the master boot sector.
-m
Installs GRUB stage1 on the master boot sector interactively.
The installgrub command accepts the following operands:
stage1
The name of the GRUB stage 1 file.
stage2
The name of the GRUB stage 2 file.
raw-device
The name of the device onto which GRUB code is to be installed. It must be a character device that is readable and writable. For disk
devices, specify the slice where the GRUB menu file is located. (For Solaris it is the root slice.) For a floppy disk, it is
/dev/rdiskette.
Example 1: Installing GRUB on a Hard Disk Slice
The following command installs GRUB on a system where the root slice is c0d0s0:
example# /sbin/installgrub /boot/grub/stage1
/boot/grub/stage2 /dev/rdsk/c0d0s0
Example 2: Installing GRUB on a Floppy
The following command installs GRUB on a formatted floppy:
example# mount -F pcfs /dev/diskette /mnt
# mkdir -p /mnt/boot/grub
# cp /boot/grub/* /mnt/boot/grub
# umount /mnt
# cd /boot/grub
# /sbin/installgrub stage1 stage2 /dev/rdiskette
/boot/grub
Directory where GRUB files reside.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
boot(1M), fdisk(1M), fmthard(1M), kernel(1M), attributes(5)
Installing GRUB on the master boot sector (-m option) overrides any boot manager currently installed on the machine. The system will always
boot the GRUB in the Solaris partition regardless of which fdisk partition is active.
24 May 2005 installgrub(1M)