hi, I have a Xen server based on Ubuntu Hardy distribution. I would like to give domU''s access to iscsi targets fra SAN in the vlan environment. In dom0 I have enslaved 2 NICs into bonding interface, made seperate bridges dedicated to seperate vlans. There is a special iscsi-bridge for SAN/iscsi vlan. I would like to have a domU with two interfaces: eth0 binding to the vlanXX-bridge and eth1 binding to the iscsi-bridge to get iscsi target. My problem is that with the standard mechanism (vif-script vif-bridge) for making domU''s image, I get networking in domU only via the eth0, the first interface on the list. I examined the domU''s root filesystem and find out that in /etc/network/interfaces there is only the first interface defined. The vifx.x on dom0 side are correctly placed in the iscsi-bridge and vlanXX-bridge. Is it a bug, or do I make it in a wrong way? In any case, what is the best approach ( make a route or make the seperate bridge) for joining eth0ð1 together in domU - having in mind access to iscsi drive? Longina -- -- Longina Przybyszewska, system programmer IT@Naturvidenskab IMADA, Department of Mathematics and Computer Science University of Southern Denmark, Odense Campusvej 55,DK-5230 Odense M, Denmark tel: +45 6550 2359 - http://www.imada.sdu.dk email: longina@imada.sdu.dk -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here we do not use the standard Xen scripts for xenbr0/1/2/n creation since I''ve found them a bit problematic for practical use. Instead of that, we use our own script which brings up every interface and bridge we want to. Also, we do not rely on eth0/1/2/n identification, but on the mac address instead. We have a different situation, though. Our dom0s boot from AoE, and Debian Etch renumerates each port differenty from a boot to another (eth1 may be eth2 after a reboot, for example). In short, that''s my suggestion: bring up your interfaces/bridges/etc with a custom script. If you''re going to work always with bounded eth0+eth1, I suggest you to do that in the dom0 to make things simpler for your domUs. Em Quinta 23 Outubro 2008 13:07, Longina Przybyszewska escreveu:> hi, > I have a Xen server based on Ubuntu Hardy distribution. > I would like to give domU''s access to iscsi targets fra SAN in the vlan > environment. > > In dom0 I have enslaved 2 NICs into bonding interface, made seperate > bridges dedicated to seperate vlans. > There is a special iscsi-bridge for SAN/iscsi vlan. > > I would like to have a domU with two interfaces: eth0 binding to the > vlanXX-bridge and > eth1 binding to the iscsi-bridge to get iscsi target. > > My problem is that with the standard mechanism (vif-script vif-bridge) for > making domU''s image, I get networking in domU only via the eth0, > the first interface on the list. > I examined the domU''s root filesystem and find out that in > /etc/network/interfaces there is only the first interface defined. > > The vifx.x on dom0 side are correctly placed in the iscsi-bridge and > vlanXX-bridge. > > Is it a bug, or do I make it in a wrong way? > > In any case, what is the best approach ( make a route or make the seperate > bridge) for joining eth0ð1 together in domU - having in mind access to > iscsi drive? > > Longina-- Daniel Mealha Cabrita Divisao de Suporte Tecnico AINFO / Reitoria / UTFPR http://www.utfpr.edu.br _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Longina Przybyszewska <longina@imada.sdu.dk> writes:> My problem is that with the standard mechanism (vif-script vif-bridge) > for making domU''s image, I get networking in domU only via the eth0, > the first interface on the list. > I examined the domU''s root filesystem and find out that in > /etc/network/interfaces there is only the first interface defined. > > The vifx.x on dom0 side are correctly placed in the iscsi-bridge and > vlanXX-bridge. > > Is it a bug, or do I make it in a wrong way?If you want a separate route towards your iSCSI target then do exactly that: include eth1 in /etc/network/interfaces. Specify its IP and netmask there, but no gateway! If you share a subnet with the iSCSI target in vlanXX then you are done. If not, you need to set up an explicit route in post-up (see man interfaces). This has nothing to do with Xen at all. -- Cheers, Feri. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When setting up Xen to use a iSCSI target with raw logical volumes works great until I restart iSCSI and it changes the device name. Can I use e2label to solve this problem or is there a way to set a persistent target? --- Chris Edwards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris Edwards wrote:> When setting up Xen to use a iSCSI target with raw logical volumes works great until I restart iSCSI and it changes the device name. Can I use e2label to solve this problem or is there a way to set a persistent target? > > --- > > Chris Edwards >e2label would probably be a sufficient way to doing that depending on how your system does things with labels. Another option would be to use udev to persist naming of the iscsi block devices. This is a link to a tutorial I used about 2 years ago to do this. http://www.performancemagic.com/iscsi-xen-howto/ The udev part of the iSCSI setup would probably be what would be interesting for you. It worked for me. Probably could use a little bit of updating as well but should give you an idea. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users