From: "B.G. Bruce" <bgb@nt-nv.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: RE: Must have been asked before, but I can't find the solution
Date: Wed, 19 Jan 2005 17:32:03 -0400 [thread overview]
Message-ID: <1106170322.30699.52.camel@master.vms.security> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12342B@liverpoolst.ad.cl.cam.ac.uk>
On Wed, 2005-01-19 at 17:21, Ian Pratt wrote:
> > I'm attempting to migrate from vmware to xen, however I need
> > to be able
> > to run more than one bridge.
>
> Should be no problem.
>
> > Now, I can modify the existing network/vif-bridge or build replacement
> > scripts/config files that will get this done, with the
> > exception of the
> > MAC. If you configure (xen-2.0.3-src.tar.bz2) a domain for
> > more than 1
> > nic, the xenU domains use the same MAC for all interfaces. EX.
>
> OK, we need to add the vif number into the MAC generation hash. Anyone
> care to submit a patch?
>
> > How/where do I change this? (not in the config file as far as I can
> > tell)
>
> I believe you can set the MAC for each vif.
WHERE? I must be missing something but for the life of me, I have not
been able to set this for anything other than eth0. If it CAN be done
in the config file, please give an example.
Thanks,
B.
>
> Ian
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-01-19 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 21:21 Must have been asked before, but I can't find the solution Ian Pratt
2005-01-19 21:32 ` B.G. Bruce [this message]
2005-01-19 21:51 ` Kip Macy
2005-01-19 21:52 ` Felipe Alfaro Solana
2005-01-19 22:08 ` B.G. Bruce
2005-01-19 22:13 ` Kip Macy
2005-01-20 13:01 ` Mark Williamson
2005-01-20 15:30 ` B.G. Bruce
[not found] ` <200501210044.03264.maw48@cl.cam.ac.uk>
[not found] ` <1106284353.4743.46.camel@master.vms.security>
[not found] ` <200501221446.12675.maw48@cl.cam.ac.uk>
2005-01-24 16:09 ` Back end domains : input desired B.G. Bruce
2005-01-24 16:18 ` Mark A. Williamson
2005-01-24 16:36 ` B.G. Bruce
2005-01-24 16:50 ` Tobias Hunger
2005-01-24 17:03 ` Jan Kundrát
2005-01-24 17:06 ` Mark A. Williamson
2005-01-24 17:17 ` Andrew Warfield
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 21:11 Must have been asked before, but I can't find the solution B.G. Bruce
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=1106170322.30699.52.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.