qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Packets dropped on tap interfaces


From: Mike Lovell
Subject: Re: [Qemu-discuss] Packets dropped on tap interfaces
Date: Mon, 11 Jun 2012 18:54:54 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

On 06/11/2012 05:14 PM, Supriya Kher wrote:

Hi everyone,

I have an issue with the tap interfaces in QEMU.

Setup Description:
Here is the long issue description to give you some background:
I have a Ubuntu 11.04 host running QEMU emulator (qemu-system-x86_64. Qemu version 0.14.0)
The VM running on this host machine has an internal VM running a second Linux operating system.
This is a VM inside a VM architecture, it being so for a reason.

Now, consider two such virtual machines running on this Ubuntu host.
Both these VMs talk to each other via bridged interfaces.

brctl show on Ubuntu host:

brctl show
bridge name     bridge id                   STP enabled     interfaces
base_br6                8000.12b225a87738       no          btap_6_3
                                                                               btap_6_7

The VMs running on this Ubuntu Host are:
1) VM_A 

    brctl show on VM_A
   bridge name     bridge id                STP enabled     interfaces
   base_br0        8000.001cae060703       no              btap1
                                                                              btap2
                                                                              eth3     
   VM_A is also running QEMU emulator to host another VM ( alias internal guest or VM_A_Internal )
   tipc-config -l -netid -addr -n issued on VM_A_Internal
   Links:
   broadcast link: up
   current network id: 7777
   node address: <6.1.7>
   Neighbors:
   No nodes found.
  
   eth0 on VM_A_Internal is configured as the bearer interface that sends out
   TIPC neighbor discovery packets to detect its neighbor and locate VM_B_Internal as its neighbor.   

   Similar settings applicable to VM_B.

2) VM_B - running QEMU emulator to host VM_B_Internal

    brctl show on VM_B
    bridge name     bridge id                STP enabled     interfaces
    base_br0        8000.001cae060300       no              btap1
                                                                              btap2
                                                                              eth3     
    tipc-config -l -netid -addr -n issued on VM_B_Internal
    Links:
    broadcast link: up
    current network id: 7777
    node address: <6.1.3>
    Neighbors:
    No nodes found.

    eth0 on VM_B_Internal is configured as the bearer interface that sends out TIPC neighbor discovery packets
    to detect its neighbor and locate VM_A_Internal as its neighbor.   

ISSUE:
Now the issue is that all these packets ( TIPC control packets ) generated by the inner guest VMs are being
dropped by the tap interfaces on VM_A and VM_B ( confirmed by the Rx drop count and Tx drop count shown by
netstat -i command) The host Ubuntu system also reports a drop of Rx & Tx packets at the base_br6 bridge.

How do we avoid the packet drops at the tap interfaces created by QEMU ? Am I missing something here ?

Note: The two inner guest VMs can see each other. Pinging the IP Addresses configured on the btap<x> interface works.
However the neighborhood detection does not, indicating that these packets alone are being dropped. Firewall on the host
has been configured to FORWARD incoming and not REJECT/DROP any packet.

this is a shot in the dark since i'm not quite following what you are describing. are you making sure the mac addresses for all of the qemu guests (both the first and second level) have unique mac addresses? if you are using a libvirt based tool, they probably are unique. but if you are specifying the qemu commands directly and are not specifying mac addresses on all the guests, then there is a high probability that your problem are due to mac address conflicts.

its a little confusing as to what you are describing. i've done qemu inside of qemu before successfully but, from your description, i'm not quite sure what the various interfaces are connected to.

mike

reply via email to

[Prev in Thread] Current Thread [Next in Thread]