From: Ben Thomas <bthomas@virtualiron.com>
To: Henning Sprang <henning_sprang@gmx.de>
Cc: xen-devel@lists.xensource.com, "Andrew D. Ball" <aball@us.ibm.com>
Subject: Re: Xen PXE solution
Date: Tue, 15 Aug 2006 14:46:03 -0400 [thread overview]
Message-ID: <44E2166B.6080408@virtualiron.com> (raw)
In-Reply-To: <5bb00b3f0608151114r2a128b48m8c0361cc848fc6b9@mail.gmail.com>
Hi Henning,
It's been a little while, and my recollection is rusty. I do
know that we ended up fixing some opcode emulation when
getting the PXE booting to work. I was pretty sure that we
had posted that to the xen-devel list, but again I plead
a faulty memory on the specifics.
I do know that we are constantly (hundreds to thousands of
times per day) booting many, many xen-based systems via PXE
for both VMX and SVM systems. Currently, we're using the
pcnet32 support. As Ian will (or probably already did) point
out, it's probably worthwhile to move forward.
I'd be happy to give you more specifics on what we're doing
to get PXE booted. I doubt that the entire list cares, so
please send me an email if you're interested.
-b
Henning Sprang wrote:
> Hi Ben,
>
> On 8/1/06, Ben Thomas <ben@virtualiron.com> wrote:
>
>> [...]
>> For what it's worth, we've been using a PXE solution based upon
>> etherboot.
>> It's effectively a floppy-like boot image that works quite well. My
>> memory
>> is that there were some instruction decode/emulation issues on VMX,
>> but that
>> we've submitted all of those patches to this list. I believe that they
>> were
>> incorporated into xen-unstable.
>
>
> This is probably more for the xen-users list, but here is the only
> post I found about somebody doing etherboot with xen hvm, which I am
> trying currently without luck.
> Does your mail mean that with xen-testing at the moment my efforts to
> try booting xen hvm with an etherboot image and pxe cannot succeed?
>
> When booting from the etherboot iso, I get
> "Loading pcnet32.zli....Ready"
>
> but no dhcp requests or anything happens. xm dmesg's last lines are:
>
> (XEN) (GUEST: 60) Booting from CD-Rom...
> (XEN) (GUEST: 60) Unknown opcode at 0F60:0E8A=0x1048A
> (XEN) (GUEST: 60) Halt called from %eip 0xD39D1
>
> No interesting info xend-debug.log
>
> I'd be a candidate for testing xen pxe solutions, because I really
> want to use it.
>
> Henning
--
------------------------------------------------------------------------
Ben Thomas Virtual Iron Software
bthomas@virtualiron.com Tower 1, Floor 2
978-849-1214 900 Chelmsford Street
Lowell, MA 01851
next prev parent reply other threads:[~2006-08-15 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:57 Xen PXE solution Andrew D. Ball
2006-08-01 13:20 ` Ben Thomas
2006-08-15 18:14 ` Henning Sprang
2006-08-15 18:46 ` Ben Thomas [this message]
2006-08-02 12:42 ` Jeremy Katz
2006-08-02 13:54 ` Andrew D. Ball
[not found] ` <452A380F.BA47.005A.0@novell.com>
2006-10-16 16:23 ` Andrew D. Ball
[not found] ` <a8a6bd980610161046y426cdf0bn64c8181c45fae9dd@mail.gmail.com>
2006-10-16 19:33 ` Andrew D. Ball
2006-10-16 19:47 ` Ben Thomas
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 11:34 Ian Pratt
2006-08-15 18:24 Ian Pratt
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=44E2166B.6080408@virtualiron.com \
--to=bthomas@virtualiron.com \
--cc=aball@us.ibm.com \
--cc=henning_sprang@gmx.de \
--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.