public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, kvm <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Glauber Costa <glommer@redhat.com>
Subject: Re: qemu-kvm: Unsolicited boot from net
Date: Thu, 12 Nov 2009 14:44:21 -0600	[thread overview]
Message-ID: <4AFC73A5.9050207@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091112201157.GA29514@amt.cnet>

Marcelo Tosatti wrote:
>> Looking closer: It's actually still pcbios that is used by my
>> installation - shouldn't this be Seabios now?
>>     
>
> My understanding is that Seabios should get more testing with qemu-kvm
> (other than the cpu hotplug debate). Gleb/Avi would know for sure.
>
> Now whether pcbios option rom supports gpxe properly i don't know, maybe
> that is the root cause for the problem (yes, qemu-kvm loads gpxe and
> attempts to boot from the network first, the above commit only removes
> the annoying multi-second delay).
>
> CC'ing people with some clue.
>   

Yup, that's the problem.  gPXE doesn't think PCBIOS is a PnP bios 
because it isn't.  Therefore it doesn't enable BEV and uses int19 instead.

This isn't a problem with older QEMUs because we only loaded the option 
roms on demand.  We now load them unconditionally.  Of course, that 
meant -boot cdn never really worked correctly.

The only easy solution is moving to SeaBIOS.  I'm surprised qemu-kvm 
hasn't already made the move to be honest.

-- 
Regards,

Anthony Liguori


  reply	other threads:[~2009-11-12 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 12:29 qemu-kvm: Unsolicited boot from net Jan Kiszka
2009-11-12 15:48 ` Marcelo Tosatti
2009-11-12 17:29   ` Jan Kiszka
2009-11-12 20:11     ` Marcelo Tosatti
2009-11-12 20:44       ` Anthony Liguori [this message]
2009-11-13 15:18       ` Gleb Natapov

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=4AFC73A5.9050207@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=glommer@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox