The following has be reported by IBM LTC:
Dummy.o module not built into rhel3 release
31/64 bit rhel builds guests under VM
Steps to Reproduce:
1. insmod dummy
2. ifconfig dummy0 [vipa address]
3. echo add_vipa4 [hex version of ip address]:[interface1] > /proc/qeth_ipa_takeover
4. echo add_vipa4 [hex version of ip address]:[interface2] > /proc/qeth_ipa_takeover
insmod: dummy: no module by that name found
ifconfig dummy0 220.127.116.11
dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:18.104.22.168 Bcast:22.214.171.124 Mask:255.255.0.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:70 (70.0 b)
We need a not-real interface to put the vipa address on, which typically is done
through a dummy network interface. This is required to do source vipa, as two
additional osa cards will be configured with that vipa address.
Also, the qethconf command, which can be used to query the chpids and retrieve
their configured vipas in decimal is not included.
Pete: it appears s390 explicitly disables dummy in the config... do you remember
why that override is in ?
I was always like that and not a regression against our Mach1 product.
I think it was inherited that way from the port made by Huntsville group.
I see no problem in turning this into FZ request or RFE and expediting it.
Modified in 2.4.21-4.5.EL
Subject: [Bug 4863] - RH106763 Dummy.o module not built into rhel3 release
X-Bugzilla-Reason: AssignedTo QAcontact
X-Bugzilla-Family: zSeries Development
Date: Tue, 14 Oct 2003 12:53:44 -0400 (EDT)
Do not reply to this note. It was sent by a machine. Instead append your
comments to the bug at the URL below.
What |Removed |Added
Summary|RH106783 Dummy.o module not |RH106763 Dummy.o module not
|built into rhel3 release |built into rhel3 release
Closing MODIFIED bugs as fixed. Please reopen if the problem perists.
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.