From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: Re: pxe support
Date: Thu, 18 Jan 2007 11:45:03 +0100 [thread overview]
Message-ID: <200701181145.03863.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20070118090144.GE18763@york.uk.xensource.com>
On Thursday 18 January 2007 10:01, Tim Deegan wrote:
> At 13:15 -0600 on 17 Jan (1169039714), Anthony Liguori wrote:
> > Sven Oehme wrote:
> > >Hi,
> > >
> > >i saw a bunch of patches from Anthony adding pxe support to qemu. will
> > >that end in xen at some point , or is it already in ?
> > >i searched in the archives and also the source but couldn't find
> > >anything ..
> >
> > It should be there. The QEMU patches were inspired by Tim's Xen
> > patches. I've seen a few commits that have disabled/enabled Option ROM
> > loading which would prevent the etherboot ROM from getting loaded.
> >
> > Should PXE booting work ATM Tim?
>
> Works for me in -unstable. Give the guest a vif, and choose boot=n.
There's no explicit PXE support needed in Xen. All what you need is a
bootmanager, which passes a multiboot header to Xen. That's all.
PXE bootmanagers which support multiboot are PXELinux and PXEGrub
(I'm aware of these two. I don't know if there are more.).
Both work fine for me. I use them regularly for development/testing.
It makes more fun to build a kernel and boot it from network. It saves
me a double reboot.
Christoph
next prev parent reply other threads:[~2007-01-18 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 18:46 pxe support Sven Oehme
2007-01-17 19:15 ` Anthony Liguori
2007-01-18 9:01 ` Tim Deegan
2007-01-18 9:22 ` Sven Oehme
2007-01-18 9:35 ` Tim Deegan
2007-01-18 9:38 ` Sven Oehme
2007-01-18 10:01 ` Tim Deegan
2007-01-18 10:21 ` Sven Oehme
2007-01-18 22:14 ` Ian Pratt
2007-01-22 9:55 ` Gerd Hoffmann
2007-01-24 15:53 ` Gerd Hoffmann
2007-01-24 15:57 ` Sven Oehme
2007-01-18 10:45 ` Christoph Egger [this message]
2007-01-18 11:05 ` Sven Oehme
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=200701181145.03863.Christoph.Egger@amd.com \
--to=christoph.egger@amd.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.