From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Tim Deegan <Tim.Deegan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: troubles using network boot with HVM guest
Date: Wed, 06 Jun 2007 17:27:13 +0200 [thread overview]
Message-ID: <4666D251.7030906@inria.fr> (raw)
In-Reply-To: <20070606150715.GB21901@york.uk.xensource.com>
Tim Deegan a écrit :
> At 16:34 +0200 on 06 Jun (1181147651), Guillaume Rousse wrote:
>> Tim Deegan a écrit :
>>> Can you check the DHCP server settings, and whether your proxy is doing
>>> something wierd to the packet?
>> I did check with a real host, it worked perfectly.
>
> 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 emulated
>> network card send an etherboot one.Just adding etherboot configuration
>> on the server was enough to provide a functional answer.
>
> Great!
>
>> 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/rtl8139/?pathrev=MDK-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.
>
> Aiee! Grub will be using its own driver and IP stack, so presumably has
> 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 :)
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
next prev parent reply other threads:[~2007-06-06 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:27 troubles using network boot with HVM guest Guillaume Rousse
2007-06-04 12:51 ` Tim Deegan
2007-06-04 12:58 ` Guillaume Rousse
2007-06-06 10:34 ` Tim Deegan
2007-06-06 14:34 ` Guillaume Rousse
2007-06-06 15:07 ` Tim Deegan
2007-06-06 15:27 ` Guillaume Rousse [this message]
2007-06-04 15:20 ` Anthony Liguori
2007-06-04 16:12 ` Guillaume Rousse
2007-06-04 18:14 ` Anthony Liguori
2007-06-04 19:36 ` Guillaume Rousse
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=4666D251.7030906@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=Tim.Deegan@xensource.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.