test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lei.a.yao@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 1/4] conf/vm_pw_mgmt_policy: virtual machine configuration
Date: Tue, 24 Dec 2019 09:56:25 +0800	[thread overview]
Message-ID: <20191224015628.11931-2-yufengx.mo@intel.com> (raw)
In-Reply-To: <20191224015628.11931-1-yufengx.mo@intel.com>


add vm_pw_mgmt_policy virtual machine configuration.

Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
 conf/vm_pw_mgmt_policy.cfg | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 conf/vm_pw_mgmt_policy.cfg

diff --git a/conf/vm_pw_mgmt_policy.cfg b/conf/vm_pw_mgmt_policy.cfg
new file mode 100644
index 0000000..bc080fe
--- /dev/null
+++ b/conf/vm_pw_mgmt_policy.cfg
@@ -0,0 +1,30 @@
+# libvirtd options:
+# [VM name] section value is the name for VM
+# cpu       # hard code type to host-passthrough
+#   number: number of vcpus
+#   cpupin: host cpu list
+# mem
+#   size: 4096
+# disk
+#   file: absolute path to disk image
+#   type: disk image format
+# login
+#   user: user name to login into VM
+#   password: passwork to login into VM
+# device
+#   pf_idx: pass-through device index of DUT ports
+#   guestpci: hardcode value of guest pci address
+# virtio_serial_channel
+#   path: virtio unix socket absolute path
+#   name: virtio serial name in VM
+
+# vm configuration for vm power management case
+[vm0]
+cpu =
+    number=8,cpupin=4 5 6 7 8 9 10 11;
+mem =
+    size=8196;
+disk =
+    file=/homeSys/vms/fedora27.img,opt_format=qcow2;
+login =
+    user=root,password=tester;
-- 
2.21.0


  reply	other threads:[~2019-12-24  1:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  1:56 [dts] [PATCH V4 0/4] vm_pw_mgmt_policy: upload suite test plan and script yufengmx
2019-12-24  1:56 ` yufengmx [this message]
2019-12-24  1:55   ` [dts] [PATCH V4 1/4] conf/vm_pw_mgmt_policy: virtual machine configuration Yao, Lei A
2019-12-24  1:56 ` [dts] [PATCH V4 2/4] test_plans/vm_pw_mgmt_policy: add test plan index yufengmx
2019-12-24  1:55   ` Yao, Lei A
2019-12-24  1:56 ` [dts] [PATCH V4 3/4] test_plans/vm_pw_mgmt_policy: upload test plan yufengmx
2019-12-24  1:56   ` Yao, Lei A
2019-12-24  1:56 ` [dts] [PATCH V4 4/4] tests/vm_pw_mgmt_policy: upload automation script yufengmx
2019-12-24  1:56   ` Yao, Lei A
2019-12-27  6:29 ` [dts] [PATCH V4 0/4] vm_pw_mgmt_policy: upload suite test plan and script Tu, Lijuan

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=20191224015628.11931-2-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@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).