Hide Forgot
Description of problem: I used two interfaces for child vm eth0 and eth1 using interface type = ethernet, eth0 is working fine but eth1 is not working. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start child VM for 2 interfaces supporting using interface type = ethernet -net nic,macaddr=xxx:fe,vlan=0,name=nic0 -net tap,ifname=tap1,script=/KVM/vm-tap1.sh,vlan=0,name=tap1 -net nic,macaddr=xxx,vlan=1,name=nic1 -net tap,ifname=tap2,script=/KVM/vm-tap2.sh,vlan=1,name=tap2 Above script create tap interface and add desire ip route automatically, i mention the detail of script in Additional info section. 2. On child up the eth1 and ping from kvm host , its not pinging/responding. Actual results: when try to ping eth1 from kvm host, its gives destination unreachable, as eth0 is pinging . tcpdump on eth1 guest and arp results on kvm host shows below. tcpdump on eth1 17:05:55.213100 ARP, Request who-has 22.22.22.22 tell x.x.x.x, length 46 17:05:56.213493 ARP, Request who-has 22.22.22.22 tell x.x.x.xlength 46 Arp -e results on kvm host Address HWtype HWaddress Flags Mask Iface x.x.x.x ether 52:54:00:56:40:56 C tap1 --> ok for eth0 x.x.x.x (incomplete) tap2 --> problem for eth1 Expected results: eth1 should be ping and accessible from kvm host and from outer world. Additional info: Above Network script use below #!/bin/bash IP= x.x.x.x # (ip of eth1) TAP=tap2 SIP=x.x.x.x # (ip of kvm host) tap=`ifconfig |grep $TAP` if [ "$tap" == '' ] ;then tap=`tunctl -b -u root -t $TAP` fi ifconfig $TAP $SIP netmask 255.255.255.255 up echo 1 > /proc/sys/net/ipv4/conf/$TAP/proxy_arp route=`ip route show |grep $IP` if [ "$route" == '' ] ;then ip route add $IP/32 dev $TAP fi Same above all is working for eth0 , but eth1 is not working/responding. I sure if same is working for eth0 then it must be working for eth1, but it cant work Kindly suggest please. Thanks Muzi
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
As far as I can tell, this BZ does not have anything to do with libvirt, but it's difficult to say for certain, so I'm closing as INSUFFICIENT_DATA. If you are using libvirt, please reopen and supply the domain xml for the guest and the libvirt logs.