Bug 1372173 - [ppc64le] spapr-vlan device can't be added to a bonding team in RHEL6.8 guest
Summary: [ppc64le] spapr-vlan device can't be added to a bonding team in RHEL6.8 guest
Keywords:
Status: CLOSED DUPLICATE of bug 1371419
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Laurent Vivier
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 06:26 UTC by Zhengtong
Modified: 2016-09-08 01:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-08 01:05:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zhengtong 2016-09-01 06:26:06 UTC
Description of problem:
In RHEL6.8 guest. spapr-vlan nic device can't be added to bonding team

Version-Release number of selected component (if applicable):
Host: 3.10.0-496.el7.ppc64le
qemu-kvm-rhev-2.6.0-22.el7
Guest kernel:2.6.32-642.6.1.el6.ppc64

How reproducible:
2/2

Steps to Reproduce:
1.Boot up guest with spapr-vlan device:
# /usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1'  \
    -sandbox off  \
    -machine pseries  \
    -nodefaults  \
    -vga std  \
    -device pci-ohci,id=usb1,bus=pci.0,addr=03 \
    -chardev socket,id=console0,path=/tmp/test,server,nowait \
    -device spapr-vty,chardev=console0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=04 \
    -drive id=drive_image1,if=none,snapshot=off,aio=native,cache=none,format=qcow2,file=/home/RHEL-Server-6.8-ppc64-virtio-scsi.qcow2 \
    -device scsi-hd,id=image1,drive=drive_image1 \
    -device spapr-vlan,mac=9a:e9:ea:eb:ec:ed,id=net0,netdev=hostnet0  \
    -netdev tap,id=hostnet0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \
    -m 8192  \
    -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -device usb-kbd \
    -device usb-mouse \
    -vnc :0  \
    -rtc base=utc,clock=host  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -monitor stdio

2.After guest boot up. In guest . load binding module and add nic device to bond0
#modprobe binding
#ifconfig bond0 up
#ifenslave bond0 eth0

3.Check the result

Actual results(copied from serial output):

[root@localhost ~]# modprobe binding
modprobe binding
FATAL: Module binding not found.
[root@localhost ~]# modprobe bonding
modprobe bonding
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[root@localhost ~]# ifconfig eth0 up
ifconfig eth0 up
[root@localhost ~]# ifconfig bond0 up
ifconfig bond0 up
ADDRCONF(NETDEV_UP): bond0: link is not ready
8021q: adding VLAN 0 to HW filter on device bond0
[root@localhost ~]# ifenslave bond0 eth0
ifenslave bond0 eth0
ibmveth 71000002: eth0: h_change_logical_lan_mac failed with rc=-2
ibmveth 71000002: eth0: h_change_logical_lan_mac failed with rc=-2
Master 'bond0', Slave 'eth0': Error: Enslave failed


Expected results:
no errors , and the device can be add the bond0

Additional info:
Works well with virtio-net
Works well with spapr-vlan on RHEL7.3 guest.

Comment 3 Zhengtong 2016-09-02 02:10:52 UTC
Passed with the given qemu version

[root@localhost ~]# modprobe bonding
[root@localhost ~]# ifconfig bond0 up
[root@localhost ~]# ifenslave bond0 eth1 eth2
[root@localhost ~]# ifconfig bond0
bond0     Link encap:Ethernet  HWaddr 9A:E9:EA:EB:ED:EE  
          inet addr:192.168.122.11  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::98e9:eaff:feeb:edee/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3092 (3.0 KiB)  TX bytes:2148 (2.0 KiB)

Comment 5 David Gibson 2016-09-08 01:05:58 UTC
Zhengtong,

Thanks for the confirmation in comment 3.  Closing as a duplicate of bug 1371419.

*** This bug has been marked as a duplicate of bug 1371419 ***


Note You need to log in before you can comment on or make changes to this bug.