|
|
|
|
|
|
|
|
|
|
xen-devel
Re: Multiple netif device channels (was Fw: [Xen-devel] Xen on /. again)
On Sun, Jan 23, 2005 at 05:52:23PM +0000, Mark Williamson wrote:
> > That's fine. Yeah, i marked the backend domain as a netif domain, started
> > it up, inserted the domain ID into the config for the frontend domain
> > (hassle, but necessary as the current code only takes an ID, and not a
> > name), and started up the frontend domain. The additional interface showed
> > up in the frontend domain, but nothing appeared in the backend.
>
> Remind me: is the frontend having netifs attached to two different backends?
> What happens if you try to attach both netifs to the driver domain (not
> dom0)?
Attempted layout is as follows:
Dom0 - single physical network adaptor
netif backend
DomU1 - no physical network adaptor
netif backend
netif frontend -> Dom0
DomU2 - no physical network adaptor
netif frontend -> Dom0
netif frontend -> DomU1
Interfaces for all the frontends appear inside the relevant domains, but the
only the 2 dom0 backend vifs appear; nothing shows up inside domU1.
I'll try connecting DomU2 only to DomU1 wrt networking when i next get a chance.
> Do you have any experience in the Xend guts? You could try turning on
> tracing
> at the top of messages.py and observe exactly what control interface messages
> are being sent. This is likely to be quite tedious but may allow you to
> infer what information about netifs is flowing between the domains. You may
> also want to instrument the probing code in netfront.c and netback.c.
A little bit. i'll try and see if i can see what's happening with it. At a
minimum it'd give me a trace i can post that might help someone else figure
out what's going on.
> Sorry not to be more helpful,
np,
J
--
Jody Belka
knew (at) pimb (dot) org
-------------------------------------------------------
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@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Fw: [Xen-devel] Xen on /. again, (continued)
- Re: Fw: [Xen-devel] Xen on /. again, Jody Belka
- Re: Fw: [Xen-devel] Xen on /. again, Mark A. Williamson
- Re: Fw: [Xen-devel] Xen on /. again, Mark A. Williamson
- Re: Fw: [Xen-devel] Xen on /. again, Jody Belka
- Re: Fw: [Xen-devel] Xen on /. again, Mark Williamson
- Re: Fw: [Xen-devel] Xen on /. again, Jody Belka
- Re: Multiple netif device channels (was Fw: [Xen-devel] Xen on /. again), Mark Williamson
- Re: Multiple netif device channels (was Fw: [Xen-devel] Xen on /. again),
Jody Belka <=
- Re: Multiple netif device channels (was Fw: [Xen-devel] Xen on /. again), Mark Williamson
- [Xen-devel] Re: Multiple netif device channels, Jody Belka
- [Xen-devel] Re: Multiple netif device channels, Mark Williamson
- [Xen-devel] Re: Multiple netif device channels, Jody Belka
- [Xen-devel] Re: Multiple netif device channels, Jody Belka
- Re: Fw: [Xen-devel] Xen on /. again, Trent Jaeger
RE: Fw: [Xen-devel] Xen on /. again, Ian Pratt
|
|
|
|
|