On 07/29/2015 02:45 AM, zhanghailiang wrote:
The 'forward_nic' should be assigned with network name,
for exmple, 'eth2'. It will be parameter of 'colo_script',
s/exmple/example/
'colo_script' should be assigned with an scirpt path.
s/scirpt/script/
We parse these parameter in tap.
s/parameter/parameters/
Cc: Stefan Hajnoczi <address@hidden>
Cc: Jason Wang <address@hidden>
Cc: Eric Blake <address@hidden>
Cc: Markus Armbruster <address@hidden>
Signed-off-by: zhanghailiang <address@hidden>
Signed-off-by: Li Zhijian <address@hidden>
---
include/net/colo-nic.h | 23 +++++++++++++++++++++++
include/net/net.h | 2 ++
net/tap.c | 26 +++++++++++++++++++++++---
qapi-schema.json | 8 +++++++-
qemu-options.hx | 7 +++++++
5 files changed, 62 insertions(+), 4 deletions(-)
create mode 100644 include/net/colo-nic.h
Interface review.
+
+typedef struct COLONicState {
+ char nicname[128]; /* forward dev */
+ char script[1024]; /* colo script */
+ char ifname[128]; /* e.g. tap name */
+} COLONicState;
Are these fixed-width fields sufficiently sized; and are you sure you
won't overflow the buffers?
+++ b/qapi-schema.json
@@ -2296,6 +2296,10 @@
#
# @queues: #optional number of queues to be created for multiqueue capable tap
#
+# @forward_nic: #optional the name of host physical forward nic for COLO
(Since 2.4)
Long line, please wrap to fit in 80 columns.
+#
+# @colo_script: #optional the script file which used by COLO (Since 2.4)
2.5 for both parameters.
New parameters should favor '-' over '_' except for consistency with
older commands; I guess the fact that we already have 'vnet_hdr'
qualifies as that unfortunate consistency.
Script files are very poor design. Management apps like libvirt CANNOT
police what happens in the script file, and have to mark the entire
domain as untrusted if a script file is used. Are you sure you can't
accomplish this through a saner method, such as allowing management to
pre-open an fd and pass that in to qemu, rather than having qemu execute
a script file?