From: <rongqing.li@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH][meta-oe] virt-what: add the recipe
Date: Tue, 29 Mar 2016 16:22:56 +0800 [thread overview]
Message-ID: <1459239776-3868-1-git-send-email-rongqing.li@windriver.com> (raw)
From: Roy Li <rongqing.li@windriver.com>
virt-what is a a shell script which can be used to detect if the program
is running in a virtual machine.
Signed-off-by: Roy Li <rongqing.li@windriver.com>
---
.../recipes-extended/virt-what/virt-what_1.15.bb | 36 ++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 meta-oe/recipes-extended/virt-what/virt-what_1.15.bb
diff --git a/meta-oe/recipes-extended/virt-what/virt-what_1.15.bb b/meta-oe/recipes-extended/virt-what/virt-what_1.15.bb
new file mode 100644
index 0000000..7509eee
--- /dev/null
+++ b/meta-oe/recipes-extended/virt-what/virt-what_1.15.bb
@@ -0,0 +1,36 @@
+SUMMARY = "Detect if we are running in a virtual machine"
+DESCRIPTION =" virt-what is a shell script which can be used to detect if the program \
+is running in a virtual machine. \
+The program prints out a list of "facts" about the virtual machine, \
+derived from heuristics. One fact is printed per line. \
+If nothing is printed and the script exits with code 0 (no error), \
+then it can mean either that the program is running on bare-metal or \
+the program is running inside a type of virtual machine which we don't \
+know about or can't detect. \
+Current types of virtualization detected: \
+ - hyperv Microsoft Hyper-V \
+ - kvm Linux Kernel Virtual Machine (KVM) \
+ - openvz OpenVZ or Virtuozzo \
+ - powervm_lx86 IBM PowerVM Lx86 Linux/x86 emulator \
+ - qemu QEMU (unaccelerated) \
+ - uml User-Mode Linux (UML) \
+ - virtage Hitachi Virtualization Manager (HVM) Virtage LPAR \
+ - virtualbox VirtualBox \
+ - virtualpc Microsoft VirtualPC \
+ - vmware VMware \
+ - xen Xen \
+ - xen-dom0 Xen dom0 (privileged domain) \
+ - xen-domU Xen domU (paravirtualized guest domain) \
+ - xen-hvm Xen guest fully virtualized (HVM) \
+"
+
+SECTION = "base"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
+
+SRC_URI = "http://people.redhat.com/~rjones/virt-what/files/${PN}-${PV}.tar.gz"
+
+inherit autotools
+
+SRC_URI[md5sum] = "35d19ca3305e8ae88c1985fbd8388f53"
+SRC_URI[sha256sum] = "7ab9220d4682eadf9139c6afe62d33ebd273fff69e49054279caba5514937c41"
--
1.9.1
next reply other threads:[~2016-03-29 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 8:22 rongqing.li [this message]
2016-03-29 14:22 ` [PATCH][meta-oe] virt-what: add the recipe Bruce Ashfield
2016-03-30 1:42 ` Rongqing Li
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=1459239776-3868-1-git-send-email-rongqing.li@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.