xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Rajiv Ranganath <rajiv.ranganath@atihita.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org
Subject: [stage1-xen (RFC) PATCH 06/10] build/fedora: Add `xen-unstable-runit/*` scripts
Date: Mon, 21 Aug 2017 12:48:17 +0530	[thread overview]
Message-ID: <20170821071817.65172.6416.stgit@rajivs-macbook-pro.local> (raw)
In-Reply-To: <20170821071721.65172.78369.stgit@rajivs-macbook-pro.local>

From: Rajiv M Ranganath <rajiv.ranganath@atihita.com>


---
 build/fedora/xen-unstable-runit/setup.sh           |   21 ++++++++++++++++++++
 build/fedora/xen-unstable-runit/teardown.sh        |   21 ++++++++++++++++++++
 .../xen-init-dom0-disk-backend/run                 |    8 ++++++++
 build/fedora/xen-unstable-runit/xen-init-dom0/run  |    6 ++++++
 build/fedora/xen-unstable-runit/xenconsoled/run    |   10 ++++++++++
 build/fedora/xen-unstable-runit/xenstored/run      |   20 +++++++++++++++++++
 6 files changed, 86 insertions(+)
 create mode 100755 build/fedora/xen-unstable-runit/setup.sh
 create mode 100755 build/fedora/xen-unstable-runit/teardown.sh
 create mode 100755 build/fedora/xen-unstable-runit/xen-init-dom0-disk-backend/run
 create mode 100755 build/fedora/xen-unstable-runit/xen-init-dom0/run
 create mode 100755 build/fedora/xen-unstable-runit/xenconsoled/run
 create mode 100755 build/fedora/xen-unstable-runit/xenstored/run

