From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] Fix network boot whether KVM is enabled or disabled Date: Thu, 23 Aug 2007 14:17:14 -0500 Message-ID: <1187896634.8838.3.camel@squirrel> References: <135cb3c30708101552j6ed4433et5c18f2dfae9cce6d@mail.gmail.com> <46BD2455.2040204@codemonkey.ws> <46C0112C.6020707@qumranet.com> <135cb3c30708131022y55383d65m41b997d2c393036@mail.gmail.com> <1187827822.6545.1.camel@squirrel> <135cb3c30708221852v2de7377t8fefee7e18836e77@mail.gmail.com> <1187837197.8799.47.camel@squirrel> <135cb3c30708231208y4e2d3e87ua4bca7922bf27646@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Avi Kivity To: Chuan-kai Lin Return-path: In-Reply-To: <135cb3c30708231208y4e2d3e87ua4bca7922bf27646-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Thu, 2007-08-23 at 12:08 -0700, Chuan-kai Lin wrote: > On 8/22/07, Anthony Liguori wrote: > > Hrm, it looks like it's the BIOS. Using the BIOS in qemu-0.9.0, -boot n works with > > x86_64 but the bios installed by KVM doesn't work. > > Yeah, it does seem to be the case. I ran a few experiments after > reading your message: kvm-28 and kvm-36 successfully PXE-boots when > using bios.bin from kvm-28, but both fails to PXE-boot when using > bios.bin from kvm-36. > > > Can you try a more recent KVM with -no-kvm? > > Using the patch I posted to the list, I can PXE-boot using the > qemu-system-x86_64 executable from kvm-36 both with and without kvm > kernel module acceleration (provided that I use the bios from kvm-28, > that is). Only with the old BIOS right? The new BIOS provides very limited support for plug-and-play option ROMs. This needs to be indicated in CMOS memory. This morning I made a quick attempt to change the CMOS boot value to 0x04 which would indicate booting from an expansion ROM but that didn't work. There was a patch on qemu-devel recently that might be worth looking at. Regards, Anthony Liguori > Regards, > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/