From: Mike Wray <mike.wray@hpl.hp.com>
To: ron minnich <rminnich@lanl.gov>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: more on current pull
Date: Tue, 13 Jul 2004 09:04:11 +0100 [thread overview]
Message-ID: <40F3977B.4040209@hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407121729550.815-100000@maxroach.lanl.gov>
ron minnich wrote:
> xm is really nice, I have to say. Easy to use and debug
>
> I am occasionally seeing my network just go away. For example, I did this:
> xend start
> xm create vmid=1
> telnet 127.1 9601
> (wait a while, admire output stuff, see that it fails to nfsroot since
> I didn't set one up)
> xm destroy 1
> (dom 1 goes away)
> at that point, I've got no eth0.
>
> Should I be using some other eth for the dom0->domN networking? Is there
> something else I'm doing wrong?
>
> thanks
>
> ron
> p.s. are you using your own s-expression library for parsing or ... I'm
> curious because all our cluster tools here use s-expressions for internal
> comms.
>
We're using our own stuff. I wrote s-exp parsers for Python and C that work
with input fed to them in chunks, because we're using asynch i/o.
There's also a Python prettyprinter.
Good to hear someone else uses s-exps.
Mike
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-13 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:33 more on current pull ron minnich
2004-07-12 23:53 ` Ian Pratt
2004-07-13 8:04 ` Mike Wray [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 0:07 James Harper
2004-07-13 0:17 ` Ian Pratt
2004-07-13 0:19 ` Mark Williamson
2004-07-13 0:32 James Harper
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=40F3977B.4040209@hpl.hp.com \
--to=mike.wray@hpl.hp.com \
--cc=rminnich@lanl.gov \
--cc=xen-devel@lists.sourceforge.net \
/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.