From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Rousse Subject: Re: troubles using network boot with HVM guest Date: Wed, 06 Jun 2007 17:27:13 +0200 Message-ID: <4666D251.7030906@inria.fr> References: <4664051B.7050900@inria.fr> <20070604125100.GA12800@york.uk.xensource.com> <46640C91.6010606@inria.fr> <20070606103400.GA21901@york.uk.xensource.com> <4666C5E3.209@inria.fr> <20070606150715.GB21901@york.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20070606150715.GB21901@york.uk.xensource.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: Tim Deegan Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Tim Deegan a =E9crit : > At 16:34 +0200 on 06 Jun (1181147651), Guillaume Rousse wrote: >> Tim Deegan a =E9crit : >>> Can you check the DHCP server settings, and whether your proxy is doi= ng >>> something wierd to the packet?=20 >> I did check with a real host, it worked perfectly. >=20 > Was your test host using an rtl8139 and etherboot? Did grub work on it= ? Now, it was standard PXE. I never had to use anything else sofar, hence my current troubles. >> But you find the >> issue: the server was only answering PXE requests, whereas the emulate= d >> network card send an etherboot one.Just adding etherboot configuration >> on the server was enough to provide a functional answer. >=20 > Great! > =20 >> I was able to make the virtual domain download a grub stage2 built for >> rtl839. As I was not able to rebuild grub myself (compilation errors),= I >> used this one >> http://cvs.mandriva.com/cgi-bin/viewvc.cgi/gi/tools/i386/netboot/rtl81= 39/?pathrev=3DMDK-2006_0-update >> >> Once loaded, the virtual host send a new DHCP request, and then ignore >> the answer once again, despite the fact than the next-server field is >> correct. According to my knowledge, it should finish the DHCP >> transaction, then requires /boot/grub/menu.list from the tftp server. >=20 > Aiee! Grub will be using its own driver and IP stack, so presumably ha= s > other restrictions on what it thinks a DHCP response should look like. > Have you considered using pxelinux? :) You know what ? I was persuaded than pxelinux was not compatible with etherboot, just from the only PXE documentation I had... I just changed my configuration to use my already existing pxelinux configuration, and everything works like a charm... Thanks a lot for your suggestion :) --=20 Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62