[Qemu-devel] adding a parameter in qemu tap option
Hi,
I'm trying to understand how to add a parameter in tap option.
I currently have a working config for a vm; i.e several interfaces using
multiqueues.
I had a try with:
--- a/qapi-schema.json
+++ b/qapi-schema.json
-2006,6 +2008,7 @@
##
{ 'type': 'NetdevTapOptions',
'data': {
+ '*foo': 'str',
'*ifname': 'str',
'*fd': 'str',
'*fds': 'str',
i.e just adding a foo parameter; nothing change in my config file (I'm
using -readconfig option and not cmdline)
multiqueue is no longer working in some cases.
I don't get how is it possible. I don't even understand why I don't have
the same behaviour using the cmdline.
Maybe I forgot something obvious.
Does someone has some hints?
Thanks,
--
William
signature.asc
Description: Digital signature
Re: [Qemu-devel] adding a parameter in qemu tap option
On Fri, Aug 22, 2014 at 10:27:35AM +0200, William Dauchy wrote:
Hi,
I'm trying to understand how to add a parameter in tap option.
I currently have a working config for a vm; i.e several interfaces using
multiqueues.
I had a try with:
--- a/qapi-schema.json
+++ b/qapi-schema.json
-2006,6 +2008,7 @@
##
{ 'type': 'NetdevTapOptions',
'data': {
+ '*foo': 'str',
'*ifname': 'str',
'*fd': 'str',
'*fds': 'str',
i.e just adding a foo parameter; nothing change in my config file (I'm
using -readconfig option and not cmdline)
multiqueue is no longer working in some cases.
I don't get how is it possible. I don't even understand why I don't have
the same behaviour using the cmdline.
Maybe I forgot something obvious.
Does someone has some hints?
I don't see any obvious reason from the small diff you have posted. Are
you sure this is the only change you've made and the environment is
unchanged?
Stefan
pgpcb_Rfjxt3u.pgp
Description: PGP signature
