From: Soren Hansen <soren@linux2go.dk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] A couple of workarounds for Xen based VPS services
Date: Fri, 14 May 2010 18:11:16 +0200 [thread overview]
Message-ID: <cover.1273825543.git.soren@linux2go.dk> (raw)
Several Xen based VPS providers (Rackspace Cloud Servers, Slicehost,
and Amazon EC2 just to name a few) are faced with (at least :) ) two
problems with the current Xen support in the kernel.
Mostly, these problems stem from the fact that there are many different
guest distro's with very different levels of flexibility in terms of
being able to find its root device and in terms of being able to use an
hvc based console.
1. Most, if not all (because that's how the infrastructure has presented
things so far) expect to find their root device on (a partition on)
/dev/sda. However, without a patch to the current kernel, Xen block
devices will turn up as /dev/xvda.
2. Very few of the guest systems know to use hvc0 as its console if its
available. Instead of requiring all the guests to be changed, it's
simpler to just make any attempt to talk to /dev/tty1 actually talk
to hvc0.
These two patches add two new configuratin options that lets you work
around these problems. Enjoy.
Soren Hansen (2):
Allow hvc tty's to pose as vt's
Make the Xen block device prefix configurable
drivers/block/Kconfig | 10 ++++++++++
drivers/block/xen-blkfront.c | 2 +-
drivers/char/Kconfig | 9 ++++++++-
drivers/char/hvc_console.c | 9 +++++++++
4 files changed, 28 insertions(+), 2 deletions(-)
next reply other threads:[~2010-05-14 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 16:11 Soren Hansen [this message]
2010-05-14 16:10 ` [PATCH 1/2] Allow hvc tty's to pose as vt's Soren Hansen
2010-05-14 16:43 ` Alan Cox
2010-05-14 16:50 ` Soren Hansen
2010-05-18 21:26 ` Valdis.Kletnieks
2010-05-14 16:10 ` [PATCH 2/2] Make the Xen block device prefix configurable Soren Hansen
2010-05-14 16:29 ` Randy Dunlap
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=cover.1273825543.git.soren@linux2go.dk \
--to=soren@linux2go.dk \
--cc=linux-kernel@vger.kernel.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.