From: "H. Peter Anvin" <hpa@zytor.com>
To: Tomas Rusnak <linker@korex.sk>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Chris Wedgwood <cw@f00f.org>
Subject: Re: virtio: kvm-62, lilo cannot be installed into virtio device
Date: Thu, 28 Feb 2008 14:38:55 -0800 [thread overview]
Message-ID: <47C737FF.7030402@zytor.com> (raw)
In-Reply-To: <47C67E1D.8050500@korex.sk>
Tomas Rusnak wrote:
> Chris Wedgwood napsal(a):
>> On Thu, Feb 28, 2008 at 10:11:30AM +0100, Tomas Rusnak wrote:
>>
>>>>> Check 'man lilo.conf' under 'disk=' and 'max-partitions='
>>> Thank you for your quick answer, but this doesn't help. After i run
>>> lilo, it give me the same error message.
>> did you try adding 'max-partitions=16' or similar?
>>
>
> Oh yes, i forgot it :)
>
> But max-partitions=16 give you "bad value". After this I try
> max-partitions=7 and run lilo with following result:
>
> Warning: /proc/partitions references Experimental major device 254.
> Warning: /proc/partitions references Experimental major device 254.
> Warning: /proc/partitions references Experimental major device 254.
> Added Gentoo-25 *
> 3 warnings were issued.
>
max-partitions=7 sounds a bit confining, why are we using such a low number?
LILO is one of several reasons why using dynamic major really isn't such
a great idea. We don't have the 8:8 limitation anymore.
-hpa
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-02-28 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 8:40 virtio: kvm-62, lilo cannot be installed into virtio device Tomas Rusnak
2008-02-28 8:54 ` Chris Wedgwood
2008-02-28 9:11 ` Tomas Rusnak
2008-02-28 9:17 ` Chris Wedgwood
2008-02-28 9:25 ` Tomas Rusnak
2008-02-28 9:49 ` Chris Wedgwood
2008-02-28 10:52 ` Tomas Rusnak
2008-02-28 22:38 ` H. Peter Anvin [this message]
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=47C737FF.7030402@zytor.com \
--to=hpa@zytor.com \
--cc=cw@f00f.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linker@korex.sk \
/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