From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Daniel Stodden <daniel.stodden@citrix.com>
Subject: Re: What is the state of blktap2?
Date: Fri, 22 Jan 2010 17:12:32 -0500 [thread overview]
Message-ID: <20100122221231.GA32286@phenom.dumpdata.com> (raw)
In-Reply-To: <1264198204.20158.22.camel@moss-terrapins.epoch.ncsc.mil>
> So I tried getting the pvops kernel working and it works fine as a
> standard Linux kernel but when I try to run it on top of Xen once I get
> to Linux I don't have any keyboard input. I'm using the grub conf on the
That smells like inittab..
> pvops page so that part of the config should be correct. I'm going to
> try to update to the latest version of xen-unstable and of the pvops
> tree to see if that fixes anything.
Here is a little script that fixes most common problems.
grep -q xenfs /etc/fstab || echo "xenfs /proc/xen xenfs defaults 0 0" >> /etc/fstab
if grep -q ata_piix /etc/modprobe.conf ; then
NR=`cat /etc/modprobe.conf | grep scsi | wc -l`
grep -q pata_oldpiix /etc/modprobe.conf || echo "alias scsi_hostadapter$NR pata_oldpiix" >> /etc/modprobe.conf
fi
grep -q hvc /etc/inittab || echo "co:2345:respawn:/sbin/agetty hvc0 9600 vt100-nav" >> /etc/inittab
grep -q hvc0 /etc/securetty || echo "hvc0" >> /etc/securetty
next prev parent reply other threads:[~2010-01-22 22:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 22:27 What is the state of blktap2? David P. Quigley
2010-01-21 22:38 ` Pasi Kärkkäinen
2010-01-21 22:46 ` David P. Quigley
2010-01-21 22:55 ` Pasi Kärkkäinen
2010-01-21 22:59 ` Pasi Kärkkäinen
2010-01-21 23:09 ` David P. Quigley
2010-01-21 23:13 ` David P. Quigley
2010-01-22 7:14 ` Pasi Kärkkäinen
2010-01-22 18:43 ` Jeremy Fitzhardinge
2010-01-22 19:41 ` David P. Quigley
2010-01-21 23:00 ` David P. Quigley
2010-01-21 22:54 ` Daniel Stodden
2010-01-21 22:52 ` David P. Quigley
2010-01-22 22:10 ` David P. Quigley
2010-01-22 22:12 ` Konrad Rzeszutek Wilk [this message]
2010-01-22 22:22 ` David P. Quigley
2010-01-22 22:43 ` Konrad Rzeszutek Wilk
2010-01-25 23:23 ` David P. Quigley
2010-01-26 7:10 ` Pasi Kärkkäinen
2010-01-26 16:32 ` David P. Quigley
2010-01-26 16:47 ` Pasi Kärkkäinen
2010-01-26 16:49 ` David P. Quigley
2010-01-26 17:06 ` Pasi Kärkkäinen
2010-01-26 14:42 ` Konrad Rzeszutek Wilk
2010-01-26 16:42 ` David P. Quigley
2010-01-26 16:57 ` Konrad Rzeszutek Wilk
2010-01-26 17:46 ` David P. Quigley
2010-01-26 18:19 ` Xen 4.0 + PVOPS + Intel VTD + USB EHCI = BUG() Konrad Rzeszutek Wilk
2010-01-26 18:44 ` David P. Quigley
2010-01-26 19:24 ` David P. Quigley
2010-01-26 19:30 ` David P. Quigley
2010-01-26 19:46 ` Pasi Kärkkäinen
2010-01-26 20:21 ` David P. Quigley
2010-01-27 2:49 ` Han, Weidong
2010-01-27 18:48 ` David P. Quigley
2010-01-28 1:50 ` Han, Weidong
2010-01-28 16:10 ` David P. Quigley
2010-01-30 13:50 ` Han, Weidong
2010-02-01 21:35 ` David P. Quigley
2010-02-03 3:08 ` Weidong Han
2010-02-03 16:38 ` David P. Quigley
2010-02-04 1:59 ` Weidong Han
2010-02-04 16:05 ` David P. Quigley
2010-01-27 9:08 ` Sander Eikelenboom
2010-01-27 20:22 ` David P. Quigley
2010-01-28 9:24 ` Pasi Kärkkäinen
2010-01-28 14:49 ` David P. Quigley
2010-01-28 15:02 ` Pasi Kärkkäinen
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=20100122221231.GA32286@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=daniel.stodden@citrix.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=xen-devel@lists.xensource.com \
/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.