All of lore.kernel.org
 help / color / mirror / Atom feed
From: prasoon jaiswal <prasoon.jaiswal@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: traceroute causes xen reboot from virtual machines
Date: Thu, 27 Jan 2005 13:24:50 +0530	[thread overview]
Message-ID: <b2c12abe05012623545e09ea53@mail.gmail.com> (raw)

Hi all,

I have successfully installed xen 2.0  on debain linux 2.6.10. I have
two methods to get networking done namely routing and bridging. I am
using UML (user mode linux) mode of bridging as the vif-bridge was not
working for me. It was cutting off my Domain 0 connection from
internet when i start the vif-bridge. Anyway this is what i did to set
up the bridge.

    host# brctl addbr br0   

    host# ifconfig eth0 0.0.0.0 promisc up 

    host# ifconfig vif1.0 0.0.0.0 promisc up 

    host# ifconfig br0 192.168.0.1 netmask 255.255.255.0 up 

    host# brctl stp br0 off 

    host# brctl setfd br0 1 

    host# brctl sethello br0 1 

    host# brctl addif br0 eth0 

    host# brctl addif br0 vif1.0

and bridge is successfully setup.. Now the problem starts... if i run
traceroute from Domain 1,2.. (child domains) linux BOOTS !!!

please look into it.

I know that i shud be using the bridge provided along with xen
(somehow that too isnt working) but UML method of bridging is equally
valid.

thanks in advance

Prasoon Jaiswal


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

             reply	other threads:[~2005-01-27  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27  7:54 prasoon jaiswal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-28  7:52 traceroute causes xen reboot from virtual machines Ian Pratt

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=b2c12abe05012623545e09ea53@mail.gmail.com \
    --to=prasoon.jaiswal@gmail.com \
    --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.