qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: cauchy-love <cauchy-love@163.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>,
	idan.brown@ravellosystems.com,
	Shmulik Ladkani <shmulik.ladkani@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems on vlan-based vnics!
Date: Tue, 29 Sep 2015 11:19:41 +0800	[thread overview]
Message-ID: <560A034D.6020206@redhat.com> (raw)
In-Reply-To: <28e2f008.b3d6.15013cc4e1a.Coremail.cauchy-love@163.com>



On 09/28/2015 07:52 PM, cauchy-love wrote:
> hi stefan.
>    I have setup a VM on a server with two NICs (eth0 and eth1).  eth0 is connected with vlan22 and eth1 is connected with vlan33. I then added eth0.22 to br2  and eth1.33 to br3. after that tap2 and tap3 were added to br2 and br3 respectively. When i start up the vm,  the network connection is failed if tap2 and tap3 are allocated to this VM while it is ok if i only allocate one tap to this VM. It is shown that the packets were all routed to one NIC. So what is the problem?
> yi
>

Need more information. You qemu command line or libvirt xml. Versions of
qemu, host kernel and guest kernel. Is the issue only reproduced with
e1000 or others? Does it work if there's no vlan? And maybe you can try
qemu.git to see if it could be reproduced.

Thanks

>
>
> --
> 发自我的网易邮箱手机智能版
>
>
> 在 2015-06-22 20:13:20,"Stefan Hajnoczi" <stefanha@gmail.com> 写道:
>> On Sat, Jun 20, 2015 at 02:26:29PM +0300, Shmulik Ladkani wrote:
>>> Currently, MAX_NICS is hardcoded as 8.
>>>
>>> Add a configuration option '--net-max-nics' so one can override the
>>> default.
>>> Unless specified, default value is kept as 8.
>>>
>>> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
>>> ---
>>>  configure         | 7 +++++++
>>>  include/net/net.h | 2 +-
>>>  2 files changed, 8 insertions(+), 1 deletion(-)
>> The -device e1000,netdev=tap0,id=e1000-nic0 syntax is preferred to -net
>> nic syntax and does not have the 8 NIC limit.
>>
>> Please use the -device syntax instead of -net.  Emulated NICs that
>> support virtio_net_hdr offload also perform better with the -device
>> syntax because -net nic does not allow virtio_net_hdr offloads.
>>
>> If you think this patch should be merged, please explain the use case.

  reply	other threads:[~2015-09-29  3:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 11:26 [Qemu-devel] [PATCH] net: Allow specifying maximum number of network NICs during configure Shmulik Ladkani
2015-06-22 12:13 ` Stefan Hajnoczi
2015-06-22 14:42   ` Shmulik Ladkani
2015-09-28 11:52   ` [Qemu-devel] Problems on vlan-based vnics! cauchy-love
2015-09-29  3:19     ` Jason Wang [this message]
2015-09-29  5:28       ` cauchy-love
2015-09-29  5:36       ` cauchy-love
2015-09-29 11:46       ` cauchy-love

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560A034D.6020206@redhat.com \
    --to=jasowang@redhat.com \
    --cc=cauchy-love@163.com \
    --cc=idan.brown@ravellosystems.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shmulik.ladkani@gmail.com \
    --cc=shmulik.ladkani@ravellosystems.com \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).