lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 14 May 2010 18:11:16 +0200
From:	Soren Hansen <soren@...ux2go.dk>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] A couple of workarounds for Xen based VPS services

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(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