From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew D. Ball" Subject: Re: Xen PXE solution Date: Mon, 16 Oct 2006 12:23:34 -0400 Message-ID: <1161015814.21233.39.camel@localhost> References: <1154357859.9876.14.camel@localhost.localdomain> <452A380F.BA47.005A.0@novell.com> Reply-To: aball@us.ibm.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <452A380F.BA47.005A.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gregory Haskins , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Good morning. Here's how far I got before I was swamped by other work: -- generated a ROM image for the pcnet32 driver from etherboot. (was before the realtek device) -- loaded the image in different parts of memory that is scanned by the ROMBIOS for expansion ROMS -- Noticed what was probably memory corruption errors preventing the PXE ROM from loading and running This dropped down to the bottom of my priorities, as it's possible to get the same functionality with etherboot as a virtual ISO image instead of an expansion ROM. This would still be useful as an expansion ROM though, IMHO. The most important work to be done that I can think of before this can work is to clearly document which parts of memory are occupied by what firmware for HVM domU's and proceed with troubleshooting the memory corruption. If you'd like, we can set up a wiki page to work on this. Hope this helps. Andrew On Mon, 2006-10-09 at 11:57 -0400, Gregory Haskins wrote: > >>> On Mon, Jul 31, 2006 at 10:57 AM, in message > <1154357859.9876.14.camel@localhost.localdomain>, "Andrew D. Ball" > wrote: > > Greetings. > > > > I've been asked to work on a PXE solution for booting Xen domU's from a > > network, and would like some feedback and any help anyone is willing to > > provide. > > Hi Andrew, > I am just wondering what the status of this project is? I have the need for this type of functionality as well. We could possibly collaborate on this effort if work still remains to be done. > > -Greg Haskins > Novell >