public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: rongeens7 <rongeens7-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: problem trying to create an Ubuntu dapper VM ...
Date: Tue, 19 Dec 2006 15:18:39 +0200	[thread overview]
Message-ID: <4587E6AF.7000003@qumranet.com> (raw)
In-Reply-To: <1166532502.11038.33.camel@localhost>

rongeens7 wrote:
>
>> This is due to a problem kvm has in processing real mode code on intel 
>> processors.  If you can disable the lilo splashscreen, this may help.
>>     
>
> I wouldn't now how to tackle this, the qemu window dissapears before I
> can do anything.  Anyone knows a way around this ?
>
> I will try to do an install without kvm and then use the resulting image
> with kvm disabled. It is slow to install ubuntu this way though ...
>   

That's the way to proceed at present.  Once you have it installed, you 
can edit lilo.conf and remove the splashscreen, then rerun lilo.



-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      reply	other threads:[~2006-12-19 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 12:27 problem trying to create an Ubuntu dapper VM rongeens7
2006-12-19 12:39 ` Avi Kivity
     [not found]   ` <4587DD7A.1040307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-19 12:48     ` rongeens7
2006-12-19 13:18       ` Avi Kivity [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=4587E6AF.7000003@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=rongeens7-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.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