From: Arthur Enright <aenright@voidnet.us>
To: kvm@vger.kernel.org
Subject: Re: Has anyone tried to run Linux 2.2 under KVM?
Date: Mon, 12 Sep 2011 16:29:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20110912T182502-387@post.gmane.org> (raw)
In-Reply-To: 20080705144420.GA7595@amd.home.annexia.org
Richard W.M. Jones <rjones <at> redhat.com> writes:
>
> On Sat, Jul 05, 2008 at 02:16:34PM +0300, Avi Kivity wrote:
> > Richard W.M. Jones wrote:
> >> I've been trying out RHL6.2 [sic] on KVM 70. This has an ancient
> >> 2.2.14 kernel and generally dates from 1999/2000. However it does run
> >> nicely in 16 MB of RAM which makes it useful for me because I want to
> >> see what happens when we run 100s of KVM instances
> >
> > Can you post a pointer to an iso image somewhere?
>
> I got it from this site, although it's often a little overloaded so
> best to use 'wget' to grab the ISO.
>
> http://archive.download.redhat.com/pub/redhat/linux/6.2/en/iso/i386/
>
> Rich.
>
I'm glad to have found this thread. I was able to install RHL 6.2 using KVM but
I have a quick question. I'm getting the interrupt errors mentioned at the
beginning of the thread during boot time. I know I can append ide=nodma and
re-install grub once the instance is up, but it seems to be taking a ridiculous
amount of time to boot to a point where I can do this.
Is there a way to pass a kernel boot time option with LILO or do I just have to
wait until the box can come up?
I have tried:
linux ide=nodma
linux append="ide=nodma"
at boot but no luck.
Any help would be greatly appreciated!
Thanks,
-Art
next prev parent reply other threads:[~2011-09-12 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 14:51 Has anyone tried to run Linux 2.2 under KVM? Richard W.M. Jones
2008-07-05 11:16 ` Avi Kivity
2008-07-05 14:44 ` Richard W.M. Jones
2011-09-12 16:29 ` Arthur Enright [this message]
2011-09-12 23:27 ` Arthur Enright
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=loom.20110912T182502-387@post.gmane.org \
--to=aenright@voidnet.us \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox