From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: xen_changeset : Mon Oct 3 05:26:29 2005 +0100 f22fba673196 updates 4k and 8 k kernel stacks
Date: Mon, 03 Oct 2005 12:54:00 -0400 [thread overview]
Message-ID: <1128358440.16758.92.camel@pluto.linsolutions.com> (raw)
changeset: 7157:f22fba673196
#########################################
FC4 dom0, Tyan 2462 SMP, 4k kernel stack
#########################################
xm shutdown does not work at all, always get the d flag , that d flag
also seems to be the stopper for xm destroy as well.
I have yet to be able to destroy a domain with the d flag.
Unable to create SMP guests
ethtool for e1000 as eth0 breaks after xend starts, don't know if this
ever has worked.
#########################################
FC4 dom0, Tyan 2462 SMP, 8k kernel stack
#########################################
smp guests get created with no issues
ethtool for e1000 as eth0 breaks after xend starts
xm shutdown works
Now at this point I don't think it offers ant more value testing 4k
stacks, if someone make a change that deems such testing worthwhile
please do let me know. I have redone my test box to be able to flip
quickly between the two, lots of stuff has to be recompiled for the
specific kernel stack.
I am also planning on working out some bridge testing scenarios.
I have 3 nics available on my 2.X and unstable test boxes.
Be more than happy to spin up some specific topologies if anyone is
interested.
Right now I am in process of trying to get a EBGP/OSPF quagga setup in
place for some network testing as well. Anything along these lines I
would be willing to toy with as well.
Regards,
Ted
next reply other threads:[~2005-10-03 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 16:54 Ted Kaczmarek [this message]
2005-10-04 7:21 ` xen_changeset : Mon Oct 3 05:26:29 2005 +0100 f22fba673196 updates 4k and 8 k kernel stacks Ewan Mellor
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=1128358440.16758.92.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--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.