On Thu, Oct 26, 2006 at 03:22:13PM +1000, Tony Breeds wrote:
> Hello Ewan,
> I was testing out the current xen-unstable on x86 and found that
> with automake 1.9 I needed the floowing patch to have the generated Makefile
> work.
>
> Otherwise I was getting variations on
>
> BR_URL =
> htt
On Wed, Oct 25, 2006 at 10:38:46AM -0400, Jimi Xenidis wrote:
> this just works in my local disk environment and I'm pretty sure othe
> local disk environments work as well.
> Hollis, Tony are you able to create domain that have net access?
Yes. On my JS20 I was able to create a domU (called t
Hi Tony,
Thanks for the info. I followed your steps and basically got the same
thing:
1. I got rid of the line : vif = [ '' ] , created a domain (id=8)
2. I issued xm network-attach 8, Here is the output
cso83:~ # xm network-attach 8
Error: Device 1 (vif) could not be connected. Backend device
On Thu, Oct 26, 2006 at 02:11:54AM -0400, Hao Yu wrote:
> Hi Tony,
>
> Thanks for the info. I followed your steps and basically got the same
> thing:
Hi Hao,
You're up late (or early).
> 1. I got rid of the line : vif = [ '' ] , created a domain (id=8)
>
> 2. I issued xm network-attach
Thanks Tony, I shall go to bed soon. Here are the info you asked.
(See attached file: 2006-10-26-domU-dmesg.out)(See attached file:
xenstore-ls.out)
Regards,
Hao
Hao Yu
Commercial Scale Out
IBM T.J. Watson Research Center
1101 Kitchawan Rd/Route 134, Rm 36-019
Yorktown Heights, NY 10598-0218
91
On Wed, Oct 25, 2006 at 09:02:29PM -0400, Maria Butrico wrote:
> I thought we diligently updated this file by hand. We edit it all the
> time. The comment is flat out wrong.
The file is in fact automatically generated. Nobody should ever edit a
defconfig by hand, since the Kconfig logic that
Why did you change the date?
Jimi did not change the date by hand. The Kconfig logic discussed
above
did so, and I believe that the myriad benefits of that logic outweigh
the cost of resolving the trivial merge conflict caused by the date.
Perhaps we can investigate removing the date insert
Remove timestamp from xen_maple_defconfig to reduce merge conflicts in
client trees. Generated with:
KCONFIG_NOTIMESTAMP=1 make xen_maple_defconfig
Thanks to Segher Boessenkool for the suggestion.
Signed-off-by: Amos Waterland <[EMAIL PROTECTED]>
---
xen_maple_defconfig |1 -
1 file cha
On Oct 25, 2006, at 9:02 PM, Maria Butrico wrote:
I want to quibble about this change.
First this is not an
# Automatically generated make config: don't edit
Yes it is.
I thought we diligently updated this file by hand. We edit it all
the time. The comment is flat out wrong. (I know
Doesn't this require that everybody build like this all the time? In
that case, I'm not sure a one-time checkin makes sense.
--
Hollis Blanchard
IBM Linux Technology Center
On Thu, 2006-10-26 at 12:28 -0400, Amos Waterland wrote:
> Remove timestamp from xen_maple_defconfig to reduce merge confli
Doesn't this require that everybody build like this all the time? In
that case, I'm not sure a one-time checkin makes sense.
Yes. You can edit your Makefile's to always include it, if
you want.
Segher
___
Xen-ppc-devel mailing list
Xen-ppc-devel@l
Enable SMP and IPI support, including remote function invocation.
There are a number of subtle issues fixed in this patch. I believe it
is a candidate for merging.
I have tested this extensively on JS21 and model 884221X JS20 blades,
and to a degree on Maple. I would appreciate further testing
We have a particular JS20 blade, named kpblade11, on which we have to
flash a downlevel SLOF, and on which when Linux runs it reports only one CPU.
Current tip of tree Xen/PPC appears to find the missing processor in
some capacity, as the following is printed during boot.
Note that this is vanill
13 matches
Mail list logo
