From: Jeremy Fitzhardinge <jeremy@goop.org>
To: bderzhavets@yahoo.com
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Booting up the most recent 2.6.29-rc3 (pv_ops Dom0 support) under Xen Unstable on Intel SATA (AHCI) box
Date: Thu, 05 Feb 2009 22:54:11 -0800 [thread overview]
Message-ID: <498BDE93.6020505@goop.org> (raw)
In-Reply-To: <393646.71982.qm@web56106.mail.re3.yahoo.com>
Boris Derzhavets wrote:
> Build 2.6.29-rc3 with the most recent change set and load under Xen
> Unstable
> Logged into Dom0.
> Was able to load F10 PV DomU via prepared image.
> DomU obtained IP (192.168.1.38) via DHCP .
> Opened ssh connection to Dom0 192.168.1.34 (Ubuntu 8.10 Server)
>
> LAN is still unavailable for both DomU & Dom0.
>
So you're saying that you got internal host<->guest networking going,
but external networking fails.
What's your ethernet hardware? Does it fail to probe, or does it probe
but not work?
J
next prev parent reply other threads:[~2009-02-06 6:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 1:42 [PATCH 2/3] xen: make direct versions of irq_enable/disable/save/restore to common code Jeremy Fitzhardinge
2009-01-31 1:42 ` Jeremy Fitzhardinge
2009-02-05 6:31 ` Tejun Heo
2009-02-05 15:00 ` Ingo Molnar
2009-02-05 15:00 ` Ingo Molnar
2009-02-05 15:24 ` Booting up the most recent 2.6.29-rc3 (pv_ops Dom0 support) under Xen Unstable on Intel SATA (AHCI) box Boris Derzhavets
2009-02-05 17:13 ` Boris Derzhavets
2009-02-06 6:31 ` Boris Derzhavets
2009-02-06 6:54 ` Jeremy Fitzhardinge [this message]
2009-02-06 12:01 ` Boris Derzhavets
2009-02-06 16:57 ` Jeremy Fitzhardinge
2009-02-06 19:49 ` Boris Derzhavets
2009-02-06 20:08 ` Boris Derzhavets
2009-02-07 9:48 ` Boris Derzhavets
2009-02-05 16:04 ` [PATCH] x86: style fascism for xen assemblies Tejun Heo
2009-02-05 16:57 ` Ingo Molnar
2009-02-05 16:57 ` Ingo Molnar
2009-02-05 17:31 ` Jeremy Fitzhardinge
2009-02-05 17:31 ` Jeremy Fitzhardinge
2009-02-05 17:34 ` Ingo Molnar
2009-02-05 17:34 ` Ingo Molnar
2009-02-05 17:42 ` Tejun Heo
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=498BDE93.6020505@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.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.