12-27-2012
10 More Discussions You Might Find Interesting
1. AIX
Hello Gurus,
i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX.
Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk?
i tried:
# extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies
2. SuSE
Hi.
I was wondering if there was a way to get the PVIDs from the disks on a SuSE Enterprise 9 box. I have 2 hdisks from a VIO setup that have specific PVIDs. I'd like to match those 2 disk to the disks within the Linux box. Any tips?
thanks. (0 Replies)
Discussion started by: Stephan
0 Replies
3. Linux
Anyone can help me answer the question.
Why does they use Linux on IBM pSeries not AIX.
I can't understand why, cause AIX is the best supporting from IBM pSeries.
Tks you. (3 Replies)
Discussion started by: quan0509
3 Replies
4. AIX
Hello,
I successfully entered VET activation key through HMC -> capacity on demand (CoD) -> advanced power virtualization -> activate VET Key .
But the option for VIOS creation is still not appearing.
VET information gives this :
Type de système : 8203
Numéro de série du système : XX-XXXX
CCIN... (2 Replies)
Discussion started by: astjen
2 Replies
5. AIX
Hi all please give me a link for IBM PowerVM (4 Replies)
Discussion started by: babinlonston
4 Replies
6. AIX
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)
Discussion started by: filosophizer
2 Replies
7. AIX
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)
Discussion started by: filosophizer
2 Replies
8. AIX
A team member installed the wrong version of License Code on a Power 740 system used in our Development environment.
The system will no longer boot.
Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies
9. AIX
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
10. AIX
Hello,
After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
"I/O hosting requires a hosting partition - boot not permitted".
HMC was connected to the machine
then HMC was removed through ASMI
Searching on... (2 Replies)
Discussion started by: filosophizer
2 Replies
UEFI(8) BSD System Manager's Manual UEFI(8)
NAME
UEFI -- Unified Extensible Firmware Interface bootstrapping procedures
DESCRIPTION
The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems. UEFI is a replacement for the
legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64.
The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP). The ESP is a GPT or MBR partition with a spe-
cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy.
Partition Scheme ESP Identifier
GPT C12A7328-F81F-11D2-BA4B-00A0C93EC93B
MBR 0xEF
The UEFI boot process proceeds as follows:
1. UEFI firmware runs at power up and searches for an OS loader in the EFI system partition. The path to the loader may be set by an
EFI environment variable. If not set, the default is /EFI/BOOT/BOOTX64.EFI. The default UEFI boot configuration for FreeBSD
installs boot1.efi as /EFI/BOOT/BOOTX64.EFI.
2. boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi.
3. loader.efi loads and boots the kernel, as described in loader(8).
The vt(4) system console is automatically selected when booting via UEFI.
FILES
/boot/boot1.efi
First stage UEFI bootstrap
/boot/boot1.efifat
msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8).
/boot/loader.efi
Final stage bootstrap
/boot/kernel/kernel
default kernel
/boot/kernel.old/kernel
typical non-default kernel (optional)
SEE ALSO
vt(4), msdosfs(5), boot(8), gpart(8)
HISTORY
UEFI boot support first appeared in FreeBSD 10.1.
AUTHORS
UEFI boot support was developed by Benno Rice <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn
<nwhitehorn@FreeBSD.org>. The FreeBSD Foundation sponsored portions of the work.
CAVEATS
EFI environment variables are not supported by loader(8) or the kernel.
boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk.
boot1.efi cannot load loader.efi from a ZFS(8) file system. As a result, UEFI does not support a typical root file system on ZFS configura-
tion.
BSD
October 17, 2014 BSD