[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Xen network for mirage


  • To: Gareth Rushgrove <gareth@xxxxxxxxxxxxxxxxx>
  • From: Dave Scott <Dave.Scott@xxxxxxxxxx>
  • Date: Sun, 6 Sep 2015 13:26:59 +0000
  • Accept-language: en-GB, en-US
  • Cc: mirageos-devel <MirageOS-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 06 Sep 2015 13:27:09 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
  • Thread-index: AQHQ6JTZgOrzZ/fm50WJz6m2puNzXp4vXLmA
  • Thread-topic: [MirageOS-devel] Xen network for mirage

> On 6 Sep 2015, at 12:10, Gareth Rushgrove <gareth@xxxxxxxxxxxxxxxxx> wrote:
> 
> Hi
> 
> I have a vague plan of automating the build-out of a box to run many
> unikernels, probably on Packet*.
> 
> Does anyone have an up-to-date set of steps for installing Xen,
> including with a suitable network setup and that doesn't require
> physical access?
> 
> Asking here as a somewhat brief look around turns up instructutions
> that require you to kill the network while you're connected, ignore
> the network setup, use a very old version of Xen or use a very old
> version of an operating system.
> 
> I've heard rumours of the box that runs the the https://mirage.io/
> site. If someone has the installation steps documented for that those
> would be perfect.

Iâm experimenting with a CentOS 7 box (from bytemark). So far Iâve had to:

[Disclaimer, this is from memory and my bash history. I guess I should write 
this down somewhere!]

- install bytemark's canned CentOS 7 image

- install the Xen4CentOS7 repo:

yum install centos-release-xen

- install Xen-4.4

yum --enablerepo=virt-xen-44-testing install xen

- fix my /etc/default/grub:

diff -u /root/grub.orig /etc/default/grub 
--- /root/grub.orig     2015-09-06 13:34:04.000000000 +0100
+++ /etc/default/grub   2015-09-06 13:31:43.000000000 +0100
@@ -8,5 +8,5 @@
 ## Serial console
 GRUB_TERMINAL="console serial"
 GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no 
--stop=1 --port=0x3f8"
-GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen nomodeset"
+GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen nomodeset 
biosdevname=0 net.ifnames=0 rd.auto"
 GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 
console=com1,tty loglvl=all guest_loglvl=allâ

In particular the lack of ârd.autoâ broke the boot because root is on a /dev/md 
device.

- regenerate the grub.cfg

grub2-mkconfig -o /boot/grub2/grub.cfg

- create a bridge config in /etc/sysconfig/network-scripts. I copied the 
fragments here: 
http://wiki.xenproject.org/wiki/Network_Configuration_Examples_(Xen_4.1%2B). 
Note that the âservice network restartâ didnât manage to cleanly erase the old 
configuration and I ended up with a dodgy routing table. It was better to run 
âifdown eth0; ifup xenbr0; ifup eth0â myself.

At this point my box is able to run domains with bridged networking. Iâm 
planning on building and installing the RPMs for the xapi toolstack (as used in 
XenServer) and setting up jitsu next.

Cheers,
Dave


> 
> Cheers
> 
> Gareth
> 
> * https://www.packet.net/. API provisioned bare metal machines with
> the relevant virtualisation support, 16GB for about Â180 a month (and
> billed by the hour).
> 
> -- 
> Gareth Rushgrove
> @garethr
> 
> devopsweekly.com
> morethanseven.net
> garethrushgrove.com
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.