This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH] Virtual console driver on /dev/xvc0

On Fri, 2006-08-04 at 08:55 +0100, Keir Fraser wrote:
> On 4 Aug 2006, at 00:07, Amos Waterland wrote:
> > The below is the least invasive approach I can find, and works well on
> > my PPC64 blades: I can boot the exact same kernel on bare hardware and
> > as a dom0.  I am sure there will be distro concerns (such as
> > /etc/inittab and /etc/securetty), but I'd like to get the ball rolling
> > with this initial submission.
> >
> > Note that you have to put `xencons=xvc0' in your Linux .config, and run
> > `mknod /dev/xvc0 c 232 0' in your rootfs.
> >
> > Signed-off-by: Amos Waterland <apw@xxxxxxxxxx>
> How did you pick the major? Is there a process for allocating one (I 
> think our bklock-device major is now official)? Could we use a more 
> dynamic (e.g., udev-based) scheme to avoid locking down 1/256th of the 
> 8-bit major space for this?

The instructions for getting a major are available at
http://www.lanana.org/docs/device-list/instructions.txt and the official
list of majors/minors is at

char major 232 is already taken for biometrics.  There's no reason that
we shouldn't be able to get a minor (or a couple, if it makes more sense
to have more than one xvc device in some case) char devices in the
low-density serial console region (char major 204)


Xen-devel mailing list