From: "Wang, Yinan" <yinan.wang@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1]framework/qemu_libvirt: add new features
Date: Mon, 19 Aug 2019 07:26:03 +0000 [thread overview]
Message-ID: <E0CBA5A1980F1F408E1F28F9991B5B1D50EE700E@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1566190649-151210-1-git-send-email-yufengx.mo@intel.com>
Acked-by: Wang, Yinan <yinan.wang@intel.com>
> -----Original Message-----
> From: Mo, YufengX
> Sent: 2019年8月19日 12:57
> To: dts@dpdk.org; Wang, Yinan <yinan.wang@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V1]framework/qemu_libvirt: add new features
>
> These new features demand come from Intel BKC team and wang,yinan.
> *. support bridge setting in xml.
> *. support vhost-user setting in xml. support to add driver attribute by set option
> opt_queue and opt_setting.
> *. add __add_vm_net_tap method to add tap&bridge net device.
> *. add __generate_net_config_script method to set default br0 using script.
> *. add __write_config method to make recursion write config in xml config file.
> *. use dut logger to take the place of print.
> *. remove graphics vnc config in set_vm_default method, add add_vm_vnc
> method to do graphics vnc setting. This is aimed to keep the same as qemu_kvm
> method.
> *. add add_vm_daemon method to keep the same as qemu_kvm method. libvirt
> run virtual machine with daemon status by default.
>
> yufengmx (1):
> framework/qemu_libvirt: add new features
>
> framework/qemu_libvirt.py | 327
> ++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 273 insertions(+), 54 deletions(-)
>
> --
> 1.9.3
prev parent reply other threads:[~2019-08-19 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 4:57 yufengmx
2019-08-19 4:57 ` yufengmx
2019-08-19 7:25 ` Wang, Yinan
2019-08-28 6:09 ` Tu, Lijuan
2019-08-19 7:26 ` Wang, Yinan [this message]
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=E0CBA5A1980F1F408E1F28F9991B5B1D50EE700E@SHSMSX104.ccr.corp.intel.com \
--to=yinan.wang@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@intel.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).