diff --git a/build/fedora/xen-unstable-runit/setup.sh b/build/fedora/xen-unstable-runit/setup.sh
new file mode 100755
index 0000000..16699be
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/setup.sh
@@ -0,0 +1,21 @@
+#!/bin/bash
+
+set -e
+set -o pipefail
+
+# runit RPM creates `/etc/service` directory
+if [ ! -d "/etc/service" ]; then
+    echo "/etc/service directory not found. Please install runit RPM."
+    exit 1
+fi
+
+runit_services="xenconsoled xen-init-dom0 xen-init-dom0-disk-backend xenstored"
+
+pushd /etc/service > /dev/null
+for service in $runit_services; do
+    ln -sf /opt/xen-unstable-runit/$service $service
+done
+popd > /dev/null
+
+echo "Successfully created symlinks in /etc/service directory."
+exit 0
diff --git a/build/fedora/xen-unstable-runit/teardown.sh b/build/fedora/xen-unstable-runit/teardown.sh
new file mode 100755
index 0000000..c0895f4
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/teardown.sh
@@ -0,0 +1,21 @@
+#!/bin/bash
+
+set -e
+set -o pipefail
+
+# runit RPM creates `/etc/service` directory
+if [ ! -d "/etc/service" ]; then
+    echo "/etc/service directory not found."
+    exit 1
+fi
+
+runit_services="xenconsoled xen-init-dom0 xen-init-dom0-disk-backend xenstored"
+
+pushd /etc/service > /dev/null
+for service in $runit_services; do
+    rm -f $service
+done
+popd > /dev/null
+
+echo "Successfully deleted symlinks in /etc/service directory."
+exit 0
diff --git a/build/fedora/xen-unstable-runit/xen-init-dom0-disk-backend/run b/build/fedora/xen-unstable-runit/xen-init-dom0-disk-backend/run
new file mode 100755
index 0000000..a952890
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/xen-init-dom0-disk-backend/run
@@ -0,0 +1,8 @@
+#!/bin/sh
+sv check xenstored >/dev/null || exit 1
+sv check xenconsoled >/dev/null || exit 1
+
+# In case of failure, allow user to run teardown script
+sleep 5s
+
+exec /opt/xen-unstable/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -monitor /dev/null -serial /dev/null -parallel /dev/null -nodefaults -no-user-config
diff --git a/build/fedora/xen-unstable-runit/xen-init-dom0/run b/build/fedora/xen-unstable-runit/xen-init-dom0/run
new file mode 100755
index 0000000..f7f56ed
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/xen-init-dom0/run
@@ -0,0 +1,6 @@
+#!/bin/sh
+sv check xenstored >/dev/null || exit 1
+
+/opt/xen-unstable/lib/xen/bin/xen-init-dom0
+
+exec chpst -b xen-init-dom0 runit-pause
diff --git a/build/fedora/xen-unstable-runit/xenconsoled/run b/build/fedora/xen-unstable-runit/xenconsoled/run
new file mode 100755
index 0000000..7a3ab4e
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/xenconsoled/run
@@ -0,0 +1,10 @@
+#!/bin/sh
+sv check xen-init-dom0 >/dev/null || exit 1
+
+[ ! -d /var/log/xen/console ] && mkdir -p /var/log/xen/console
+
+# In case of failure, allow user to run teardown script
+sleep 5s
+
+# --log=[none|guest|hv|all]
+exec /opt/xen-unstable/sbin/xenconsoled -i --log=none
diff --git a/build/fedora/xen-unstable-runit/xenstored/run b/build/fedora/xen-unstable-runit/xenstored/run
new file mode 100755
index 0000000..42e5e41
--- /dev/null
+++ b/build/fedora/xen-unstable-runit/xenstored/run
@@ -0,0 +1,20 @@
+#!/bin/sh
+[ ! -d /var/run/xen ] && mkdir -p /var/run/xen
+[ ! -d /var/run/xenstored ] && mkdir -p /var/run/xenstored
+[ ! -d /var/log/xen ] && mkdir -p /var/log/xen
+[ ! -d /var/lib/xen ] && mkdir -p /var/lib/xen
+[ ! -d /var/lib/xen/dump ] && mkdir -p /var/lib/xen/dump
+[ ! -d /var/lib/xen/xenpaging ] && mkdir -p /var/lib/xen/paging
+[ ! -d /var/lib/xenstored ] && mkdir -p /var/lib/xenstored
+modprobe -q xen-evtchn || exit 1
+modprobe -q xen-gntdev || exit 1
+modprobe -q xen-gntalloc || exit 1
+mountpoint -q /proc/xen || mount -t xenfs xenfs /proc/xen
+mountpoint -q /var/lib/xenstored || mount -t tmpfs xenstored /var/lib/xenstored
+grep -q "control_d" /proc/xen/capabilities || exit 1
+
+# In case of failure, allow user to run teardown script
+sleep 5s
+
+# Use `--trace-file /var/log/xen/xenstored-trace.log` for logs
+exec /opt/xen-unstable/sbin/xenstored --no-fork


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-08-21  7:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  7:17 [stage1-xen (RFC) PATCH 00/10] Add Fedora support Rajiv Ranganath
2017-08-21  7:17 ` [stage1-xen (RFC) PATCH 01/10] .gitignore: Add Rajiv Ranganath
2017-08-21  7:17 ` [stage1-xen (RFC) PATCH 02/10] build/fedora: Add `buildroot-README.md` Rajiv Ranganath
2017-08-21  8:30   ` M A Young
2017-08-24  0:22   ` Stefano Stabellini
2017-08-21  7:17 ` [stage1-xen (RFC) PATCH 03/10] build/fedora: Add `buildroot-Dockerfile` Rajiv Ranganath
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 04/10] build/fedora: Add `run` Rajiv Ranganath
2017-08-24  0:21   ` Stefano Stabellini
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 05/10] build/fedora: Add `source_path.sh` Rajiv Ranganath
2017-08-21  7:18 ` Rajiv Ranganath [this message]
2017-08-24  0:51   ` [stage1-xen (RFC) PATCH 06/10] build/fedora: Add `xen-unstable-runit/*` scripts Stefano Stabellini
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 07/10] .circleci/config.yml: Add Rajiv Ranganath
2017-08-24  0:24   ` Stefano Stabellini
2017-08-24 10:39     ` Rajiv Ranganath
2017-08-25  0:56       ` Stefano Stabellini
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 08/10] README.md: Add CircleCI badge Rajiv Ranganath
2017-08-24  0:24   ` Stefano Stabellini
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 09/10] build/fedora: Add `RUNNING_STAGE1_XEN.md` Rajiv Ranganath
2017-08-24  0:37   ` Stefano Stabellini
2017-08-21  7:18 ` [stage1-xen (RFC) PATCH 10/10] BUILDING.md: Add Fedora instructions Rajiv Ranganath
2017-08-24  0:42   ` Stefano Stabellini
2017-08-24  0:01 ` [stage1-xen (RFC) PATCH 00/10] Add Fedora support Stefano Stabellini

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=20170821071817.65172.6416.stgit@rajivs-macbook-pro.local \
    --to=rajiv.ranganath@atihita.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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 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).