12-26-2012
I cannot say what the exact problem is, but I must assume that booting via a virtual interface (which is what you are doing using IVM) is not the same as booting from a physical interface. It might have worked with VIOS 1.0 but then there was no IVM.
On POWER5 I can boot from AIX 5.3 TL7, and this should support most/all VIOS 2.2.X versions, but I would assume ML0, what we would now call TL0 will not know enough to proceed with the virtual scsi interface. Linux on Power was a headache for a long time because of issues with booting on virtual disks. Again, I am assuming, i.e., I may be wrong - but I would proceed by making lpar1 a nim server, THEN update to TL12, and nim install lpar2.
This I have been doing for years.
Happy hunting
10 More Discussions You Might Find Interesting
1. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
2. AIX
I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570.
Two Vio server ( VIOS ) and many LPAR clients.
VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2
When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies
3. AIX
Hello,
I have created mapping of 2 virtual adapters for Lpars using following command:
mkvdev -vdev ipanalyzerlv1 -vadapter vhost11
mkvdev -vdev ipanalyzerlv -vadapter vhost13
The above two commands were succesfull
but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
4. AIX
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies
5. AIX
Hi All,
Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great.
... (5 Replies)
Discussion started by: itik
5 Replies
6. AIX
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)
Discussion started by: vilius
0 Replies
7. AIX
Hi guys,
does anyone know how to get a list of the LPAR running on VIOS?
Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies
8. AIX
Hi,
Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems.
I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies
9. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
10. UNIX for Advanced & Expert Users
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
vni(7d) Devices vni(7d)
NAME
vni - STREAMS virtual network interface driver
DESCRIPTION
The vni pseudo device is a multi-threaded, loadable, clonable, STREAMS pseudo-device supporting the connectionless Data Link Provider
Interface dlpi(7P) Style 2. Note that DLPI is intended to interact with IP, meaning that DLPI access to applications is not supported. (For
example, snoop fails on the vni interface.)
The vni device is a software-only interface and does not send or receive data. The device provides a DLPI upper interface that identifies
itself to IP with a private media type. It can be configured via ifconfig(1M) and can have IP addresses assigned to it, making aliases pos-
sible.
The vni pseudo device is particularly useful in hosting an IP address when used in conjunction with the 'usesrc' ifconfig option (see
ifconfig(1M) for examples). The logical instances of the device can also be used to host addresses as an alternative to hosting them over
the loopback interface.
Multicast is not supported on this device. More specifically, the following options return an error when used with an address specified on
vni: IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MULTICAST_IF, IPV6_JOIN_GROUP, IPV6_LEAVE_GROUP. In addition, broadcast
is not supported.
Because there is no physical hardware configured below it, no traffic can be received through nor transmitted on a virtual interface. All
packet transmission and reception is accomplished with existing physical interfaces and tunnels. Because applications that deal with packet
transmission and reception (such as packet filters) cannot filter traffic on virtual interfaces, you cannot set up a packet filter on a
virtual interface. Instead, you should configure the policy rules to apply to the physical interfaces and tunnels, and if necessary, use
the virtual IP addresses themselves as part of the rule configuration. Also, note that the virtual interface cannot be part of an IP multi-
pathing (IPMP) group.
FILES
/dev/vni
64-bit ELF kernel driver
SEE ALSO
ifconfig(1M), in.mpathd(1M), ip(7P), ip6(7P)
SunOS 5.10 18 July 2004 vni(7d)