TurnKey Linux Virtual Appliance Library

Announcing TurnKey Xen optimized builds

Xen LogoAs we mentioned before, making TurnKey easy to deploy on as many public and private clouds is an important goal for the project.

Recently we announced TurnKey optimized builds in a number of new formats, which brings the supported list to: ISO, VMDK, OVF, Amazon EC2, OpenStack and OpenVZ.

I'm pleased to announce that we have just added Xen to the list of optimized builds. They are hot out of the build farm and available for immediate download.

You can get them from the Download link on the appliance pages.

Pre-seeding / Default passwords

The Xen images are mainly built for hosting providers who utilize the Xen Hypervisor.

Because Xen builds are used in headless deployments (without an interactive console), they include an inithook which preseeds default values and passwords.

/usr/lib/inithooks/firstboot.d/29preseed

MASTERPASS=turnkey

cat>$INITHOOKS_CONF<<EOF
export ROOT_PASS=$MASTERPASS
export DB_PASS=$MASTERPASS
export APP_PASS=$MASTERPASS
export APP_EMAIL=admin@example.com
export APP_DOMAIN=DEFAULT
export HUB_APIKEY=SKIP
export SEC_UPDATES=FORCE
EOF

You will most likely want to have your provisioning system to override the defaults by creating /etc/inithooks.conf.

Note that inithooks.conf will be blanked out once its no longer needed for security. You should also make sure that inithooks.conf includes *ALL* of the variables, otherwise the inithook system will turn on interactivity.

If you cannot support preseeding, the alternative is to have the user execute turnkey-init on first login.

Muchas Gracias to Marc from GigaTux (an official TurnKey partner) for testing the Xen images and providing feedback!
 

You can get future posts delivered by email or good old-fashioned RSS.
TurnKey also has a presence on Google+, Twitter and Facebook.

Comments

Looking forward to testing it out.

I have Xenserver running, but minimal knowledge of where to get started. I'll learn something one way or the other today.


Jeremy's picture

A Xen server or XenServer?

Xen is open source hypervisoer tech as opposed to XenServer which is a proprietry hypervisor OS (built on top of Xen technology). These are Xen images - not XenServer ones...

According to this post the Xen images are not directly compatible with XenServer (although there is mention of how they can be converted).

BTW How you going Rik? Long time - no see mate! Hope you're well. :)

DTC .debs now available

If anyone happens to be using DTC to provision Xen VPSs, I have now made compatible .debs available at http://deb.gigatux.com/

Alon Swartz's picture

Getting up and running with Xen TurnKey images

If you need some pointers on getting Xen up and running with TurnKey, Marc has provided steps and tips here. Thanks Marc!

Xen Builds work with PRGMR.Com VPS

For anyone intrested, I was able to get the Xen builds to work with PRGMR.Com VPS hosting. If there is any one out there what would like a howto, I'll post how I got it to work.

Xen images compatible with KVM running on CentOS?

Can I use Xen images on KVM running on CentOS? Are they compatible? If not, is it possible to convert Xen images to KVM compatible ones like qcow2 or raw?

Jeremy's picture

No Xen and KVM are not compatible

But AFAIK the 'standard' VM images (either of them IIRC) can be used with KVM and require minimal tweaking. But personally I have never done it so YMMV.

I generally just use the OVZ images (on ProxmoxVE) and whenever I have wanted a KVM machine (Proxmox supports both OVZ & KVM) then I have just installed from ISO (which I imagine is a 3rd option if you get stuck...)

XenServer support

XenServer has become open-source. Are you planning to support it from now?

This would be really appreciated, since I could make the 12.0 VMs work on XenServer 6.1, but I simply cannot get the 12.1 VMs work on it. Unfortunatelly, the old 12.0 VMs cannot be downloaded any more...

For those who whish to install 12.0 images on XenServer 6.1/6.2, check out my tutorial.

Jeremy's picture

I can't speak for the devs

But now it's open source then perhaps! :) I have just lodged a feature request on the TKL Dev Tracker.

Support for xen paravirtualization on solusvm

Hello,

I was wondering if the xen tarballs of all these turnkeys would work on a solusvm xen environment? We currently use solusvm to create xen paravirtualized vms and xen fully virtualized vms. I think these tarballs could be used in our paravirtualized vms, but i am not sure. If anyone can answer this question it would be a huge help.

Thanks,

Muneer

Jeremy's picture

TBH I have no idea...

Your question prompted me to a quick bit of research and I note that SolusVM also supports OpenVZ and KVM. I know that these VM technologies are irrelevant to your question directly but I figured I'd add this quickly as an FYI:

TurnKey provides OpenVZ templates which should work fine under SolusVM. I haven't had confirmation of that - but they work fine on ProxmoxVE and vanilla OVZ though so I have no reason to think that they wouldn't work under SolusVM.

TurnKey also provides a VMDK build (which is a disk image primarily designed for consumer/desktop grade virtualisation such as VMware player and VirtualBox). This build works great under KVM as is (recent versions of KVM support VMDK disk images OOTB). Again I haven't confirmed this on SolusVM itself, but works under vanilla QEMU/KVM and ProxmoxVE.

But back to your specific question:

The SolusVM Xen Docs suggest that the TKL Xen templates may work, although it states that there is a strict naming format which I doubt the current TKL Xem templates provide. FWIW TurnKey is built on Debian so renaming them to the specific required format would be a required first step (although obviously still no guarantee that they'd work). For example you would probably rename the 64 bit Xen LAMP appliance from:

turnkey-lamp-13.0-wheezy-amd64-xen.tar.bz2

to something like:

debian-7-x86_64-TKL_LAMP.tar.bz2

If SolusVM still doesn't see it, then perhaps try renaming the bz2 to gz (so long as your server supports untarring bz2 compression then it shouldn't matter that the extension does not match the compression - Linux is good like that! :)

If that still doesn't work then you could still always install from ISO.

Regardless, it'd be great to hear how you go.

Post new comment

The content of this field is kept private and will not be shown publicly. If you have a Gravatar account, used to display your avatar.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <strike> <caption>

More information about formatting options

Leave this field empty. It's part of a security mechanism.
(Dear spammers: moderators are notified of all new posts. Spam is deleted immediately)