From: Alex Williamson <alex.williamson@hp.com>
To: Tom Wilkie <tom.wilkie@gmail.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: Re: [Xen-staging] [xen-3.1-testing] xend: Fix use of PIFIsPhysical (takes no arguments).
Date: Wed, 02 May 2007 10:05:15 -0600 [thread overview]
Message-ID: <1178121915.28577.55.camel@bling> (raw)
In-Reply-To: <D8BA9762-E458-4D29-B1E8-2E305A480E24@gmail.com>
On Wed, 2007-05-02 at 16:46 +0100, Tom Wilkie wrote:
> Checked in a fix, and a fix for that fix.
>
> cset number 15001.
Confirmed, Thanks!
> ps did you do something weird like turn the box off, remove a network
> card, and turn it back on? Thats the only way I can think of this
> bug getting triggered... Or this could be related to the networks
> scripts not being run when xend is started.
Removing a NIC from a powered off box doesn't seem so weird to me,
but no, the hardware config did not change at all. The only interesting
config is that one port of a dual port e1000 NIC is hidden from dom0
using "pciback.hide=(0000:01:02.1)". Otherwise it's a standard Debian
Etch system netbooting xen & xenlinux w/ matching tools locally built
and installed. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2007-05-02 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705021410.l42EAuwL011557@latara.uk.xensource.com>
2007-05-02 15:24 ` [Xen-staging] [xen-3.1-testing] xend: Fix use of PIFIsPhysical (takes no arguments) Alex Williamson
2007-05-02 15:29 ` Keir Fraser
2007-05-02 15:46 ` Tom Wilkie
2007-05-02 16:05 ` Alex Williamson [this message]
2007-05-02 16:15 ` Tom Wilkie
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=1178121915.28577.55.camel@bling \
--to=alex.williamson@hp.com \
--cc=keir@xensource.com \
--cc=tom.wilkie@gmail.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.