Mailing List Archive

> Hmm, if i rethink about this, you probably won't even need this. Bridge the
> varios vif-* devices, and your domU's should be able to communicate over
> there xen frontend network devices.

Yup, that'd work.

Cheers,
Mark

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> The first steps are ok. I hide the network devices from dom0, give domu
> access to the pci devices, and use a kernel with hw access and network
> backend compiled in.
> I can start a domu that can use a network card, but how can I configure
> an other domu to use this domain as network backend instead of dom0?

You need to set some config file options.

For the backend domain, set "netif=1" to tell Xend it's an authorised backend.

In the frontend, for each VIF you declare you need to add a "backend=dom" in
the config list item for each vif, to connect that vif to the backend.
Writing "dom" as a domain number will certainly work, I'm not sure if a
textual domain name will work.

Cheers,
Mark

>
> Regards,
> Krisztian Czako
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> I can start a domu that can use a network card, but how can I configure
> an other domu to use this domain as network backend instead of dom0?

I'm not sure what you are trying to achieve with that setup. Why don't you
have the network device driver in your dom0 as normal and use bridging?
If you don't want to have the dom0 to have network access, just don't assign
any ip address to the eth0.

However, if you really want to access the nic from a domU, it might be
possible to use the "dummy net driver" in dom0 and bridge that to the
domU's, but as the "dummy net driver" discards any package, i'm not
sure if this works (but i guess the bridging code will dispatch the
package to the bridge before it even reaches the dummy net driver).

Regards
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> However, if you really want to access the nic from a domU, it might be
> possible to use the "dummy net driver" in dom0 and bridge that to the
> domU's,
[...]

Hmm, if i rethink about this, you probably won't even need this. Bridge the
varios vif-* devices, and your domU's should be able to communicate over
there xen frontend network devices.

Regards
Michael

--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

2005-05-20, p keltezéssel 09.10-kor Mark Williamson ezt írta:
> > The first steps are ok. I hide the network devices from dom0, give domu
> > access to the pci devices, and use a kernel with hw access and network
> > backend compiled in.
> > I can start a domu that can use a network card, but how can I configure
> > an other domu to use this domain as network backend instead of dom0?
>
> You need to set some config file options.
>
> For the backend domain, set "netif=1" to tell Xend it's an authorised backend.
>
> In the frontend, for each VIF you declare you need to add a "backend=dom" in
> the config list item for each vif, to connect that vif to the backend.
> Writing "dom" as a domain number will certainly work, I'm not sure if a
> textual domain name will work.

Thanx. Textual name works fine, the vif interface is created in the
right netif backend domain.
However, the vif interface isn't added to the specified bridge. If I add
it to the bridge by hand it works. How can I make it automatic (like in
dom0)?

Regards,
Slapic



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Thanx. Textual name works fine, the vif interface is created
> in the right netif backend domain.
> However, the vif interface isn't added to the specified
> bridge. If I add it to the bridge by hand it works. How can I
> make it automatic (like in dom0)?

That's a problem right now: we need to execute the vif-bridge script in another domain. Once we have hotplug or rtnetlink events plumbed through we should be able to solve this.

[.I think (hope :-) Jeremy might be working on part of this.]

Ian



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

2005-05-29, v keltezéssel 22.10-kor Ian Pratt ezt írta:
> > Thanx. Textual name works fine, the vif interface is created
> > in the right netif backend domain.
> > However, the vif interface isn't added to the specified
> > bridge. If I add it to the bridge by hand it works. How can I
> > make it automatic (like in dom0)?
>
> That's a problem right now: we need to execute the vif-bridge script in another domain. Once we have hotplug or rtnetlink events plumbed through we should be able to solve this.

Do you plan it in the 2.x series in the near future?

Regards,
Slapic



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users